List is Unmaintained

[indiealexh]

This author does not appear to be maintaining this list.

I would like to offer my fork as an actively maintained list.

https://github.com/masrly/awesome-mastodon

If someone knows of a better fork to use, I am open to it.

[ineffyble]

@indiealexh I think you might need to enable issues on your fork. I also wonder if having GitHub show it as a fork might affect SEO and discoverability (might want to detach it).

[indiealexh]

Interesting thought. I will look into that.

[gcruchon]

I've seen some contributions from @tleb on other repos...

IMHO: Would be interesting to help @tleb maintain this Awesome list (600+ stars) rather than changing to as 2-star fork.

Do you need help, @tleb ?

[tleb]

Hi, author here. I still believe a list such as this one can be useful. I'm unsure about how to handle it. A few thoughts:

• I wouldn't mind spending some time on it, but help is appreciated. Knowing that I will have to check each submission and make a judgment that people kind-of trust is what makes me rather leave it stall. That kind of help can be from anyone: just go through pull requests and give your opinion. Is the project/link useful? Is the patch done well? etc.
• I would rather the list be awesome-activitypub than awesome-mastodon. That promotes the protocol ecosystem, which is what really matters. Mastodon-specific stuff would become a subsection (or multiple). That could be an overall trend, to allow for renaming later on. First step would be to rename sections and fix descriptions so that they mention "Mastodon" for Mastodon-specific projects. Then make sure general ActivityPub links are present (spec, good first-timer text article, etc.). Then rename the list. Please don't hesitate to send patches in that direction.
• I don't want it to become an append-only list. Submissions have to be truly challenged, and it should be fine to remove a link from the list. Please don't hesitate to make patches in that direction.
• I don't feel like this list is mine, it should probably belong in an organisation namespace.
• Ideally I wouldn't be needed anymore, but I don't know who could be given moderator rights. I think the first point about having people simply giving their opinion is a good way to have people show their involvement interest.

I'd also like to thank you guys for not assuming I have any obligations towards this list. I was afraid of that when seeing the title. I'd be down to spending some time on this list to keep it in shape, again having as long-term vision the whole ActivityPub ecosystem and not only Mastodon. Organic help through opinions and discussions on pull requests would be really appreciated.

Have a good day!

[hueyy]

I forked it too at https://github.com/hueyy/awesome-mastodon and made some updates before I noticed this issue. Definitely agree there should be an actively maintained version of this list somewhere. Happy to send in a PR to @indiealexh's, but maybe we should create an organisation and give the current participants merge access.

[ronilaukkarinen]

+1 for maintained list!

I wouldn't mind spending some time on it, but help is appreciated. Knowing that I will have to check each submission and make a judgment that people kind-of trust is what makes me rather leave it stall. That kind of help can be from anyone: just go through pull requests and give your opinion. Is the project/link useful? Is the patch done well? etc.

Come on, it's just a list! Don't stress about it. Just add all things related to Mastodon. That's my 2 cents.

I would rather the list be awesome-activitypub than awesome-mastodon. That promotes the protocol ecosystem, which is what really matters. Mastodon-specific stuff would become a subsection (or multiple). That could be an overall trend, to allow for renaming later on. First step would be to rename sections and fix descriptions so that they mention "Mastodon" for Mastodon-specific projects. Then make sure general ActivityPub links are present (spec, good first-timer text article, etc.). Then rename the list. Please don't hesitate to send patches in that direction.

Create another list for that purpose? These are not mutually exlusive.

I don't want it to become an append-only list. Submissions have to be truly challenged, and it should be fine to remove a link from the list. Please don't hesitate to make patches in that direction.

Also at the same time submissions should not be stuck in the request queue. You should apply them with a low bar. They can be later removed.

I don't feel like this list is mine, it should probably belong in an organisation namespace.

This does not matter. Even though it's under your name, who cares and why should one care? The list is all that matters.

Ideally I wouldn't be needed anymore, but I don't know who could be given moderator rights. I think the first point about having people simply giving their opinion is a good way to have people show their involvement interest.

If you're available, that's good. If not, then start looking for maintainers.

These are just my two cents. Sorry if the frustration leaks through my opinions but I've seen too many times that maintainer loses interest for wrong reasons. Releasing something light as a list for god's sake as open source should be simplest thing to do. It shouldn't be stuck in meta discussion and creating endless forks because of that. Heck, I could create a maintained fork as well. But let's see this through first. There's 15 PRs, check & merge those first and let's continue from there?

[BasixKOR]

Hi, maintainer of awesome-activitypub (albeit quite poorly maintained) here. And I think this list serves a different purpose and a list focused on Mastodon is pretty valuable imo.

Awesome lists are meant to be a 'curated' list, and the idea of listing up-to-date and quality items is great but I also don't think that means inspecting every single corner of the project. Usually GH stars and commit history give enough context to whether the project is recognized by the community. Maybe look into source code, or community sentiment, sure but it isn't mandatory.

[shamiv]

Happy to help maintain this list.

[hyperupcall]

sindresorhus/awesome now recognizes hyperupcall/awesome-mastodon as the awesome list for mastodon. See related discussions:

• Update link to Awesome Mastodon sindresorhus/awesome#2739
• Following _Awesome_ guidelines hueyy/awesome-mastodon#45

I spoke with @hueyy (who maintains the next active fork), and as discussed in the second link, there would have been obstacles with the list getting recognized by the main awesome repository (since it runs awesome-lint, and fixing those violations would have removed some of the aesthetic improvements).

Unfortunately, I didn't think about discussing the same thing here, because here was substantially less active 🤦 . So now we have a thing where there are two awesome-mastodon lists. As mentioned by @tleb I commented on a few pull requests - I'll make some of my own as well.

About a separate organization, that might be a good idea. There is an organization specific to awesome awesome-lists, but maintainer of Awesome prefers that awesome lists are under people's accounts, so people feel more ownership over it. So in the end, it might just be better to leave it under tleb. My thinking is that if we get this repository back in shape (maintenance, compliance with awesome-lint, etc.) quickly, I can change the link back to this one so there is no split.