deleted by creator

Sure it does. I can have T’s & C’ for my own services and so can they. They are not legally obliged to let him scrape them. Then they’d need to pay for the load. Makes no sense.

It’s not left if I give it away. As soon as I wire it to, let’s say Red Cross*, it is not longer there.

*first thing that came to mind

The issue is not the free headphones that aren’t there, it’s that people think having no headphones is an excuse to create an acousting hellscape for everyone around them.

We can only solve that issue by telling people all the time until they stop doing it. It seems the reason it’s happening more and more is just because many others wear headphones and stare at their phones and no longer observe their surroundings. Strange times.

Not really the point, it costs, people need to buy it, not doing it is easier.

My wired headphones (Sony MH410c) cost me three euros. But those were often included when buying a Sony phone. A decade ago you automatically had headphones when buying a phone.

Still doesn’t make it alright, but it’s let’s accessible now and I can see that leading to a societal change.

I’ll donate it all. Nothing left, nothing to lose.

Update what?

Not much, the battery will just deplete quicker. Otherwise you only notice that phone calls make the phone ring. If it is suspended, it won’t ring. (for now)

Also, SailfishOS uses an Android kernel with libhybris, I want to use a mainline kernel to ensure I’ll get updates for a long time.

UFS == flash in this case, it’s where the phone stores OS, bootloader, user data and so on.

Could you please link to where you found that? Maybe that’s outdated info? Without the context I’m not sure what exactly is unreliable.

Phone calls work, but only if the phone is not suspended. Some people are working on letting the phone wake up when called. Haven’t followed the progress for a while. If you disable suspend, is works well, at least for me. Not sure whether others have noticed issues in different situations.

Oh and I’m currently working on mainlining the Xperia 10 III with the intention of porting Mobian. I got display, GPU, flashlight working, but am stuck at figuring out whether that phone has a bug that breaks it if I enable UFS support, like some Xperias has in the past. If anyone knows a way of veriying whether it is safe to turn on flash, that’d help a lot. I could then enable UFS, Wifi, Modem, GPS, and probably Bluetooth… all at once.

Just don’t want to find out whether it’ll break the hard way.

I’ll keep this up to date with my current progress: https://git.erebion.eu/forgejo/erebion/pdx213-temp

I’ve ported Mobian to the Pixel 3a and use it as a daily driver.

two annoyances:

• I’ve not yet figured out calls via Bluetooth, but other audio works fine, including XMPP calls via Dino [if anyone knows how to get calls working via Bluetooth, drop a comment and I’ll see if I can get it working]
• camera is buggy and does not work well yet (there are people working on that)

Here’s what I had posted on it around a year ago: https://lemmy.sdf.org/post/22388672

They’re prpbably all spicy pillows by now, be careful.

You can buy a physical eSIM an provision it in a phone that runs the right app.

Do people actually text each other? Haven’t received an SMS message in… years? :D

Did you consider talking to the RFC’s author? Maybe they are planning a new RFC that will update that, this could then be included.

I already have an invite flow that users will arrive at and go through when signing up, now I want to let users create invites for other users. That page does not mention anything about that. It seems to be about adding a flow that asks user for details such as an email address and then they get their account.

In my case users have already gone through that and want to invite someone else.

With invitations, you can either email an enrollment invitation URL to one or more specific recipients with pre-defined credentials, or you can email a URL to users, who can then log in and define their own credentials.

I already have enrollment invitation URLs. Just not automatically. I wrote a script that uses the API for that purpose.

The docs even mention this about the flow:

Enrollment (2 Stage)

Flow: right-click here and save the file.

Sign-up flow for new users, which prompts them for their username, email, password and name. No verification is done. Users are also immediately logged on after this flow.

Nope. Not what the question is about. This requires an admin user to create an invitation in the admin backend. I want a way to let users do that.

I read the whole thing, but my brain decided it should replace IRC with XMPP while reading, so it made less sense. xD