Does app.element.io still work in Firefox?
At first I thought they were blocking the IP-address range of VPN nodes that I'm using, but now that I've tried switching to a different one, I think something else is at play here.
It doesn't give me any meaningful error — it just looks like a blank page, the only error I see in the console is:
Uncaught TypeError: Intl.Segmenter is not a constructor
node_modules bundle.js:2
Webpack 21
Could this be it? 🤔
OMG, it's not just me and it's… disgusting:
https://github.com/element-hq/element-web/issues/27684
Apparently, their policy is to only support two latest releases of Firefox and Chrome, so the fact that it had worked for me is just a coincidence!
The "that browsed is a year old already" line is simply priceless!
The most fun part is that this update coincided with the new FF ESR, so their solution is: just install the new ad-ridden FF — or Chrome even, what is your problem?😤
Oh my, this is such a trainwreck!
#element #matrix
@scops
Yep, I have Nheko on my only Windows machine, Schildi on my Android phone — also doesn't have the problem as underlying JS frameworks haven't been updated yet.
And I use gomuks my other machines, most of them anyway — really like the TUI experience.
But Element was still indispensible for more advanced stuff that you didn't have to do often, but at times still did — like managing sessions of exporting room keys.
It would be sad if this doesn't get resolved 😩
@m0xee switch to a suitable fork, not updating a browser is a bad idea anyways
@kitkat
Not always possible — there are old machines, there are uncommon architectures. Developers of forks have even less resources than Mozilla does and can't afford supporting those.
Besides, it turned out that not updating is actually quite fine — all the recent major vulnerabilities did not affect old versions, be it xz/liblzma — everyone rolled back to old version as first response; recent openssh one that didn't affect 8.4p1.
Even the critical libwepb vulnerability, which affected FF…
@kitkat
…I was safe because I had support for WebP disabled😁
AND they have made it non-optional right after this was discovered. One of the major reasons why I started building Firefox myself was to bring the preference to disable WebP back.
That's the problem — no one has problem with updates when they are security updates, but they often come with feature updates: support for new things that no one asked for or changes in the UI — at times rather serious ones, which might ruin your workflows.
@m0xee thats the mindset of "modern webdevs"... check out #nheko or #fluffychat :(