Sounds like a variant of Doom. Now I want to play this game and shoot up the monsters.

Found this: https://x.com/PenPizzaReport

He is right though, 5000 USD per month for an instance with 12k monthly active users is completely unrealistic, or it is run very inefficiently. mastodon.world is a similar size and costs much less than 2300 Euro per month (which includes numerous other instances like lemmy.world etc).

It helps if you block all those communities you don’t care about. Or even block some instances.

Signatures are only used to deliver activities to inboxes. The Activitypub json data of posts is usually available without any auth.

Private communities will be in 1.0, along with some other visibility modes.

We don’t have the capacity to implement all the features users ask for, at least not without additional contributors or waiting a long time. So it’s better to implement it as a bot.

The cleanest solution seems to be the one described in my previous comment, so you get an archived community with all the original content, correct usernames etc. And make a new community for new posts. Or have the bot create new posts and comments with the same content, and credit the author in markdown body. But that seems like a worse solution in many ways.

Many of these are already implemented in Lemmy, others are too controversial and wont be added (such as karma).

We are currently preparing the 1.0 release which will have lots of major new features, such as private communities, multi-communities and much more. Although 0.19 is also getting constant updates with smaller improvements, for example 0.19.11.

Can you say which mod tools Piefed has that are missing from Lemmy?

You can write a script for this:

# loop through all post
GET https://lemm.ee/api/v3/post/list?limit=50&sort=New&community_name=fedigrow&page=*page*
# take `post.ap_id` for each item
# then fetch it over activitypub on the other instance
GET https://lemmy.ml/api/v3/resolve_object?q=*urlencode post.ap_id*
# same thing for comments
GET https://lemm.ee/api/v3/comment/list?limit=50&sort=New&community_name=fedigrow&page=*page*
# again fetch
GET https://lemmy.ml/api/v3/resolve_object?q=*urlencode comment.ap_id*

Part of the reason is that Lemmy forwards all replies and votes to community followers. Mastodon doesn’t do that, so if you’re on a different instance you can miss a lot of content.

Feel free to open an issue for federation between Piefed and Ibis, at least in theory it should work. The wikis in Piefed are not federated.

111, nice

That instance runs Lemmy 1.0 which is still in alpha state, and the frontend is not compatible yet. So only the api works there.

Yes not sure whats wrong there, the server was using a lot of cpu for no reason. Restart fixed it for now, let me know if it happens again.

Im not familiar with Wikidata, but with enough development time it could probably also be recreated as a Fediverse project.

Thanks :)

Ibis uses markdown, not wikitext because the former has better support in Rust. There are some tools for converting from wikitext to markdown for example this one. By the way ibis.wiki is specifically for articles related to open source projects, you can use open.ibis.wiki for other topics.

Fully agree that theres too much politics. Like you say too often about attacking some kind of enemy rather trying to understand other perspectives. For better or for worse, those seem to be the types of people more likely to use a new platform like Lemmy. Hopefully in the future they will also get tired of this stuff.