Lemmy maintainer
Funny, Mastodon just posted a similar thing about creating a foundation. But the problem is, the existence of a foundation does nothing to prevent billionaires from controlling social media. For billionaires its very easy to donate a few hundred thousand USD to the foundation and gain influence that way. I expect that Bluesky will be fine for the first years (maybe like early Twitter), but sooner or later the foundation will take decisions that the users dont like, and there is nothing they can do about it.
In my view, the only way to avoid influence from billionaires is to avoid any large centralized structures. In the Fediverse there are dozens of platforms and thousands of instances. Even if a billionaire were to take control over a couple of projects or large instances, people would create forks in a matter of days. Some admins would block these corrupted instances, and their users would barely notice that anything changed.
So Bluesky is just trying to repeat something that has already failed. The Fediverse is the future, but it will take a long time for most people to understand that.
It’s like Blaze says, we are already working towards version 0.20 now which will have various breaking changes. There will be an announcement a while before the final release to let developers know about the changes. Also the current api v3 will still be available for backwards compatibility.
Sounds like you are familiar with this topic. I dont have time to work more on this particular aspect (there are lots of other tasks like comment support, federation with Lemmy, etc). But contributions are definitely welcome, preferably directly to leptos_use
so that others can benefit and its easier to maintain.
It uses the browser preference for light/dark theme by default. After you click the theme toggle on the site, it keeps using that chosen theme by storing it in a cookie.
Seems unlikely, but maybe it will happen in many years if Ibis shows that its possible and desirable.
Not sure really.
If there are still problems you should open a new issue. We cant leave issues open forever because they go stale and dont account for new features. By the way we are planning to implement multi-communities.
The post yes, but not the comments at depth > 50.
No the max comment depth is generally lower now. However this doesnt affect comments created before upgrading.
Changing post.url
from varchar(512) to varchar(2000) really messed up database performance so lemmy.ml became unusable. Turns out that column statistics are removed when the type is changed, so we had to run analyze
as part of the migration. Seems like a bug in postgres.
https://github.com/LemmyNet/lemmy/issues/4983#issuecomment-2446945046
Dont think I did, it was really a team effort. And in the end the working solution was suggested by @phiresky@lemmy.world, thanks for that!
It will be rejected by the api (or by federation).
Correct, I suppose the ban button could be hidden from the ui in that case.
Do you think all of lemmy.ml is a single person? In this case its just the decision of a single moderator, nothing to do with admins.
Right I will also have to make a template with these common parts of the release announcement. Instance blocking is not implemented yet, but it uses the same federation library as Lemmy so that will be easy to add when its needed.
And yet the article manages to get people upset, makes the talk about it and get shared. Basically free marketing for SH2. It’s a win-win for eurogamer and for the game publisher. All it takes is a single troll on Wikipedia and some PR work.
In principle it’s finished, but last time we put it on lemmy.ml for testing there were performance problems and we had to revert. So far it’s not clear what caused those problems, so we need to try again somehow.
The Lemmy backend doesnt treat this field as markdown, if you look at the Activitypub data (
curl -H "Accept: application/activity+json" https://lemmy.world/post/24241974 | jq
) the title is federated as plaintext. Only lemmy-ui decides to render it as markdown for some reason.