Firstly, there is the unstoppable flood of new posts that are added while browsing “All”. Although this doesn’t happen when using the Jerbea app, it sometimes renders “All” unusable in the browser.

This will be resolved once websockets are removed with the next update:

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

Secondly, the issue of the same posts being displayed for days under “Hot”. There is already a pull request for this, so it has been fixed and just needs to be implemented:

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

Now, the only remaining points for me are:

  1. Links to external instances should automatically be transformed when opened so that one can participate with the account of their own instance. For example, lemmy.world/c/memes should automatically become feddit.de/c/memes@lemmy.world.

  2. Communities from different instances should be able to merge, allowing users to see the content of all communities across different instances.

  • tvmole@lemmy.dbzer0.com
    3·
    1 year ago

    Links to external instances should automatically be transformed

    100% agree. Getting linked to other instances where I’m not signed in is a really clunky experience. It seems like that’s been happening less since I got on the Jerboa app (or maybe I’m just clicking on less links)

  • adinfinitum@lemmy.film
    2·
    1 year ago

    Secondly, the issue of the same posts being displayed for days under “Hot”. There is already a pull request for this, so it has been fixed and just needs to be implemented:

    Adding the “hide” feature from reddit would be an easy fix/stopgap solution. I had a similar issue in reddit when one of my multis included a less active community, so I’d just hide the posts I was done with.

  • hardypart@feddit.deOP
    2·
    1 year ago

    Both would keep exiating. I imagine it like a federation on the community level. Gaming@kbin.social could federate with gaming@lemmy.world and when you view one of the two, you would see the contents of both as if they were one community. When creating a post you would still need to decide to which of both you want to post it, though. This would make sure that there are no problems in the case of “defederation”.

    That’s how I imagine the whole thing. Not sure if there are any negative side effects I can’t think of right now, though.

  • macniel@feddit.de
    1·
    1 year ago

    What do you mean with

    This will be resolved once websockets are removed with the next update

    I hope it wont be removed throughout the software since its really refreshing to see updates in realtime, be it Upvotes/Downvotes, Comments, Posts etc.

  • funkyb@lemmy.world
    1·
    1 year ago

    I posted this in Ask Lemmy but since it didn’t get traction I’m gonna piggyback on the visibility of this thread:

    As i learn my way around ActivityPub based services, what stands out to me the most is federation is very much exposed to the users. (That, or I still just haven’t wrapped my head around the architecture details and how they manifest in terms of user experience.)

    Am I just misunderstanding this, or would the end-user experience be more fluid and functional if the federation mechanics were mostly ‘under the hood’. What I mean by that is - right now if there’s a community I would enjoy participating in that is located on a different instance, in order to do that I need to (a) know it exists in the first place, (b) know what instance it is on, and (c) explicitly tell my instance about its address in order to join.

    Would it be possible to have some form of master index (replicated across instances - not a centralized service) along with a public standard for registering an instance/community on the index? And if something like that existed, couldn’t that push what is an inherently more technical detail to lower levels of the implementation, and make for a simpler UX by allowing every instance to expose a more complete list of communities to users from directly within whatever instance they choose to use?

    • EthanolParty@lemmy.sdf.org
      1·
      1 year ago

      This is probably the biggest issue I have with Lemmy right now. To make matters worse, it’s really easy to miss how the system works. A lot of new users on smaller instances probably think this place is a ghost town because they don’t see many communities in the directory. It’s not ideal to have to use an external tool to find communities, then extra problematic that the actual process is so awkward: manually pasting the address from the external site in the search bar, then you get a “community not found” warning but ignore that, then the community will appear but it’ll grab the old posts and not the comments. Weird.

      I can accept that it would be too much if every single instance defaulted to a full local sync of every other community on every other instance, but they should at least show up in a list when searched for, IMO.

    • hardypart@feddit.deOP
      01·
      1 year ago

      Am I just misunderstanding this, or would the end-user experience be more fluid and functional if the federation mechanics were mostly ‘under the hood’.

      I know what you mean, but I’m not sure it’s a good idea. Look at the recent beehaw-defederation drama. This would have been totally intransparent if the whole federation thing would be something that’s only running behind the curtains.

  • tyfi@wirebase.org
    1·
    1 year ago

    How would merging communities across different instances? Would one be chosen as the new primary, and the other goes away?