Now in theory, you could have a DC-like app that uses other protocols to add extra features, but keeps email protocols for text delivery and attachments, and whatever else it can do. But I'm guessing there's reasons OG Jabber wasn't built around email protocol. Just like there's reasons OG Twitter and the fediverse weren't built on XMPP.
But maybe a graceful fallback to email delivery could be a thing in for private messages in apps that use realtime federation protocols?
(3/3)
@strypey Coincidentally I'm trying out Spike email right now. It is EXACTLY what I was looking for. Too bad there's no FOSS equivalent that I know of.
@cwdolunt
> trying out Spike email right now
AFAICT this is completely proprietary, and bundling an "AI" chatbot. Not for me, thanks.
> Didn't know about delta chat. I'll have to take a look
I've been using it for a few years. Managed to get a few family and friends to try it, but it didn't stick. Still useful to me though, because I can exchange ordinary email with them using a chat-like interface.
> AFAICT this is completely proprietary, and bundling an "AI" chatbot. Not for me, thanks.
Yep, I know, though most of the AI stuff requires a subscription, so I can ignore it. Spark email has a similar interface, but is also proprietary and full of AI crap. If there was a FOSS alternative to either that would be wonderful.
>I can exchange ordinary email with them using a chat-like interface.
That there is what I'm looking for, email grouped by person, not message or thread.
MS/MMS is slated to be replaced with “Rich Communications System” (RCS), a new standard for sending electronic text-based messages between phones.
...
You have to basically be a phone company and pay the GSMA tens of thousands of dollars per year to be a member in order to have the privilege of implementing an RCS based system. That’s not open or democratic at all."
#AdamZLein, 2022
"... phone numbers are recycled. If you were to get a new phone number today, it probably belonged to someone else already. Thusly, you’re going to get all of the text messaging notifications and calls for that person.
#AdamZLein, 2022
(1/?)
"Plus any apps you sign into with a phone number will probably hijack that previous person’s account, too. I was able to easily do that with WhatsApp, Signal, & Telegram since those apps are heavily (and stupidly) dependent on phone numbers. "
@Adam, 2022
Hang on, are you saying you were able to hijack people's Telegram and *Signal* accounts using recently issued SIMs with recycled phone numbers?!
@strypey >>Hang on, are you saying you were able to hijack people's Telegram and *Signal* accounts using recently issued SIMs with recycled phone numbers?!
Yes, by accident even. Apps that use phone numbers for registration just give you everything associated with that # if you get the SMS messages. I had full access to someone's lottery app too.
"Instead of simply typing a message to your friend and pressing the send button, you have to spend some cognitive energy trying to remember which messaging app that friend prefers to use, then switch to that app, find the message thread, THEN you can pick up the conversation."
@Adam, 2022
(1/?)
If you want to go back and reference or search for something in some conversation you had with someone, you have to spend more cognitive energy trying to figure out which app and which service that conversation took place in. You’ll be lucky if that app even has a functional search, and you can imagine how much cognitive energy you’ll have to spend looking for it."
#AdamZLein, 2022
(2/?)
The smartest messaging method is not a segregated mess of WhatsApp, Signal, Telegram, SMS, Slack, Teams, Facebook, Instagram, WeChat, etc.
This sort of (theoretically) avoidable cognitive load is especially taxing for those of us who are neurodivergent, and already experience more load day-to-day than the average neurotypical. Solving the chat app proliferation problem is even more urgent for us.
(3/?)
@strypey They dod not hijack a signal account with just a phone number, recently
Signal uses PIN numbers too.
