> I'm security conscious and made sure to disable all the data collection I could find in the companion app before removing my account, turn off remote access services, dig through the infotainment to turn off what I could, etc.
Android Auto, Apple CarPlay, OEM mobile app...Bluetooth??
Consider the business case of leased Comcast modems broadcasting open side-channel xfinitywifi SSIDs...essentially everywhere.
I'm active in many art communities on the web for whom being able to view and share lossless images are table stakes. Also many other communities for which being able to view and share lossless screen captures is fundamental.
I can accept a claim that JPEG-XL is not the best format for it, or that it is good, but not worth the complexity and extra surface area it introduces. I can not accept a claim that "lossless just isn't very useful on the web".
I'm confused by this. I remember genetically modifying E. coli to glow in the dark in high school. You can apparently buy a kit to do it online for $39.99 USD.
I'm not suggesting that making bacteria glow in the dark is the same as making arbitrary changes to a virus. At the same time, do you really need $100M of automated freezers and cell culture rooms? Do you need to synthesise a whole virus? Presumably you could just find a building in the desert, shoot anyone who goes near it, feed the past decade of gain-of-function research into Qwen, splice stuff into viruses based on the most promising leads Qwen gave your biologists, then infect some immunosuppressed political prisoners and see who dies fastest.
I would have thought the main thing stopping people is that this is a clearly stupid thing to do and offers little strategic advantage.
I feel like JPEG XL could be a good RAW format for mirrorless cameras... something with huge flexibility but with the perk of being easier to view casually on other devices. And then that in turn could make it a more useful web format? Camera vendors are of course notoriously proprietary/stubborn.
The second paragraph doesn’t follow from my question, because it assumes JPEG XL does become useful on the web. The author believes AVIF is too far ahead already.
All I care about is my favourite podcast app, Pocket Casts, which Automattic bought in a dumpster fire a few years ago.
But even if I don't personally use WP, the fact that something like 25% of the web runs on software which this lunatic has this much control over, is problematic in itself.
How are these models being used to solve all these problems. Is it just "please solve this problem", "keep trying" repeatedly in a loop, or is there are more grounded workflow?
Last month, I bought two pairs of sneakers: one was a full leather design made in Spain, the other was a leather/cloth combination (Italian design, I'm not sure where they are made). Both are comfortable, seem to be of very good quality and look premium. The price of these two pairs together was less then one Nike pair made of synthetic materials.
This was in Novi Sad, Serbia. I don't know what's going on around the world, but if this anecdote is of any indication, Nike is simply too expensive for the (lack of) quality they have.
I've been working on anti age verification/surveillance projects lately. I put together this thing I call The Mandating Honeypots Project and it shows how anyone with an internet connection and copy + paste skills can trick Linux D-Buses with a simple Python script, proving that if companies want to verify your age by asking the D-Bus interface, it's easy to just tell it to always send 18+, making the whole thing useless. The only reason you'd want ID verification is so you can create the world's biggest and sweetest honeypot.
In that project, I also proposed a tool with heavily redundant password protection that parents could use to keep kids from tampering with the service so the government can stop saying that this is for the kids. I'm planning on doing a mobile device version and/or an ID database focused version, but that's still in the planning phase.
I also want to do a Windows version when they release their 'GetUserAgeRangeAsync' API, but idk if I'll be able to. Windows is always a pain to work with.
It'd be nice if someone had advice or ideas to share, too.
Fair. And yes, the Wall-E problem still stands. We already have dark factories though. Can we design machine repairable factories that produce machines to repair machine repairing factories? I suspect we'll find out very soon.
Android Auto, Apple CarPlay, OEM mobile app...Bluetooth??
Consider the business case of leased Comcast modems broadcasting open side-channel xfinitywifi SSIDs...essentially everywhere.