• 2 Posts
  • 32 Comments
Joined 1Y ago
cake
Cake day: Jun 07, 2023

help-circle
rss

Especially with Lemmy getting support for plugins soon, I don’t see the need for making a new platform

A new sorting method for “unanswered” is a cool idea. I’m not sure if it’s quite as simple as just finding posts with 0 comments, because people can put additional questions in the comments but it’s still unanswered. Also how do you sort them for posts with the same number of comments/answers. But this is definitely something that a plugin could handle.

I saw someone else suggested we could just put “[unanswered]” in the title and then edit the title to “[answered]”




Yeah it’s like trying to delete a torrent that you created lol, deleting stuff from the Internet is not so easy. Even websites that claim to allow you to delete stuff may still be backed up by The Wayback Machine or similar, or even just a random user who liked your post and downloaded it.

I would like improvements here, but you should probably still be careful about anything you post if you’re worried about being able to delete it, no matter what site you’re on.


You’re framing it as if this is a bad thing that Lemmy can only see some of the agupe content, but wait until you see how much content non federated platforms can see from each other! I really don’t see how some content is worse than none, if you really want all of it then make an account over there like every other social network in the past requires you to browse on their site/app. It’ll probably improve over time but it really sounds like you’re upset that it already sometimes works instead of not at all.


Defederation messes with this though, we need more ways to control the content without relying on defederation

It makes me feel like I should be making the post to multiple communities, but then I feel like I’m spamming


The GitHub issue is here, you could put a thumbs up reaction on it, and also subscribe to the issue to get updates about it

https://github.com/LemmyNet/lemmy/issues/2987


couldn’t a malicious instance or fork just ignore who is trying to access the data and show all the toots that have been federated at all? anything that can be retrieved by another instance is public

it’s kinda like when Steam asks for your age when looking at an M rated game


The first is that listed subscriber numbers are for your server only

For your first issue, subscriber counts will be fixed in Lemmy v0.19.0

https://github.com/LemmyNet/lemmy/issues/1440

Preview here: https://voyager.lemmy.ml/communities?listingType=All&sort=TopMonth&page=1

The second is that there are many redundant communities, which makes it difficult for onboarding new users. There should be some way to group like-communities into super-groups based on topics

Yeah this one has an issue open, you could join the discussion if you have any ideas, this is a big one

https://github.com/LemmyNet/lemmy/issues/818


Yep haha, it was just running when I made my comment. It’s the alpha testing server so it does go down sometimes.


you can try it out on https://voyager.lemmy.ml/

I made an account and subscribed to a bunch of communities on there to test out, seems pretty good


New users don’t want to be required to block 1000 accounts when they first start, that’s more friction to joining a new social network. I mean Lemmy users already get turned away by the Lemmit bot and that’s just 1 single account to block lol literally like 2 clicks.


A database of bans with tags for the ban reasons could work, like https://gui.fediseer.com/instances/censured

I wouldn’t use email as a great example for spam filters, considering how much it caused Gmail to take a monopoly and how often it blocks emails you actually want. You practically can’t self host email anymore.


But you said you can post to multiple relays, and you can choose what relays to post to freely? Doesn’t that mean duplicate work for all the relay admins?

I have thought about nomadic social networks before based on public keys, I do generally think it’s a good idea. I’m just not sure if the Twitter/Mastodon style is an ideal fit.


I feel like moderation could be an issue though, since Mastodon is only moderated by the instance admins.

If there was a Nostr for Reddit/Lemmy style communication, it could be possible for the communities to have moderators, so that could be good.


Seems like admins can hide communities from all, local, and trending, unless subscribed
https://github.com/LemmyNet/lemmy/issues/2943#issuecomment-1581485335 https://github.com/LemmyNet/lemmy/pull/2055 ``` curl -X PUT http://localhost:1236/api/v3/community/hide \ -H "Content-Type: application/json" \ -d \ '{"community_id":3,"hidden":true,"reason":"controversal","auth":"Foo"}' ``` I haven't tried this, but maybe someone will find it useful and test it out. You could probably also easily do it in the database instead of using the API call.
fedilink


If Lemmy allows you to follow users and their posts show up in your subscribed feed then it sounds like that would be what you want?

https://github.com/LemmyNet/lemmy/issues/3903

If you click the Subscribe button on that GitHub issue then you’ll get email updates about its progress


one thing that’s annoying about this is that sometimes new content will be added to an old URL

like Steam Hardware Surveys, there’s no way to perma-link to a specific month, their page only shows the most recent results

https://store.steampowered.com/hwsurvey/

which can cause weird issues with Lemmy thinking it’s the same post and only showing 1 of them

I had this issue with one of my own communities, I was posting links to the Github Releases page for every new release (which is usually good because people finding old links on Google should see the latest release and the full list of releases, not the one specific release)

but I realized only 1 post would be visible at a time, and if you did Top All sort then it would be a post about an old release, now I gotta post directly to the specific release

when Lemmy has some form of sibling communities or grouped communities, I think it can be less aggressive in detecting “cross-posts” and only explicit cross-posts would be handled as such


stricter instance-level moderation compared to the more “individualistic” view

I definitely think letting users block posts and/or comments from specific instances is way better than full defederation (maybe the instance admin could set a default block list for new users)

but now I’m thinking maybe communities should be able to block instances too

found a feature request for it https://github.com/LemmyNet/lemmy/issues/3022


and people on the site will be talking about Lemmy again

honestly I wonder if it would be more effective to be talking about lemm.ee, sh.itjust.works, compuverse.uk, beehaw.org… pretending they’re just their own things and not talking about Lemmy or Federation or anything like that

might be good to get some users to just signup to the given instance, and slowly realize they’re actually communicating with people from many servers and now they’re in the rabbit hole lol


PSA for Lemmy instance admins: in backend v0.18.3 there is a bug that causes your instance to stop federating properly and to stop sending out outgoing messages
cross-posted from: https://yiffit.net/post/868741 > This new version introduced a system so that your instance stops sending out content to other instances that are supposedly dead / offline. > > Unfortunately for some reason there's false positives. When I checked comparing the results from a curl request vs the information in our Lemmy database I found over 350+ false positives. > > In the DB there is a table called "instance" which has a column called "updated". If the date on that column is older than 3 days, your server will stop sending any content to those instances. > > For some reason I had entries that were dated as last being alive in July, while actually they were always up. If an entry is incorrect, you can fix it by manually using an update statement and adding today's date. If your instance is not too large you can safely update all entries to today's date and check if everything works as expected from then on any new content created on your instances. > > The dead instances won't have an impact unless your instance is larger and generates more content, thus it might be easier to simply update all entries and have Lemmy believe they're all alive if you start noticing wonky behavior and don't want to check one by one. > > If you don't know how to access the database run this command where domaincom is your instance domain without the dot. > > 1. `docker exec -it domaincom_postgres_1 busybox /bin/sh` > > 2. `psql -U ` > > (The default user is 'lemmy') > You could technically do this is one single step, but it's good to know the command to get shell access to the container itself if you didn't know how to. > > This should give you access to a postgres CLI interface. > Use \c to connect, \dt to list tables and \d+ tablename to list table definition. You can also run SQL queries from there. > > Try with this query: `SELECT * from instance` to list all instances and their updated date. > > You can use other SQL queries to get better results or correct false positives. Just be careful with what you execute since there's no undo.
fedilink