

Technically it would be a breaking change to remove it, so in that sense it could only be removed in a version 2.0. But maybe after some time we could add a setting for admins to disable api v3, and later have it disabled by default.
Lemmy Lead Developer and father of two children.
I also develop Ibis, a federated wiki.


Technically it would be a breaking change to remove it, so in that sense it could only be removed in a version 2.0. But maybe after some time we could add a setting for admins to disable api v3, and later have it disabled by default.


Yes makes sense, I opened an issue: https://github.com/LemmyNet/lemmy-ui/issues/3725


The difference is that Mastodon already reached version 1.0 much earlier, but Lemmy did not. In the current development branch we made some large rewrites breaking changes early on. Over time more and more features were added, and we cleared much of the backlog of existing issues. Then instead of calling the new version 0.20 we decided to make it 1.0, which indicates that it will be stable for a very long time. After 1.0 is released we will definitely continue with smaller releases to get changes out faster, and there will be no need for breaking changes.


To create multi-communities there is a button one the homepage sidebar (or use the direct link). I tried it just now as normal user without admin and it worked fine. Are you getting any error message?
Ah that makes sense, thanks for the suggestion!
You mean that announcements like this should include a list with the names of all donors?


You can try it now on https://voyager.lemmy.ml/multi_communities


You can try it now on voyager.


Yes just like that, and it will be compatible over federation.


There are a few reasons:


I also developed a plugin for automatic language tagging of posts/comments, it works quite well even on very short text. Will also put it on voyager.lemmy.ml soon.


It will be available for testing on voyager.lemmy.ml soon.


@dessalines@lemmy.ml made various UI changes that seem controversial to me. Such as changing the theme colors or moving most post/comment actions from the action menu to the context menu. If you have strong opinions on the design it’s best to follow the repository on Github and comment in the issues or pull requests where these changes are made. Otherwise these may also get adjusted later during beta testing.


I live in Spain. The user donations alone would not be sufficient, but together with the money from NLnet it’s enough to pay the bills.
Of course I could earn much more money by working for a company. But I don’t like to be ordered around by a silly manager, be stuck in an office for 8 hours every day and get stressed working on a project I don’t care about. With Lemmy no one can tell me what I have to do, and it’s work that’s actually meaningful.


It looks like Castopod is the main podcasting platform on the Fediverse. I had a quick look how it federates. Unlike Peertube it doesnt use groups, so it wont be possible to follow the podcasts from Lemmy. What you could do is make a Lemmy post with a direct link to the Castopod audio file so users can play it from Lemmy (that is after 1.0 is released with the audio player feature).
These types of changes are rather annoying because you need to edit the file, wait about an hour for the release build to finish, then fix any problems and repeat until it works. Though its definitely good to have multiple platforms for releases.
So if you want to make a PR and get it working you are welcome to do that. Then I will add the auth token so you can test it. Github seems preferable as we already use that.
Thats doable with our CI tools (docs). Would you open an issue?


Thank you :)


Thanks!
No it’s only the number of votes given by you personally to a specific user. Not the total of votes by all users.