Hacker Newsnew | past | comments | ask | show | jobs | submitlogin
Mastodon Announces Fediverse Discovery Providers (wedistribute.org)
14 points by ZacnyLos on Oct 1, 2024 | hide | past | favorite | 2 comments


Aren't relays already a thing? I remember using one back in 2017, but don't use one anymore because you basically had the choice between private relays that just existed to connect up 3 or 4 instances or public relays.

Public relays were really the most authentic way to get the "true" interconnected experience: just a constant deluge of assholes dumping shit nobody actually wanted to look at, which is why I abandoned using them; you'd basically given yourself a secondary job to get rid of jackasses. (Which wasn't worth it on a single-user instance; I'd rather accept the low discovery and just rely on a slowly building graph instead.)

I don't really see any replacement fix those problems; relay quality was always reliant on the operators of the relays after all.


I read here https://www.fediscovery.org/ :

  > How is this related to relays?  
  >  
  > Relays can be used to get a more complete view of what is going   on in the larger  
  > Fediverse. As such there are some similarities to this proposal.  
  >  
  > From an instance operator’s point of view the biggest difference is that using a relay
  > comes with a higher cost. The instance needs to ingest and index everything the relay
  > sends which takes up processing power and storage. A discovery provider will do that
  > work for one or more instances.
  >
  > Implementation-wise we expect to see some similarities with how relays work, at least
  > for real-time data. But discovery providers should be able to index historic data as
  > well. So ingesting real-time data from instances is only part of the story.
  > Querying instances for historic data is not currently something that relays do.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: