#instantmessenger — Public Fediverse posts

Chemnitzer-Linuxtage-Nachlese Teil 1:

Das Datenschutz-Problem mit Push-Benachrichtigungen – sehr eindringlich und unterhaltsam erklärt von Merle Fäller

Ich wollte nur Zulip-Notifications auf dem Handy. Also habe ich angefangen, selbst was zu bauen – und bin in ein Rabbit Hole gefallen.
Dieser Vortrag erzählt die Geschichte, wie ich versucht habe, ein Problem zu lösen – und dabei verstanden habe, wie Push-Notifications wirklich funktionieren. Warum mein erster Ansatz nicht skaliert. Warum fast jede App Firebase oder APNs nutzt. Warum selbst Signal bei Google anklopft. Und warum das seit dem Wyden-Brief von 2023 ein dokumentiertes Privacy-Problem ist: »We kill people based on metadata.«
Ich zeige, welche Alternativen es mit UnifiedPush und ntfy gibt, wie ich eine Bridge für Zulip gebaut habe, und warum das gleiche Problem auch für Prometheus-Alerts, Grafana-Notifications und CI/CD-Pipelines gilt. Und was das mit digitaler Souveränität zu tun hat.

https://media.ccc.de/v/clt26-143-warum-selbst-signal-bei-google-und-apple-anklopft

#google #notifications #firebaseCloudMessaging #gcm #firebase #fcn #apple #apn #ntfy #UnifiedPush #zulip #messenger #instantMessenger #clt2026

Chemnitzer-Linuxtage-Nachlese Teil 1:

Das Datenschutz-Problem mit Push-Benachrichtigungen – sehr eindringlich und unterhaltsam erklärt von Merle Fäller

Ich wollte nur Zulip-Notifications auf dem Handy. Also habe ich angefangen, selbst was zu bauen – und bin in ein Rabbit Hole gefallen.
Dieser Vortrag erzählt die Geschichte, wie ich versucht habe, ein Problem zu lösen – und dabei verstanden habe, wie Push-Notifications wirklich funktionieren. Warum mein erster Ansatz nicht skaliert. Warum fast jede App Firebase oder APNs nutzt. Warum selbst Signal bei Google anklopft. Und warum das seit dem Wyden-Brief von 2023 ein dokumentiertes Privacy-Problem ist: »We kill people based on metadata.«
Ich zeige, welche Alternativen es mit UnifiedPush und ntfy gibt, wie ich eine Bridge für Zulip gebaut habe, und warum das gleiche Problem auch für Prometheus-Alerts, Grafana-Notifications und CI/CD-Pipelines gilt. Und was das mit digitaler Souveränität zu tun hat.

https://media.ccc.de/v/clt26-143-warum-selbst-signal-bei-google-und-apple-anklopft

#google #notifications #firebaseCloudMessaging #gcm #firebase #fcn #apple #apn #ntfy #UnifiedPush #zulip #messenger #instantMessenger #clt2026

Chemnitzer-Linuxtage-Nachlese Teil 1:

Das Datenschutz-Problem mit Push-Benachrichtigungen – sehr eindringlich und unterhaltsam erklärt von Merle Fäller

Ich wollte nur Zulip-Notifications auf dem Handy. Also habe ich angefangen, selbst was zu bauen – und bin in ein Rabbit Hole gefallen.
Dieser Vortrag erzählt die Geschichte, wie ich versucht habe, ein Problem zu lösen – und dabei verstanden habe, wie Push-Notifications wirklich funktionieren. Warum mein erster Ansatz nicht skaliert. Warum fast jede App Firebase oder APNs nutzt. Warum selbst Signal bei Google anklopft. Und warum das seit dem Wyden-Brief von 2023 ein dokumentiertes Privacy-Problem ist: »We kill people based on metadata.«
Ich zeige, welche Alternativen es mit UnifiedPush und ntfy gibt, wie ich eine Bridge für Zulip gebaut habe, und warum das gleiche Problem auch für Prometheus-Alerts, Grafana-Notifications und CI/CD-Pipelines gilt. Und was das mit digitaler Souveränität zu tun hat.

https://media.ccc.de/v/clt26-143-warum-selbst-signal-bei-google-und-apple-anklopft

#google #notifications #firebaseCloudMessaging #gcm #firebase #fcn #apple #apn #ntfy #UnifiedPush #zulip #messenger #instantMessenger #clt2026

Chemnitzer-Linuxtage-Nachlese Teil 1:

Das Datenschutz-Problem mit Push-Benachrichtigungen – sehr eindringlich und unterhaltsam erklärt von Merle Fäller

Ich wollte nur Zulip-Notifications auf dem Handy. Also habe ich angefangen, selbst was zu bauen – und bin in ein Rabbit Hole gefallen.
Dieser Vortrag erzählt die Geschichte, wie ich versucht habe, ein Problem zu lösen – und dabei verstanden habe, wie Push-Notifications wirklich funktionieren. Warum mein erster Ansatz nicht skaliert. Warum fast jede App Firebase oder APNs nutzt. Warum selbst Signal bei Google anklopft. Und warum das seit dem Wyden-Brief von 2023 ein dokumentiertes Privacy-Problem ist: »We kill people based on metadata.«
Ich zeige, welche Alternativen es mit UnifiedPush und ntfy gibt, wie ich eine Bridge für Zulip gebaut habe, und warum das gleiche Problem auch für Prometheus-Alerts, Grafana-Notifications und CI/CD-Pipelines gilt. Und was das mit digitaler Souveränität zu tun hat.

https://media.ccc.de/v/clt26-143-warum-selbst-signal-bei-google-und-apple-anklopft

#google #notifications #firebaseCloudMessaging #gcm #firebase #fcn #apple #apn #ntfy #UnifiedPush #zulip #messenger #instantMessenger #clt2026

Chemnitzer-Linuxtage-Nachlese Teil 1:

Das Datenschutz-Problem mit Push-Benachrichtigungen – sehr eindringlich und unterhaltsam erklärt von Merle Fäller

Ich wollte nur Zulip-Notifications auf dem Handy. Also habe ich angefangen, selbst was zu bauen – und bin in ein Rabbit Hole gefallen.
Dieser Vortrag erzählt die Geschichte, wie ich versucht habe, ein Problem zu lösen – und dabei verstanden habe, wie Push-Notifications wirklich funktionieren. Warum mein erster Ansatz nicht skaliert. Warum fast jede App Firebase oder APNs nutzt. Warum selbst Signal bei Google anklopft. Und warum das seit dem Wyden-Brief von 2023 ein dokumentiertes Privacy-Problem ist: »We kill people based on metadata.«
Ich zeige, welche Alternativen es mit UnifiedPush und ntfy gibt, wie ich eine Bridge für Zulip gebaut habe, und warum das gleiche Problem auch für Prometheus-Alerts, Grafana-Notifications und CI/CD-Pipelines gilt. Und was das mit digitaler Souveränität zu tun hat.

https://media.ccc.de/v/clt26-143-warum-selbst-signal-bei-google-und-apple-anklopft

#google #notifications #firebaseCloudMessaging #gcm #firebase #fcn #apple #apn #ntfy #UnifiedPush #zulip #messenger #instantMessenger #clt2026

The history of #AOL #InstantMessenger.

The public interest might be obvious and the developers might be dying to build it, but ultimately, given the chance, corporate greed wins and our best ideas get delayed.

https://mashable.com/archive/aim-history

RE: https://mstdn.social/@rysiek/116007605131589165

#Signal is down. Time to learn #distributed #instantMessenger such as (in no particular order): #SimpleX, #XMPP such as #Conversations, , #DeltaChat, #Matrix (i.e. #Element or #FluffyChat)

Fast alle nutzen Messenger-Dienste. Vor allem einen. (Statista, Info + Kurzkommentar) #Messenger #InstantMessenger #MessengerDienste #Whatsapp #Telegram #Signal #Facebook #GoogleChat #IT #WWW #Internet #Technik #Gesellschaft

https://derwahlberliner.com/2025/12/12/fast-alle-nutzen-messenger-dienste-vor-allem-einen-statista-info-kurzkommentar/

How about I disable the whole thing? Screw WhatsApp! Screw Meta!

#BanMeta #BanWhatsApp #BanAI #InstantMessenger #Friday

WhatsApp has become even more detestable with its forced Meta AI inclusion. I can't stand it.

#BanWhatsApp #BanMeta #BanAI #Friday #InstantMessenger

We need a new #InstantMessenger something that's not #WhatsApp, #Telegram or #Signal.

There should be indexers that act as a phone books, but at the same time, people can bypass that by directly adding contacts.

All chat history and groups are peer 2 peer and are stored like torrents with the extended backup being self-hostable.

Recent chat history (up to 30 days) can be stored on the indexer, though they're encrypted and so the server is blind to what's in them. They should explicitly be opt-in.

Whenever a user adds a new client (device) to private chat groups, all conversations recipients should have to approve in order for them to see the chat history.

It should also have all the bells and whistles, like emoji, stickers, groups, channels, etc.

#messaging #communication #DecentralisedTech #DecentralisedWeb #DecentralisedCommunication #DecentralizedTech #DecentralizedWeb #DecentralizedCommunication #SelfHostable #SelfHosted #SelfHost

We need a new #InstantMessenger something that's not #WhatsApp, #Telegram or #Signal.

There should be indexers that act as a phone books, but at the same time, people can bypass that by directly adding contacts.

All chat history and groups are peer 2 peer and are stored like torrents with the extended backup being self-hostable.

Recent chat history (up to 30 days) can be stored on the indexer, though they're encrypted and so the server is blind to what's in them. They should explicitly be opt-in.

Whenever a user adds a new client (device) to private chat groups, all conversations recipients should have to approve in order for them to see the chat history.

It should also have all the bells and whistles, like emoji, stickers, groups, channels, etc.

#messaging #communication #DecentralisedTech #DecentralisedWeb #DecentralisedCommunication #DecentralizedTech #DecentralizedWeb #DecentralizedCommunication #SelfHostable #SelfHosted #SelfHost

We need a new #InstantMessenger something that's not #WhatsApp, #Telegram or #Signal.

There should be indexers that act as a phone books, but at the same time, people can bypass that by directly adding contacts.

All chat history and groups are peer 2 peer and are stored like torrents with the extended backup being self-hostable.

Recent chat history (up to 30 days) can be stored on the indexer, though they're encrypted and so the server is blind to what's in them. They should explicitly be opt-in.

Whenever a user adds a new client (device) to private chat groups, all conversations recipients should have to approve in order for them to see the chat history.

It should also have all the bells and whistles, like emoji, stickers, groups, channels, etc.

#messaging #communication #DecentralisedTech #DecentralisedWeb #DecentralisedCommunication #DecentralizedTech #DecentralizedWeb #DecentralizedCommunication #SelfHostable #SelfHosted #SelfHost

We need a new #InstantMessenger something that's not #WhatsApp, #Telegram or #Signal.

There should be indexers that act as a phone books, but at the same time, people can bypass that by directly adding contacts.

All chat history and groups are peer 2 peer and are stored like torrents with the extended backup being self-hostable.

Recent chat history (up to 30 days) can be stored on the indexer, though they're encrypted and so the server is blind to what's in them. They should explicitly be opt-in.

Whenever a user adds a new client (device) to private chat groups, all conversations recipients should have to approve in order for them to see the chat history.

It should also have all the bells and whistles, like emoji, stickers, groups, channels, etc.

#messaging #communication #DecentralisedTech #DecentralisedWeb #DecentralisedCommunication #DecentralizedTech #DecentralizedWeb #DecentralizedCommunication #SelfHostable #SelfHosted #SelfHost

We need a new #InstantMessenger something that's not #WhatsApp, #Telegram or #Signal.

There should be indexers that act as a phone books, but at the same time, people can bypass that by directly adding contacts.

All chat history and groups are peer 2 peer and are stored like torrents with the extended backup being self-hostable.

Recent chat history (up to 30 days) can be stored on the indexer, though they're encrypted and so the server is blind to what's in them. They should explicitly be opt-in.

Whenever a user adds a new client (device) to private chat groups, all conversations recipients should have to approve in order for them to see the chat history.

It should also have all the bells and whistles, like emoji, stickers, groups, channels, etc.

#messaging #communication #DecentralisedTech #DecentralisedWeb #DecentralisedCommunication #DecentralizedTech #DecentralizedWeb #DecentralizedCommunication #SelfHostable #SelfHosted #SelfHost

Looking back at #ICQ's Designs throughout time, at the Web Design Museum
https://www.webdesignmuseum.org/?s=icq
#WebDesignMuseum #InstantMessenger #RetroSoftware

Putting a bunch of bridges into Matrix to try and centralize my messaging is really giving me Trillian/Pidgin vibes. :neofox_what:​ Except Trillian/Pidgin were way more straightforward (no shade to Matrix, it's not really what it's meant for).

It's depressing thinking back to when XMPP was super promising and companies were on board to implement it. Instead of that happening, they all teamed up to crush it and messaging has stayed the same level of fragmentation (or, depending on how you look at it, gotten worse) in the meantime.

#Matrix #MatrixMessenger #XMPP #Trillian #Pidgin #InstantMessenger #InstantMessaging

It would be great if #Telegram would allow these things with links/shared stuff:
- group by domain (e.g. "all YouTube links")
- filter seen/unseen (like blue vs purple links on the web)
- filter without interaction/has reaction/has reply an show, which it has (like a personal to do list)
- indicate when the link has been shared before

#InstantMessenger #instant_messaging #selfOrganisation

@m_artigiani Personally, it's not that it's being explained poorly, rather, people are too used to siloed / closed-garden #SNS that they find it hard to get their heads around it.

For example, in the #messenger / #InstantMessenger space, we've had #federation since the late 90s, thanks to #XMPP (formerly known as #Jabber). We didn't encounter this issue, people simply understood it like how people understood email.

Then later, there's #Matrix, which is also a federation. But I haven't heard anyone ask or got confused how it works.

In a way, I would say #Trillian, #PsiIM, #Gajim, and the interoperability of #ICQ and #AIM played a role there.

However, when it comes to SNS, majority of people were never exposed to interoperable SNS. Since #Friendster #MySpace #Hi5 came out, there never was a federated SNS until 2008 when the #Fediverse was born (then called #Identiverse).

The #ATproto / #BlueSky federation is coming in 2024, so we'll see if they'll encounter the same challenges in explaining instances. If they do, or do not (as the BlueSky team are saying they won't have that issue), then we'll know better since we'll have a comparison by then.

For me, I think we've done everything that we can to explain it.

You know those Google and Facebook buttons to log in into a website, which doesn't belong to those big corps, like small blogs.

What if we would have something like a universal #Fediverse login? Imagine logging in with your Mastodon account to comment on blogs, participate in a chatroom or do other stuff...

I really would like to have a chatroom where everyone can login with their fediverse login.

#Chatrooms are things I really miss on the fediverse or does it exist and I don't even know it's existence?

Is this technically possible with the #activitypub protocol and would it make sense?

What do you think?

#question #askfediverse #askfedi #askmastodon #askmasto #chat #communication #instantmessenger

#MessagingLayerSecurity: #IETF standardisiert Protokoll für sichere Gruppenchats

https://www.golem.de/news/messaging-layer-security-ietf-standardisiert-protokoll-fuer-sichere-gruppenchats-2303-173089.html

#MLS #InstantMessenger

How “data-free” messaging app MoyaApp is taking on WhatsApp in South Africa (now also on iOS and macOS)

https://gadgeteer.co.za/wp-content/uploads/2022/10/Screenshot_20221017_201853-400x385.jpg The “data-free” messaging app MoyaApp, which already has six million active monthly users in South Africa, is working hard to become as big as WhatsApp in the country. When an app or website is #datafree […]

https://gadgeteer.co.za/how-data-free-messaging-app-moyaapp-is-taking-on-whatsapp-in-south-africa-now-also-on-ios-and-macos/

https://gadgeteer.co.za/how-data-free-messaging-app-moyaapp-is-taking-on-whatsapp-in-south-africa-now-also-on-ios-and-macos/

Telegram Desktop 2.7 Introduces Limitless Voice Chats, Recorded Chats, and More

https://9to5linux.com/telegram-desktop-2-7-introduces-limitless-voice-chats-recorded-chats-and-more

#TelegramDesktop #chatclient #messenger #instantmessenger

Telegram Desktop 2.7 Introduces Limitless Voice Chats, Recorded Chats, and More

https://9to5linux.com/telegram-desktop-2-7-introduces-limitless-voice-chats-recorded-chats-and-more

#TelegramDesktop #chatclient #messenger #instantmessenger

Bridgefy, the messenger promoted for mass protests, is a privacy disaster - Rather use open source Briar or Jami

In a paper published on Monday, researchers said that the app’s design for use at concerts, sports events, or during natural disasters makes it woefully unsuitable for more threatening settings such as mass protests.
The researchers notified Bridgefy of their findings in late April. The app maker has yet to fix any of the vulnerabilities but said it is in the process of completely overhauling the messaging internals to use the Signal protocol, the widely trusted open-source cryptographic engine that drives both the Signal and WhatsApp apps.
Briar is an open source peer-to-peer app with a long pedigree which will work perfectly well except only for Android. Jami is also a very secure privacy based peer-to-peer privacy based messenger that also works on iOS. Likewise, Loki Messenger is also Android and iOS. https://squeet.me/objects/962c3e10739402f89dbaede8dd059c005ac1c70c

Moya Messenger App was always #datafree on South African and Nigerian networks to stay in contact with families

It's worth remembering that Moya Messenger for Android is still around and still providing data free messaging (as well as to some websites like Wikipedia, weather, and some government sites) even when a phone user has zero airtime or data balance. You may have data but someone else may need to contact you without data so it is well worth installing.
In South Africa it is data free on MTN, Vodacom, Cell C, Telkom and in Nigeria on MTN and Airtel.
See Download #datafree mobile apps
#technology #datafree #instantmessenger
https://www.datafree.co/moya-messenger-app https://squeet.me/objects/962c3e10a44f50a5ef9aaad3f3947a1bd860958b