whatsapp, facebook messenger, imessage all support multi-device and it's pretty convenient, in fairness to telegram they launched a bit before double ratched was invented, but still, they've had over a decade to switch to it...
That's still one device. If you turn the primary phone off, the secondary device stops working. WhatsApp just proxies everything through the primary device, it's like WhatsApp Web.
They used to, but that hasn't been true for a few years now.
Now it uses the Signal protocol's native multi-device capabilities, specifically in the "key per device" variant (unlike signal itself, which uses "key per account" if I'm not mistaken).
> You can now use the same WhatsApp account on multiple devices at the same time, using your primary phone to link up to four devices. You’ll need to log in to WhatsApp on your primary phone every 14 days to keep linked devices connected to your WhatsApp account.
It's not true for Signal either. Why don't you try it for yourself instead of spreading outdated (at best) information? Signal supports native multi-device capabilities without relaying everything through the "primary" device.
Messenger seems to be properly multi-device, but you pay for this by some PIN code bullshit (maybe they removed that, I haven't seen a popup about this for over a year now?) and having to sync chat history in the background, through a process that is, of course, broken and unreliable.
I'm actually still jaded about this. Messenger worked fine before they broke it by introducing E2EE; it took years for them to fix the problems this caused (at least the ones that were immediately user-perceptible).
yeah messenger still has the pin code thingy, i'm curious why they do it at all that way, can't you just have your keys on fb servers encrypted with another set of keys derived from your password, which is much stronger than a 4-6 digit key?
It's still broken if you're like me and you clear cookies
"Let's take people's years-long history between each other and just utterly break it. Why? 'privacy'" but they've never cared about it, they're opportunistic fucks. It's Zuckerberg's company to do with it "as he wishes" https://news.ycombinator.com/item?id=16770818
It's called iMessage. It's possible, Telegram just doesn't care. All their differentiating features (large groups, channels, device sync) is directly enabled by the lack of encryption.
they do have encryption, just not e2ee, and in fairness to them, it doesn't make sense to have e2ee on a channel or a group with 100k ppl in it, also device sync is possible with e2ee, it's just a slower
What are you talking about? WhatsApp, iMessage, and Signal all have multi-device support and are E2E encrypted, just to name a few very popular options.
EWM implements a Wayland compositor as a native thread spawned by a dynamic module in Emacs, it's a full compositor within the Emacs process: https://codeberg.org/ezemtsov/ewm
So it is architecturally possible (but infeasible in plain Emacs Lisp).
This one could technically be written in plain Emacs Lisp, but I'm happy to use something that already has all the XML codegen stuff for Wayland figured out. Dynamic modules work pretty well, fwiw.
Oh, reka looks interesting. Thanks for linking it. I don't disagree with you about dynamic modules, I just think that EWM's architecture shouldn't be necessary. (In which I think we agree?)
It is probably country and language dependent, I think. I don't know anyone under 40 who doesn't write in cursive (in Russian), and for other languages I personally also write in cursive (and learnt that in school). I'm in my 30s.
OP double negated - cursive is the norm for Russians of all ages.
Russian cursive is actually not that bad to read for the most part. Russian “print” is super awkward because all the characters are very angular.
There are some differences between generations (younger generations are more likely to write “т” in handwriting whereas the “correct” form looks more like a Latin “m”, but with obvious examples excluded (like the above), it just takes learning as a separate alphabet.
I know. I always feel utterly embarrassed when Russian-speaking friends write down a movie title for me, and I have to ask them to rewrite it in block capitals.
Okay, so which hardware are you buying that isn't using any Chinese components?) I don't think the empire can make this kind of hardware from scratch without China at the moment.
Killing off free repos is not going to happen. That would be a suicide move on the level of the Digg redesign, or Tumblr's porn ban.
It kind of would be good for everyone if they did do it though. Need to get rid of this monopoly, and maybe people will discover that there are alternatives with actually good workflows out there.
People go through all this trouble to host convoluted chat systems, and all this time IRC is right there. There's modern servers like Ergo and modern clients like Halloy (or for the JavaScript addicts: Convos, The Lounge, Kiwi, ...) providing all the multi-device history sharing and emoji reactions you could need. All on top of a super simple, extremely battle tested protocol.
But according to https://ircv3.net/software/clients, none of the clients you mentioned actually support emoji reactions (draft/react), and other features like multi-line messages and image uploads are likewise extremely limited in server/client support. So, for the time being, you can't use these features if you want to actually be interoperable with existing IRC users and their clients. Sounds like if you want decentralized, Matrix is still the better bet.
These weird anti-Graphene posts confuse me. I use GrapheneOS, fwiw, and I believe some things the project does (like its attacks on F-Droid) are misguided for orthogonal reasons.
However, it all makes sense from the perspective of Graphene not attempting to be a general purpose OS like Lineage, but explicitly a security focused OS. Security is often in conflict with what the average consumer wants, and they can go use Lineage or whatever.
It's like writing lots of comments complaining about OpenBSD devs coming across as grumpy and refusing to support Bluetooth. That is part of their value proposition! You're just not the target audience and that is okay.
Most if not all of their attacks are inexcusable. Calling a competing OS, CalyxOS, nazi sympathizers is unacceptable and when I first read that I started seeing the red flags.
Nothing is open about GrapheneOS aside from the source code. We officially know nothing about the leadership, their current plans, what their finances look like or even who this new mysterious OEM is.
not much in the parent comment is anti-graphene. it's probably the best available option for a mobile OS right now.
the sentiment is that the dev team - specifically one zealot - does not engage politely/rationally/transparently in any public forum, which undermines the image of the OS as a whole.
I've only seen the carrier locked phones and long-term contracts in a handful of countries. I've lived in a lot of countries on three continents.
In many places the default is prepaid SIMs with separately purchased phones. Sometimes the prepaying can be automated (e.g. in Russia), sometimes it involves you physically going to a shop once a month or so (e.g. in Egypt).
There are many pragmatic reasons to do what Anthropic does, but the whole "soul data" approach is exactly what you do if you treat "the void" as your pocket bible. That does not seem incidental.
Key distribution is just too hard. I think we won't get a messenger for non-tech people that works well with multi-device and E2E basically ever.
reply