mastodon/fediverse_auxiliary_service_provider_specifications

Remove Lemmy

Closed this issue · 4 comments

I just found out about this repo by coincidence, and was surprised that Lemmy is implied to be involved, by prominently showing the Lemmy logo in various images. We Lemmy maintainers have never been contacted by Mastodon maintainers about this, and do not support it in any way. The whole purpose of Lemmy is to be a decentralized alternative to large social media corporations, so we will never add support for the kind of centralized services you are proposing.

So please remove the Lemmy icon from all images in this repo, and I also suggest you contact the maintainers of Pleroma, Peertube etc for permission to include their logos.

@oneiros this issue didn't automatically close, just fyi

Hi @Nutomic!

First of all, I respect your stance on this and I removed the logo from both this repo and the website at www.fediscovery.org. I am sorry if this recreation and usage of your logo has offended you in any way. It was my idea and fault and offending anyone was never my intention.

That being said, I think you might have misunderstood my intentions and I believe it is important to understand what I was trying to achieve here:

Lemmy is implied to be involved

I did not mean to imply this at all. Instead I chose a diverse set of fediverse software logos to

a) show how diverse the fediverse is and
b) that this project is not a Mastodon-only thing

I have only been with Mastodon for a couple of months but already had to learn that we are often accused of doing our own thing and not collaborating with the wider fediverse enough.

We wanted to prevent making this impression with this project and thus I came up with the idea of showing the fediverse as a set of diverse software projects. Note that I even left out our own logo trying to really convey that this is meant for everyone.

I am sorry I failed to make this more clear ☹

Also, we reached out on several channels to invite collaboration from other implementers. If this did not reach you than we were not thorough enough.

The whole purpose of Lemmy is to be a decentralized alternative to large social media corporations, so we will never add support for the kind of centralized services you are proposing.

This is our purpose as well. We tried to take great care to demonstrate that the FASP concept is not meant to facilitate centralization.

I like to think of this as something akin to storage providers. I know many Mastodon (and other fediverse) server administrators use AWS S3 for storing media files. So you could say this is centralization, but I do not think it is, because we offer the ability to use different providers and even local storage. And while switching can be a pain, it is possible.

We would really like to see the same here: Different implementations of FASPs run by different organizations and server administrators being able to choose if and which ones they want to use.

If you believe this is too centralized than we would really love to hear your opinion on how we could improve the concept.

Thanks for addressing this so quickly, feel free to close the issue then.

a) show how diverse the fediverse is and
b) that this project is not a Mastodon-only thing

But it seems that this project is entirely made by Mastodon and no other Fediverse projects are involved, right? So that impression would be completely correct.

Regarding this project itself, it seems like all the example use cases can be handled just fine over Activitypub. For example link previews can be generated by the instance where a post is originally created, and federated as part of normal Activitypub messages. The same goes for blocklist synchronization which can be done through an attribute on the instance actor. So I fail to see the purpose of creating yet another protocol.

Thanks for addressing this so quickly, feel free to close the issue then.

Will do, thanks!