Well the Sony XZ1 Compact got IP68 even with aux input and a microSDXC slot so I don't think combining the SD Card with water resistance should be a problem. The swappable battery would probably be worse.
Regarding bloatware I've gotten used to using adb and the uad to remove it when buying a phone. https://github.com/0x192/universal-android-debloater/tree/main

Keepass2Android doesn't have it yet, but seems to be working on it
https://github.com/PhilippC/keepass2android/issues/2099

Strongbox seem to have their implementation done for iPhone
https://strongboxsafe.com/updates/passkeys/

I was thinking about trying another ROM on my old XZ1C but my banking apps wouldn't run properly if I did that anyways.

I can only imagine that your conviction is wrong. If we were large enough a market to make a nice profit then I imagine the smaller phones would still be around.
With all the video that's being consumed through phones today I kinda understand why most people prefer a larger screen too. I have friends who has neither tablets nor computers at home and if I didn't have both of those I might even prefer a 6 inch screen myself.

Yeah, I'm using the Sony Xperia 10 IV right now and while it is better than many phones I'm reminded of how much better the XZ1 Compact feels in my hand everytime I use it to startup some music.
129mm vs 153mm in height and 65mm vs 67mm in width - it's amazing how much a difference those 2.4cm in height does for me.

That's a cool project and it did have a small screen, I give you that. Might be nice to only have to worry about answering the phone for 5 hours a day too. ;-)

Vaultwarden is a nice self hosted bitwarden alternative
https://github.com/dani-garcia/vaultwarden

Some prefer using KeepassXC and sync the database between devices
https://www.ctrl.blog/entry/keepass-vs-bitwarden-server.html

Ah, that sucks and complicates things. One can only hope that doesn't stop the US phones from getting them then.

I was just about to say that this thread needs more Harvey.

If they've already spent the developer time to create a security update for the EU market then I imagine they will push it to phones in the US too.

If your phone can survive until next summer it might be a good idea, EU is forcing some consumer friendly requirements which I imagine will give you a wider availability of models with five years of updates.
https://energy-efficient-products.ec.europa.eu/product-list/smartphones-and-tablets_en

Ecodesign requirements will apply to mobile phones and tablets put on the EU market from 20 June 2025 onwards, including:

1. resistance to accidental drops or scratches and protection from dust and water
2. sufficiently durable batteries which can withstand at least 800 charge and discharge cycles while retaining at least 80% of their initial capacity
3. rules on disassembly and repair, including obligations for producers to make critical spare parts available within 5-10 working days, and for 7 years after the end of sales of the product model on the EU market
4. availability of operating system upgrades for longer periods (at least 5 years from the date of the end of placement on the market of the last unit of a product model)
5. non-discriminatory access for professional repairers to any software or firmware needed for the replacement

I believe that both proprietary non-free systems and fully free systems can exist and that having licensing alternatives like GPL, LGPL and MIT gives the developer options for specifying how their software is to be used.

The movement towards using MIT or LGPL instead of the full GPL for libraries thus allowing the developers using the libraries the freedom to choose what license their software should use is one I can stand behind.

If someone builds a FLOSS turbotax competitor and don't want anyone to use their hard work and fork it into a commercial and proprietary product then I believe there should be a license for that.
If they rather earn money from it and copyrights their code instead that is also their prerogative.
The middle-ground where they create a free turbotax competitor with a license that allows others to fork it into a proprietary software should also be possible - although I personally don't see the allure.

Oh, as someone who hates doing gift runs this is a great tip!

That question is kind a rabbit hole and not one I feel confident in going down.

Free as in freedom, not as in free beer.
The real world implications of non-free software is that other's can't run, copy, distribute, study, change and improve the software.

I like having computing alternatives that are free from corporate control and believe that the hardliners like FSF helps us keep those alternatives alive. I realise that those alternatives are in many ways worse and that a lot of hardware today requires the vendor blobs to work. When/If corporations push their control even further I want those alternatives to be around.

And you really should pay for winrar. ;-)

Not in this case, the tests they're running doesn't need the vendor blobs in those testing folders.

Generally I agree with Debians changes to include nonfree firmware in the default images and making the "completely free" images the non-default version. I do think maintaining and having completely free distro versions to be a good thing though.

The whole situation is really unnecessary because none of the things that we're testing really requires those vendor blobs.
We're just testing the basic vboot and CBFS structures in those images, the file contents are not really relevant as long as they match the signatures.
So I think the easiest option here is to just remove the offending CBFS files from those images / overwrite the offending FMAP sections with zeroes.

https://issuetracker.google.com/issues/374385985

In this case the binaries with the nonfree software seem be completely unnecessary, so why not keep it free?

https://mail.coreboot.org/hyperkitty/list/coreboot@coreboot.org/thread/6JI7KTJ3QVK6Q5BLNWREX2IBVZP7GCLP/

They were put there for some testing and from their mailing list it sounds like it will be removed as it's unnecessary.

Apologies that this has caused problems for you.
This is just some old test data used to confirm that the parser in the command line utility works, and I don't think anyone thought about the redistribution legality implications of putting those images into the repo.
I agree that it's not a good situation and we should try to fix it.

There is no real reason for these binaries to be in those test fixtures — the point of the tests is just to verify parsing for vboot data structures, the actual contents of the file are not really relevant.

• Julius Werner, member of the Advisory Group

https://mail.coreboot.org/hyperkitty/list/coreboot@coreboot.org/thread/6JI7KTJ3QVK6Q5BLNWREX2IBVZP7GCLP/

edit: "there is a general advisory committee made up of any individuals who wish to help out and discuss their thoughts with the leadership board. This is done at bi-weekly meetings, which all members of the project are invited to attend and contribute."
https://coreboot.org/leadership.html

That's a hilarious and wonderful solution! How much quicker is she with that trick?

Take a deep breath, make yourself a cup of tea and go through your notes for the exam. Ace the exam!
Then think about which lemmy server you want to start your new stardew valley community on and what your community rules should be.

The profits gained from sales of .io domains has come under increasing scrutiny given that the UK's control over the archipelago itself is under threat.
Chagossian refugee groups (former inhabitants forcibly removed in the 1960s and 1970s) petitioning the UK government for the right of return have recently extended their grievances to the return of the .io domain as well (Chagos Refugees Group United Kingdom et al. vs. Internet Computer Bureau Limited Citation 2021).
Additionally, Mauritius is also attempting to gain control over .io by petitioning IANA for redelegation (Bowcott Citation 2022).
However, while these groups fight for control over the .io domain, a recent UN ruling challenging British sovereignty over the island threatens the existence of the ccTLD itself.

https://www.tandfonline.com/doi/full/10.1080/23738871.2023.2238723

While I agree with you in that ICANN will probably save .io through some policy change it isn't as easy as just saying "screw all our policies, this ccTLD is now a gTLD." considering the fighting going on regarding it.

https://x.com/TheDeniseCrosby/status/1092268606711197698
https://x.com/TheDeniseCrosby/status/1093037262856572928