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)?
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.
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.
> and you literally heat each other so actually-fair costs are fuzzier
What you're describing is closest to "actually fair" I think we can get. A neighbour of someone I know leaves their apartment empty for long periods of time and when they're gone they just shut off their heating completely and leave all of their neighbours to pick up the bill - each apartment has their own heating system but they share walls, floors, and ceilings.
The backup heat source of a heat pump is extremely nice to have if your furnace craps out, just shut off the gas supply and let the heat pump do its job. If I had to replace my A/C condenser I’d probably opt for a heat pump to replace it so that I’d have that option too.
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).
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?
The huge switch from SMS to WhatsApp in Europe was well done before they were acquired by Facebook. By then the damage was already done, because the network effects made it very hard to move away. By now, many people I know also have a Signal account, but it doesn't really get off the ground as long as, say, 30% of every group chat does not use Signal.
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 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.
> key verification - I certainly don't see any of that in Google's "Messages" app!
I do! I have a old-ish but up-to-date and stock Pixel phone, and I see (what appears to be) full E2EE with several text contacts in Messages, with ability to verify keys (which admittedly I have not attempted to use yet). It only works if both devices / all of the devices in a group are fully compatible with the version that adds encryption or newer, but when they do, it just starts working automatically and transparently. AFAIK, that's primarily thanks to Google's work.
I think what we've learned from the rise and fate of current alternative messaging apps and services is that, if we actually want to get the majority of the world's population on modern-quality E2EE for all of their communication, it's going to have to be done gradually and transparently through the apps they already use. Getting everyone to switch to a different app is a pipe-dream that will never happen, at least not thanks to the work of any particular person or company.
Apple is pretty good at privacy and security for people playing within their ecosystem. They seem rather indifferent to any attempts to communicate or interact with anybody without an Apple device. Better than nothing, but not great IMO. Google has many faults in many areas, but I think they're doing awesome work at a difficult and thankless job as far as developing a standard for modern and fully encrypted communications that is actually possible for everyone to switch to transparently, and dragging everyone kicking and screaming into actually using it. Apple just rolled out support for it in beta 4 months ago. Very likely in the next year or so, we may see the majority of texts and group-chats between Android and iOS be actually E2EE without the users needing to do anything besides ordinary OS updates. That will be IMO 80% Google's doing, and 20% Apple's.
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.
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.
>You may modify the software only for non-commercial purposes such as personal use for research, experiment, and testing for the benefit of public knowledge, personal study, private entertainment, hobby projects, amateur pursuits, or religious observance, all without any anticipated commercial application.
Violates clause 3 (Derived Works) and clause 6 (No Discrimination Against Fields of Endeavor) of the Open Source Definition [0].
>You may distribute the software or any part of its source code only if you do so free of charge for non-commercial purposes.
Violates clause 1 (Free Redistribution) and clause 6.
>Notwithstanding the above, you may not remove or obscure any functionality in the software related to payment to the Licensor in any copy you distribute to others.
Violates clause 3.
It is a "source available" license, not Open Source.
Thanks for sharing this! I spoke out of ignorance, having only considered the source code being available but not the licensing. (though I find narrowly defining "open source" to be rather pointless) I haven't tried every open-source Android keyboard, I've been very happy with FUTO Keyboard. Kinda too bad it's not compatible with being shipped with GrapheneOS, but it's also understandable why they'd license it this way.
It is not open source. They use a custom source available license. There's no way any Android distribution would include it. A layman's reading is that FUTO could claim license violation on account of the distribution accepting donations (non-commercial use only) and there's a weird clause about not accusing FUTO of patent infringement.
Right, they are adhering to a definition of open that includes free as in liberty, so licensing matters. What good is it to read the source if I don’t have rights to modify and redistribute?
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.
I'm so thankful that Minecraft has developed it's own ecosystem for modding (I don't like CurseForge but it's MILES ahead of NM, and modrinth is great) and did not rely on NexusMods. Try to install a big modpack in TES, Fallout or Cyberpunk without actually paying for the API access, it's borderline insane.
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)?
reply