Groxx

I've had multiple that do it. they're quite visible in the right light. you can also see it when your yellow cartridge runs out, despite printing exclusively black and white, while the other color ones are full.

"most" might not, I can't claim anything there and EFF claims most don't, when they were checking on it in 2015-2017. I'm pretty darn sure that some do though.

It's also not subject to signal loss issues like anyone who uses a phone is quite familiar with. Unless you have narcolepsy.

The Shepard tone of "progress"

You can use "the" in the original sentence just fine if the pool had been established earlier, like with planning a pool party. Then the pool is the pool that you'd be using, and not simply a pool that will be found at some point in the future.

GET requests can have bodies too, and many low-level APIs will allow it - given how few things seem to be aware of this, you could probably sneak stuff through that way too.

>This leads to passkeys being the perfect fit for a corporate environment, but a poor fit for personal security.

I 100% agree - almost everything about them screams "this is The Ideal Corporate Solution".

This isn't a bad thing, it's nice to have a standard for corporate uses. And the attestation-DRM stuff makes perfect sense there, you already have MDM and it fits with that perfectly....... though not all that differently than using MDM to set up client-side certificates. But app/OS support is better, for some reason. Why didn't they just improve that flow?

For personal use though, they seem outright hostile to people living in the real world with common failure modes. It's outrageously clear that normal people were a distant afterthought - just look at how hostile it was to syncing at the beginning, and how long it took to get key exporting (and how directly hostile they were to anyone building a stopgap in the meantime).

Passwords can move between walled gardens generally very easily (export) or manually in all cases (enter by hand).

Passkeys only very recently got relatively broad support for migrating data (after years of promise and no support at all), and they report (optionally with hardware attestation) what password manager you're using so sites can force specific ones.

I've been using keyboard-based launchers for a couple years now, I really like it. None quite yet feel perfect to me, but Olauncher has lasted the longest: https://play.google.com/store/apps/details?id=app.olauncher

If you set up a swipe to launch another launcher, you can have all your widgets there, as sometimes that's nice for a multi-app overview of Stuff™ at a glance.

1b: the docs are a pointless ritual that sometimes ends up taking multiple times longer than implementing, and if too many people see it they start asking things like "what are your KPIs" and "when are your deliverables synergized" and "have you written the oncall runbooks yet? what's the protocol spec for that?" and "what's your projected uplift". if it's less than 5 pages of text, you're dinged on perf because your documents aren't detailed enough. for projects like "we should add a small in-memory cache to this slow area".

so you're best off writing a small one that you do your best to hide, and make a few fancy ones per season with graphs and absurd will-never-be-implemented details for the higher-ups to be distracted by.

Yes! I am indeed, thank you! Bottles has been useful, though I haven't used it in years.

(edit: removed because I was confusing Bottles and Boxes, no need to leak wrong ideas)

particularly if you want to support all of the message-body features, of which there are MANY. it's very business-comms oriented.

I broadly expect third-party RCS apps to drop that though, like how essentially none support all of MMS. did you know MMS supports slideshows (I built support for this once)? 3d objects (mimetype model/gltf+json)? "timed text" (mimetype text/mp4)?

For anyone unfamiliar with this strategy: it's literally just "clone from a /path".

Part agreed (E2EE by default so broadly is a great achievement), part "I think this is likely a massive communications power-grab on Google's part and not all that altruistic". They control almost literally all of the servers and the only app nowadays (Samsung's is shutting down), globally, outside of Apple. Soon they will see a massive portion of the world's contact graph in near real time due to presence checking.

I am very glad to hear they're finally exposing some of those details though. Now they just need to open it up to third parties, like the original reference implementation did over a decade ago, so we don't need to blindly trust them as much.

Generally yes. But also it is sometimes like half the cost or less for comparative heating power, and for air-heating an apartment in the middle simply doesn't need anywhere near as much, and you literally heat each other so actually-fair costs are fuzzier. Gas bills in places that didn't include it would often be like $15/month in the middle of winter, hardly worth the administrative and hardware costs.

One of the houses I rented many years ago didn't even have metered gas. We paid a "hookup" fee to the city (like... $40/quarter?), and they didn't care how much we used, as long as it wasn't for commercial purposes. I assume the city had something for detecting extreme use or leaks, but that's probably it. It was a somewhat strange property though.

Yep - where I am, it's moderately more expensive to use our heat pump to heat the house (at basically any time of year) than to use the gas furnace, and approximately nobody has a heat pump water heater. And with datacenters trying to move in, that equation may get even worse in the future. Gas is surprisingly, weirdly cheap, often not even metered in apartments.

Having two options during cold winters can pay for itself with one emergency repair though, or be a massive savings if it can't be fixed fast enough and pipes burst.

In most ways, yes. E.g. you clean yourself before you get in, so the water remains relatively clean after a few people. Unlike a hot tub though it's drained between uses, so it doesn't really have some of the nastier issues that hot tubs can acquire (nor does it need higher chlorine content to mitigate it).

Year, back prior to the Zuckification I'd say it was a very clear upgrade for everyone in essentially every way. Dirt cheap (much less than even minimal texting), installable everywhere, adopted solid E2EE far ahead of basically every major player (2016!), it was great. USA had everything worse for a long time, and many things still are.

But once it landed in Zuck's hands, I no longer trust it one bit. Abandon ship.

It depends heavily on country, yes. USA is extremely light on WhatsApp, and MMS use is widespread (and has been free for a long time now, and SMS even longer). RCS is a mostly silent upgrade for USA.

I'm not sure which of the two is better tbh. Utterly dominated by a Facebook-owned system, or using something that's crappy enough that people spread out to a variety of systems?

It has it in its current documentation (maybe 3.0 too? I forget, but it's new this year), and Apple and Google have had messages to themselves encrypted for a while (but not to each other, which is what the RCS docs are intended to resolve). It took many years to get it documented though (despite loudly claiming RCS is more secure the whole time), and AFAIK none yet implement it. Definitely none with all the documented things it needs to show to be compliant with the spec I read, e.g. key verification - I certainly don't see any of that in Google's "Messages" app! Though hopefully that will all change.

But honestly, in a non-open ecosystem, can you really trust that the near-exclusive two major players are actually playing by the rules? Apple has been relatively protective of its users on privacy stuff, but I've lost all trust in Google at this point.

Ah, yeah, agreed - "source available" fits that much better. I'm pretty sure that's the same for immich (which is also from FUTO).

Thank you for the details! That lays it out nicely for anyone else passing through.

The source is here: https://gitlab.futo.org/keyboard/latinime

Featured prominently in the "Source Code" container on https://keyboard.futo.tech/

AFAIK everything FUTO makes is open source? I haven't seen a counter-example (I have not looked hard though!), and https://futo.tech/about claims the following:

>All FUTO-funded projects are expected to be open source or develop a plan to eventually become so. No effort will ever be taken to hide from the people what their computers are doing, to limit how they use them, or to modify their behavior through their software.

Spam is, rather definitionally, undesired marketing.

If they don't desire it, it's spam for them. And they rather clearly do not desire it.

(You could also go with the stronger "unrequested marketing" definition, which makes this even more "definitely spam". CAN-SPAM rules define it this way, so that seems fair too)

Probably speaking as someone who has used nexusmods in the past decade. Their monetization stuff is on the "lolwhat, that's kinda excessive" side of things.

Spotify definitely has a better claim for "mainstream", but Epic's store/game-app takes the cake for me. Stunningly slow and bad.

And accessibilize it. Pixel perfect per zoom level per language per font variant per font.

Don't forget increased-contrast too!

Diamond hands pays off at last, congrats on the windfall!

It very much depends on the people and the relationship. Through many years, I've swung a few hundred$+ in either direction with a bunch of people, thousands with a couple.

I much prefer zero stress - if money is tight, we just don't do expensive stuff, or steal the bill before they have a chance to pay. Mostly that means we stay cheap until we can safely cover multiple people if needed (running your safety-buffer low enough that you can't do that is a terrible idea anyway).

It's so weird to me that this kind of thing wasn't a day-1 kind of thing. Android's has loads of issues too[1], not least of which is that you need to manually enable it.

1: you can't get access to actions or details in the history (e.g. no long-press to change settings), nor does it show you ones you didn't dismiss by hand afaict (I've been having Discord notifications disappearing almost immediately after making a noise, but there's nothing in history even though I saw it for its whole half-second existence because it popped over my screen).

Prefetching applies to SSDs too, and that's generally sequential in some sense.