I see, that is understandable.
Lemmy Lead Developer and father of two children.
I also develop Ibis, a federated wiki.
I see, that is understandable.
I was asking Rimu, but good to get confirmation that it’s working for you at least :)
Did you receive my email from last Thursday? Seems there might be some delivery problem.
Good idea, adding this to Lemmy.
The code change is linked here: https://github.com/Chocobozzz/PeerTube/issues/2704#issuecomment-3914781110


This is a known bug in lemmy-ui. Looks like the fix was not backported to stable yet.
https://github.com/LemmyNet/lemmy-ui/pull/3459
Edit: Fixed in #3968, will be included in the next 0.19 release.
You can subscribe to Peertube channels from Lemmy since a very long time. Recently there has been a problem with federation on the Peertube side, but that will be fixed soon.
If any Activitypub platform sends messages to an actor which they arent addressed to, thats clearly a bug.
This is wrong, Lemmy doesnt send private messages to followers.
This is not correct, Lemmy sends private messages only to the single recipient server. Other instances cannot access it at all.
Not public. Private messages can only be accessed by your own admin, and the admin of the recipient. Other instances cannot access it in any way.


How does the json for a batched vote activity look like?


Working on Lemmy, instead of selling my soul to a company.


Good job! I wonder why some of these are missing from fediverse.observer. There is an add instance page, and entering for example aussie.zone says it already exists, but the search doesnt find it. Lemmy.cafe, fosscad.io are included in the statistics (file instances/full.json.gz in the git repo), but not currently shown on the website.
Thanks to your comment I realized that we are only showing instances with registration application on the official site, as there was concern that others would be overrun by spam bots. I had a look at it now, and instances with captcha are actually fine. Here you can see all that are newly listed on joinlemmy.
The instance list is sorted by monthly active users with slight randomization. As these instances you mention are among the larger ones, it is expected that they show near the top. Is there a better sort method that you would suggest?
Good idea, I just implemented this.


You’re in luck, I just modified the instance crawler on join-lemmy.org to collect statistics for all Lemmy instances. You can find them in this repo in JSON format. Now we need someone to build a tool that can visualize it. The stats could even be shown directly on join-lemmy.org.
Lemmy also has an admin setting like that. Additionally there will be private, federated communities available in version 1.0.
I made a couple of “Help Design Lemmy” posts in !lemmy@lemmy.ml recently to get feedback and ideas, which was very helpful. I will continue to make such posts to improve join-lemmy.org, and also Lemmy itself.
Had a look at the Piefed signup now, choosing categories like that is a good idea. But the question is how these categories get curated. We have something similar with the instance topics on join-lemmy.org but no one is really helping to maintain them. So for community categories it would probably similar. In 1.0 we will have some improvements for discovery, like multi-communities and a “suggested communities” collection which can be set by local admins.
For the Mastodon recommendation there isnt any good alternative software that I can see. So its probably best to recommend a single Mastodon instance, depending on the target audience.
What do you mean by instance url redirection?
We discussed about merged comments for same post url, but there was no clear support for it. Many people dont care or warn that it could have unwanted side effects.