henfredemars

It's been said to death but at heart, I've always felt that when it comes to piracy, it's a service issue, not a cost issue.

Except for you Adobe. That's a cost issue.

It's part of the migration plan to help users move away from the platform.

We do have privacy laws today (USA user), but they are so weak that near my office I regularly see ads advising businesses to treat it as a liability problem and instead buy insurance as a faster and cheaper alternative to good practices.

And it works! This approach should not be feasible to address the costs of violating user privacy. It reiterates to me that we are far too lax.

Reddit is the best thing to ever happen to Lemmy. By making their product so terrible, it just keeps making Lemmy look more enjoyable because it's incendentally rather than actively trying to be terrible.

It's nice, but I feel like this is temporary. I don't see Lemmy being more bot resistant. The bots will probably come. I think that's alright because it's just not the main problem that Lemmy is trying to solve.

This is hilarious. On my Desktop, which is quickly becoming my preferred interface for the moment, I just keep opening new tabs and letting it work when I post so I can move on with reading other content.

I ain't even mad. You've got a good heart, soldier.

It really helps that the official Reddit app is so awful. The bar is quite low for acceptability!

The purpose is backward and forward compatibility respectively.

The minimum version is the easiest to explain: any older, and your app just won't run. Don't even try. I (app) don't have the compatibility code to work with you if you are older than my minimum version because I didn't choose to include it, and you (Android) don't know the changes that were made in the future platform versions, so you can't help me.

Target version is a little more complex. This is the version of the API that I am designed to run with. You can use this information to set compatibility parameters for forward compatibility. For example, if I try to use API that doesn't exist in your version or that would have had different behavior, you would know what I'm expecting because I declared to you what it was designed for at the time. This allows the system to tolerate your outdatedness better.

However, that compatibility feature sometimes leads to security issues because the new API tends to be more restricted or improved in ways that enhance security and privacy, hence the argument why there should be a minimum target version to express that you cannot use the less secure API even for the sake of compatibility.

As you mentioned, that in and of itself isn't a bad thing. Sometimes it's good not to have people who are really casual users in your community. They can take their time coming over as long as the people who are here are having a good time.

I'm using Connect for Lemmy. It's not perfect, a few bugs, but it seems to run acceptably well.

Because of the common API, if this becomes the mode, I expect clients would allow you to sign into multiple instances in the same way that you can have multiple email accounts in the same app. I'm very curious how this plays out.

I think usernames are specific to the instance, so any time in the future a person can start up their own instance and get user@myinstance, but your username at lemmy.world is yours.

I think that's a wondrously extensible way of extending the username space.