tyilJul 9, 2024
I just love when #Element has an update (which it has every couple hours), and when you click the button to refresh all you're left with is a white page and an error in the #Javascript console. #Matrix
Show threadtyilJul 10, 2024
It turns out this time its not even a bug, it is intended behaviour! #Element apparently simply doesn't support #Firefox ESR, which is what I use on #Debian, so I guess I just won't use #Matrix on my laptop anymore.

One of the devs argues they cannot support a browser release that is one year old. Why are modern developers so scared of stable software? Why does everything need to be new and changed? It's so dumb...
Intl.Segmenter is not a constructor - unable to use Element Web on Firefox ESR 115.12.0esr (64-bit) · Issue #27682 · element-hq/element-web

Steps to reproduce Try to open the app in Firefox ESR Outcome What did you expect? I expected the app to work. What happened instead? Got an exception in console: Uncaught TypeError: Intl.Segmenter...

GitHub
Show thread+bonifartius 𒂼𒄄Jul 10, 2024
@tyil i really don't get why they do these shit decisions since one or two years.
Show threadtyil
@bonifartius I'm guessing they suffer from an issue that seems to affect the majority of web developers, they're all using high-end hardware and operating systems that value bleeding-edge over stability. It is disturbing how few web developers have ever tried to use their applications on lower-end hardware or on slower or unstable Internet connections. They simply don't understand the majority of people on the planet are not living lives as luxurious as theirs.

If one of the devs were using regular #Debian with #Firefox supplied from the standard repositories, they would've immediately caught this issue.
Jul 10, 2024 at 8:57amWeb
Show thread+bonifartius 𒂼𒄄Jul 10, 2024

@tyil probably it's devs running on latest apple hardware or something alike, yes ;)

i just remembered hydrogen which also is a web client but it should run on older browsers