Interesting, hadn’t heard of it before today, but guess I don’t look at European car brands that often anyways

Ah I mean fair enough :) I don’t keep up much with car brands and ownerships, but still TIL haha

Huh, didn’t realize Volvo was primarily owned by a Chinese company, you got me there lol, genuinely always thought they were standalone and therefore a Swedish company

Colour me intrigued. I want more manufactures that go against the norm. If they put out a generic slab with normal specs at an expected price, I won’t be very interested, but if they do something cool I’m all for it

Except I just noticed the part where it’s developed by Meizu so nevermind probably will be a generic Chinese phone

Hope it comes out soon that’s some nice QOL updates :)

Very interesting they wouldn’t let him film the camera bump… it must have some kind of branding on it like Hasselblad? Or maybe they’ve secretly found a way to have no bump! One can dream…

By far the biggest pain point of Sony… their software is clean stable and fast, with acceptable release cadence, but their promise of 2 years is completely unacceptable in this day

Wish there was any way at all to influence them

deleted by creator

Not a glowing review that this is accidentally not a reply to a comment. :p

Not much detail in the article but at least it’s not set for phones for now

Does it not? I’ve never received a single spam message on telegram in my 6 years of use :S

Even Sony dropped theirs, miss it so much

Thanks for the comment! Yes this is meant more for your personal projects than for using in existing projects

The idea behind needing a password to get a password, totally understand, my main goal was to have local encrypted storage, the nice thing about this implementation is that you can have all your env files saved and shared in your git repo for all devs to have access to, but only can decrypt it if given the master password shared elsewhere (keeper, vault etc) so you don’t have to load all values from a vault, just the master

100% though this doesn’t cover a large range of usage, hence the name “simple” haha, wouldn’t be opposed to expanding but I think it covers my proposed use cases as-is

definitely for sure this time we promise

link is broken

but content in the title is enough, just sad especially as an owner of a TicWatch Pro 3 Ultra… been gathering dust in my drawer waiting for WearOS 3…

cries in to watch pro 3 ultra

still so sad about the death of blobbies :'(

You could definitely do clever things to obfuscate what you’re doing, but it’s much easier to replicate building the image as there are no external dependencies, if you have docker installed then you can build any docker image

When you make a docker image and push it to dockerhub all of the instructions it took appear there so it’s very transparent, also super easy for any person to build it themselves unlike executables, just download the Dockerfile and run a single command

Besides the obvious of telling your users to build the exe, have you considered alternative distribution methods like docker?