hhmx.de

Jürgen ⁂ :gts:

Jürgen ⁂ :gts:
@juergen@servus.jyrgi.de

· Föderation EN Mi 05.03.2025 20:40:19

@ivory @cms

GtS is doing push notifications differently.
@vyr can explain, she has developed PN in GtS and maintains FediText, a Mastodon client that has working PN. I do not have the tech background, but there seems to be different methods in implementing PN. Mastodon is using an outdated mechanism if I understood correctly.

0x   1   0x

fashionable cyber witch project vyr

fashionable cyber witch project vyr
@vyr@princess.industries

Föderation EN Mi 05.03.2025 20:47:49

@juergen @cms @ivory short version: GTS uses standards-compliant RFC 8291 Web Push encryption (Content-Encoding: aes128gcm).

Mastodon has, for most of its history, used a draft version of that RFC (Content-Encoding: aesgcm): see perform_legacy_request.

current development versions of Mastodon support the standard version as well: see perform_standard_request. if and when Ivory picks up aes128gcm support, it should start working with GTS Web Push notifications.

0x   1   0x

amd

amd
@amd@gts.amd.im

Föderation EN Mi 05.03.2025 21:59:15

@ivory

Totally get that GtS support is not on the agenda, but you might want to reconsider this error message until / if you support aes128gcm in Mastodon, just to reduce people with GtS pinging you about how restarts don’t actually fix it.

@vyr @juergen @cms

Medien: 1

0x   1   0x

Ivory by Tapbots :emoji_wink:

Ivory by Tapbots :emoji_wink:
@ivory@tapbots.social

Föderation EN Mi 05.03.2025 22:07:53

@amd @vyr @juergen @cms Yea we are looking into it. 🙂

0x   0   0x