

Maybe it’s different when you’re starting in the States, but every international flight I’ve been on has served at least two meals and complimentary drinks.
Maybe it’s different when you’re starting in the States, but every international flight I’ve been on has served at least two meals and complimentary drinks.
Joke’s on Ozzy if that was an international flight, you get free drinks on those whether or not someone next to you dies
I agree that that specific use case is a pain, but I don’t think federated logins are the fix for it. Rather, links to posts on other instances should be automatically translated to a link to the federated version of that post on your home instance, such that you can interact with that post without having to re-log-in. There’s a bunch of issues in the Lemmy GitHub project related to this, so hopefully it gets implemented soon.
In my opinion, federating logins kind of defeats one of the main purposes of federation though, which is to give the user control over where their user information lives.
I don’t think the lack of “federated login” is unintuitive. You wouldn’t expect going to gmail.com and logging in with your Yahoo credentials to work, right?
Having a “federated login” service would probably either add a ton of complexity for instance owners, or someone would implement some super naive and insecure centralized solution, leading to a bunch of people’s creds getting stolen.
Getting the post/<id>
thing to work across instances would be a pain too, because it would require instances to all coordinate post IDs to ensure collisions don’t happen, since far as I can tell, the id in the URL isn’t globally unique.
No, I’m saying all of my international flights that take off from the States have had complimentary meals and drinks