social.coop is one of the many independent Mastodon servers you can use to participate in the fediverse.
A Fediverse instance for people interested in cooperative and collective projects. If you are interested in joining our community, please apply at https://join.social.coop/registration-form.html.

Administered by:

Server stats:

491
active users

@silverpill care to elaborate?

What is wrong with those things existing as auxiliary services?

@mariusor

None of those things need an external provider.

There is also an EEE aspect of it, because they use custom API instead of ActivityPub.

Dmitri | 🇺🇦

@silverpill @mariusor what about cross-instance (opt in) Search? That kind of does need to be an external service, no?

@dmitri @silverpill personally I'm of the opinion that whatever people publish as a public ActivityPub activity/object is fair game for doing public things with it, including search or dissemination in other formats: RSS, calendars, bridging to other networks, etc.

@dmitri @mariusor Server operators who want to provide data can host a relay (for example, Pleroma has a built-in one). People who want to access that data (for whatever purpose) can subscribe to those relays.

@silverpill isn't that pretty redundant? On multiple levels even... one: collections should be accessible through HTTP, two: if a server is interested in content from another server AP already has ways of modelling that in the vocabulary.

@dmitri

@silverpill @mariusor wait, but that relay you're describing - that's an auxiliary service

@dmitri the way I understood what
@silverpill is saying is that if those are part of the same server ... they're not "auxiliary".

@mariusor @dmitri Yes, a built-in relay. Direct communication between servers, 100% ActivityPub