Great job jabronis - attached picture is what the site looks like on an old phone. All the buttons are broken and do nothing, except for the Modlog which somehow is still accessible. Tried different browsers on the phone, tried clearing all the cookies and cache, still doesn’t work.
EDIT: This came off a bit hot and aggro - it just sucks since pre-migration the site worked fine on my dinosaur phone, so I’m pretty frustrated. Makes me appreciate communist web-design (like marxists.org and redsails.org) even more.
Please stop blaming our beautiful devs, shit sucks but Apple fucked you over by forcibly breaking their own shit, it’s not our devs fault that your phone is on a platform that apple has made out of date for your phone in particular. They genuinely put in a herculean effort to get this thing merged back into Lemmy so that they aren’t stuck doing completely unpaid dev work just for us forever.
I think a big part of the problem is that the Lemmy UI (and by extension, the Hexbear UI) doesn’t work properly with Javascript disabled. There are some people who would have the same issue as OP because they deliberately turned off JS even on a device that can support it.
Making the UI work without JS will be a lot of work, but also worth it.
JS is really the only way live updates can work. Like getting pinged with a notification instead of refreshing the page and seeing one pop up.
Having a barebones fallback UI that doesn’t require JS would be good though.
tbh I really don’t see the need for live updates on a Reddit-style website. I don’t need to instantly respond to a comment or reply, and I don’t normally stay on the same page long enough that updates would be significantly delayed anyway.
Serious question, do you have any idea what you’re even asking for? You gonna mail Layla an Iphone 6 from a decade ago to see if our site works on a shitty outdated version of safaris rendering engine?
I can’t even imagine how bad 10 year old safari would be handling the site. I definitely don’t have any way to test or debug it myself. If you are savvy at all, try and open the safari debugger console and screenshot what errors come up in there.
It actually handled pre-migration fine, I don’t know what it is about the lemmy code that it doesn’t like - maybe it’s a javascript thing? That’s what someone else said. I sadly don’t have the code chops to know how to effectively use the debug console.
this looks like a decent guide: https://www.lifewire.com/activate-the-debug-console-in-safari-445798
If you get me a good list of errors, i can probably take a look at mitigating them for iphone. We recently fixed a bug for old safari around using regex.
There’s a little message under the “Web Inspector” toggle that says in order to use the web inspector I need to connect my phone to a computer with a cable and use the “Develop” menu in the menu bar … so that’s a Mac only thing apparently. :-(
Your phone is old enough, it might be worth looking into flashing some sort of open source ROM that replaces your old iOS and gives you a newer browser and security updates. It’s actually a bit of a security issue that apple puts on you by not updating their shit.
I’ve unfortunately noticed a handful of mobile performance issues with vanilla lemmy in general. hopefully this is something the team here is doing their best to improve, but I also know a lot of that is probably upstream issues.
Related, I still think for a community like this, needing javascript to be enabled is a big issue opsec-wise.
yeah I’ve literally had someone else’s username/pronouns randomly pop up in the top right corner (on desktop) when I load a new page. As though I was logged in as someone else. Usually it switches back but I also see upvote data and thread titles and other such stuff randomly get substituted for the data that is supposed to be loaded. I only ever experience these kinds of weird glitches on javascript-heavy websites. to this day idk why javascript has this problem but it’s very disorienting and bizarre
Almost the entirety of exploitable flaws in browsers these days go through javascript; and it’s all of them if considering only the ones that can actually allow you to execute code (in or outside the sandbox).
JS can also be used to fingerprint you far far more precisely than without it.
Not inherently so. It can be used maliciously, and it can be used usefully. Web browsers are designed to at least contain potential damage by sandboxing the browser processes and by limiting how the javascript can speak to the rest of the computer.
That said, basically 95+% (I make this number up but it’s probably correct) of user ad tracking, which is a nicer term for legitimized spyware, will be written in javascript. The mitigation strategy on desktop is to use the ublock origin extension. The mitigation strategy for cellphones is a big fat “it depends.”
