- Manjaro for me.
- Impossible to choose, there are too many.
- I didnt have the time or motivation to try different clients yet. The web ui works just fine for me.
The only reason is that no one got around to it yet. Its not that difficult, in fact I plan to work on it soonish. There have just been tons of more important things to work on recently (like improving performance and keeping up with all the pull requests).
Account migration is not in the works, and I consider it very low priority. Unlike Mastodon, Lemmy isnt focused on individual users, so it doesnt matter much if you start posting from another instance one day. If its important for you, you can always put a link in your profile to your other accounts. I would rather implement a way to export/import account data. Thats much simpler and can also be used as a backup in case your instance goes down.
1.0 is not about features, but stability. It means there wont be any breaking changes to the api or federation for a while, until 2.0. In fact we were thinking to make some breaking changes and then release 1.0 later this year. But then the Reddit migration happened and those plans had to be scrapped.
Chat simply orders the comments in a different way, newest first without any nesting.
We are not lawyers so we dont know much about licensing. To be honest I doubt that such bad actors would care much how posts are licensed, they are going to scrape it anyway.
The fix you are referring to only limits how many comments can be retrieved in a single API call (300). This limit is only used when specific parameters are passed, not in all cases.
Limitations no, if anything the protocol is too extensive and lets you do too many things (or do the same thing in different ways). But thats somewhat expected for a protocol which can handle all types of social media platforms. I think the protocol is fine as is, but it needs minor changes here and there to keep up with how it is being used in the real world. The FEP process is doing a good job of that.
From what I know the AT protocol used by Bluesky is entirely centralized, so it doesnt look like a competitor yet. They claim that it will be decentralized in the future, but I will believe it when I see it. For now the decentralization seems more like a marketing gimmick.
I definitely didnt expect it, nor did I expect that there would suddenly be more than a dozen different apps. But its not a problem, the more choices users have the better. Those who like such clients can use them, thout it affecting anyone else. Plus monetization of apps could potentially help to fund development of Lemmy itself.
For instances with ads its pretty much the same, more choice for users. But I really doubt that model can have any success considering how many free instances are around which are run by volunteers. Defederation should be unnecessary assuming that ads are only shown to local users.
Im not a lawyer so I dont know about GDPR. Do you know how similar platforms such as Mastodon handle it?
Thanks for your help :)
It's not so bad if companies don't use your project. Normal people won't care.