wise.com/gb/compare/
atlantic.money/gb/en/
Probably not who you think of, but I like this example. 😅
28.02.2026 14:53
👍 0
🔁 0
💬 0
📌 0
wise.com/gb/compare/
atlantic.money/gb/en/
Probably not who you think of, but I like this example. 😅
It's using MLS, not proprietary. It works cross-platform, even though the initial communication from Apple regarding the beta 1 was strange. However, other features in UP 2.7 and 3.0 aren't available yet, which is a more annoying issue.
Now the sad part, Wikipedia's article is pretty bad too. Lots of confusion due to the terrible job done the press, not trying to really understand what Google did with/to RCS.
Claiming that telcos routinely inspect decrypted TLS to Google infrastructure is quite the insane claim!
And the weirdest part, it references a Reddit thread where people explain precisely the opposite.
Checking out Grokipedia on RCS since I know a thing or two about the topic:
> ... carriers like those using Google Jibe hubs routinely inspecting decrypted payloads to enforce policies, as confirmed in deployment analyses where TLS alone proved insufficient against endpoint access by providers.
Grolar sounds like "fat bastard" in French which is somehow appropriate. 😅
Mais pourquoi la France aurait-elle droit à un traitement spécial?! C'est pas du tout le pays où Apple a commencé à déployer le RCS. Les opérateurs utilisent Jibe comme à peu près tout le monde occidental.
Pas de raison logique que le NO soit temporaire pour une raison technique.
@ericbothorel.fr Développement intéressant, iOS 26.3 beta semble annoncer l'arrivée du chiffrement de bout en bout en RCS, un nouveau paramètre est apparu dans la configuration des opérateurs: SupportsE2EE. Uniquement chez les opérateurs français! Et réglé à "NO".
You know that's a logical fallacy right?
Monads fix this! Or algebraic effects, I assume.
Hey, Google has cut off "guest" access to Jibe in several countries. Typically because phone operators aren't interested in RCS at all, but in Korea it's because Chatting+ is using its own domestic RCS backend. And now iOS is connected to Chatting+, the Korean market is unavailable to Google.
Server-client architecture, partial LSP support, new UI using Compose (the IntelliJ family still depends on Swing).
By 2050 I hope we'd have collectively moved to Zstandard. 😔
From what I could gather (I work at a telco but not on anything related) we have to proactively deregister a SIM, for instance when it gets stolen or we terminate the subscription. I don't understand how your hardware could be blacklisted for both SIMs, it must be by Jibe itself. But why and how...🫠
Could you figure out if the issue happened at the carrier IMS registration step, or deeper with Jibe?
I assume the new board gives you fresh app attest tokens, thanks to a new hardware signature?
In other words, monads are a surefire way to confuse people and fuel misinformation. 😅
In a language like Java you kinda see the opposite, not enough people challenge the cargo culting of bad and outdated practices.
I believe you need parts of the language or its ecosystem that are a bit exotic or niche and seen as advanced for good or bad reasons. It's probably very hard to spread misinformation about Python. But for instance in Typescript, I've seen really bad takes about Effect.
Typeclasses are everywhere, there's no distinction in usefulness between library authors and consumers.
Despite no auto-currying, partial application is possible. Pipes as well, Scala has infix operators that can be inlined. Some people would like first class |> but I honestly don't see the need.
@cascoinfoundation.org @bft.wtf
You guys criticize Tether but do you have a drone show with memes? I didn't think so!
www.youtube.com/watch?v=oogS...
Chartreuse liquor bottles.
It comes from the liquor
Nothing new. People who want to put cryptocurrencies everywhere fundamentally don't understand what they are. It's even one order of magnitude worse with blockchains, usually they don't understand either blockchains or the problem they claim to solve.
It's in a weird spot, if I want slow compilation and memory safety Rust is more mature in many dimensions, and used in spaces that nobody expected earlier.
Re: "modern Swift is simpler Rust" argument: learning curve doesn't look that different given the explosion of features, syntax and keywords.
It's famously so unserious it was granted to Nordhaus for his DICE model about climate change mitigation: "damages are estimated to be 2 percent of output at a 3°C global warming and 8 percent of output with 6°C warming" (talking about worldwide GDP in 2100).
Disable 2G on your phone and also 3G if you can.
These are two different issues:
- Some carriers such as AT&T are moving RCS to their own IMS registration infrastructure, exactly like iOS (hence the updated T&C).
- Google is seemingly cutting Jibe off MNOs that aren't playing ball in several regions.
He was radicalized by linear transformations during first semester algebra class.
It's not about gambling. 😅
The first season was a bit slow but if you can watch both seasons together, the pace isn't too bad. It's always tricky when different timelines are interleaved.
The Apple TV+ show is interesting too!
The fact Quarkus exists in Java shows that backend services aren't a solved problem and my whole point is that the Scala ecosystem was even better positioned in this space.
Outside a couple top tier companies that force a handful of sanctioned tech stacks on every team, the majority are more siloed and allow some diversity. Otherwise every backend dev on Earth would use either Java/Spring or Go, and that's not the case.