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:

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/[email protected].
Communities from different instances should be able to merge, allowing users to see the content of all communities across different instances.

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 2 points 1 year ago

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?

Sure, this and anything else is possible as long as people have the motivation and knowledge to pursue and implement it.

Something similar to DNS standards could work for Fediverse sites. In fact, why not piggyback on DNS like the SPF, DKIM, DMARC, and even openpgp4fpr / KeyOxide standards. DNS itself fulfills the first two requirements:

Some form of "master index" - check! ✅
Replicated across "instances" - check! ✅ ... in a sense ...

If you consider: Zone Transfer / AXFR a form of "replication"
If you consider DNS servers a "node" / "instance"... rather than just a Lemmy/Kbin/Fediverse "instance"

For the second point about DNS zone transfer... it used to be the case that anyone could issue the AXFR request to a DNS server. However, this basically dumps all the records on a DNS server's zonefile for that domain. So, it's often disallowed nowadays because it discloses all hosts in the zone file, some of which might be considered private by the domain owner. Instead, server admins usually configure this to only be allowed by trusted IP addresses of other hosts. (I guess it's a very crude form of "web of trust" based on IP allow lists and the whims of a SysAdmin.)

Maybe the Fediverse has use for piggybacking on DNS via TXT records for some use cases. However, it's likely that some other decentralized method of replication might be invented specifically for federation with other ActivityPub servers.