this post was submitted on 02 Jul 2023
10 points (100.0% liked)
Reddthat Community and Support
661 readers
1 users here now
Reddthat Community & Support
This community is for us to chat about anything and everything, including support topics!
There is no defining specific rules for this community and it can be anything from "I do not like the weather" to "I've won the jackpot and want to give all the money away to charity!" ๐
Before posting, have you read the rules?
Introductory Required Reading
For anything else, try a search and see what turns up, if not post away!
Alternative Matrix Chatroom:
Alternative Support Forums:
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Champion Tiff - it's a new frontier so all of these things I imagine will come with time.
This helped a lot ๐
I do not know how quickly it would be implemented in Lemmy UI, but I fully expect a third party app like sync when it becomes available or connect at some point will support it.
When you request a list of posts, the return is in json. It should only be like 5 lines of code to filter out posts at an instance level using a third party app setting before displaying in the app.
Blocking on a native level will require a database to hold user block preferences, and then the server would have to look the user preferences and parse the json on the way out to fulfill the filter at a server level. At scale, this will be very resource intensive for instance servers, but would be much easier for performance if the filtering is distributed and done on the users computer.
TLDR: hard for Lemmy server to do, easy for third party apps.
This could be implemented natively with a DB list on the server side that holds the user block preferences and is presented to the Lemmy UI client and then some JavaScript runs on the user side that is supplied by Lemmy UI to block the instances in the view. Would take unification of implementation between server and UI code base, but it would not be 5 lines of code like it would be on a third party app with its own local user setting database.