• 16 Posts
  • 23 Comments
Joined 1 year ago
cake
Cake day: June 11th, 2023

help-circle














  • @TGRush

    for me any of the up/downvote, click in to view, or boost counts.

    I’m a scroller, but, like, if i see a joke in https://lemmy.world/c/dadjokes then i can chuckle and give it an upvote but i dont have to click in and load the thread fully. But the next time i load the page id lke to not have to scroll past that same thread to see new stuff.

    If i downvote something id like to not see it again on the next load. If i open a thread and read the comment posts, i dont need to see that thread again on tne next load.

    That sort of thing.

    It does have some downsides in that finding threads i /sort-of/ remember and want to check again is harder, but i’m used to that.

    @Facni @ADHDefy



















  • @DaughterOfMars

    For #1 - ive thought about that.

    My thought would be something like a small LDAP type server. Self-hostable. You make a user like myuser@mydomain.net and its honored as a log in for the various fediverse stuff.

    So like it could hold the subsciptions for the communities on the various threadiverse servers you connect to localy, and when you open say lemmy.ml, part of the info sent for your user would be a list of communities you are subscibed to on lemmy.ml.

    If it just handles the user auth, then it could also be a user auth for other fedivers stuff too. PixelFed, and Mastodon, etc. Each service could have its own sub section of the user object’s info.

    You would still probably end up with a “home” instance you would use, but if that home instance becomes untenable, or goes away, then you would just pick a new instance and log in there with your myuser@mydomain.net account.

    Im not a good enough dev to code it, but thats my idea anyway.