Formerly /u/Zagorath on the alien site.

  • 3 Posts
  • 30 Comments
Joined 2 years ago
cake
Cake day: June 15th, 2023

help-circle


  • Comments from the original post on [email protected]:

    there have been a series of lies from our Lord Mayor and his council over this. Starting by blaming the pedestrian path closure on ex-cyclone Alfred, and then saying they needed a couple of days for inspections before it could be opened. We know now that the closure had nothing to do with Alfred, and was in fact damage that they’ve known about since at least 2016.

    We haven’t been given any timeline for when it will reopen, so our best guess is not until next year.

    they claim it’s impossible to close a lane because one lane wouldn’t be wide enough, so they would need two. If that were true, then fine; the answer is to do that, close two lanes. There’d still be 4 for cars. But it’s not true. In fact, while the pedestrian paths on the bridge are wider than what would be left of one lane after water-filled safety barriers are installed, the paths on the on-ramps up to the bridge are already narrower than that.

    they lied to the press and public by claiming the protests are linked to the Greens, that they’re related to Extinction Rebellion, and that they’re illegal. None are true. Every protest has gone through the accepted process of declaring intent. Instead, BCC & QPS have wasted their resources fighting the protests in court with multiple expensive Silks, against the self-repped organisers. And they lie, inventing nonsensical security risks, in order to get the court to block the protest.

    (the protest pictured here is a different one to the one that BCC and QPS lied to get blocked. A weekend march through the CBD streets that make up the official detour. Instead of the originally-planned peak-hour block of the Story Bridge)

    For context, “silks” is a term used by lawyers in Australia to refer to experienced barristers who can command the highest prices.





  • Zagorath@aussie.zonetoLemmy Shitpost@lemmy.worldSheeple
    link
    fedilink
    English
    arrow-up
    3
    ·
    3 days ago

    fyi you can put alt text on an image by putting it between the square brackets

    ![alt text here](url here)

    Might not be a great option for long and detailed alt texts describing all the text in a comic, but for something simple like this it’s much more convenient for people with screen readers.












  • I agree with you about dropdown menus being something that could/should be natively available to HTML, but I’m less convinced about form submission. Sure, if we assume everything is happy path it’s a great idea, but a system needs to be robust enough to handle a variety of cases. Maybe you want to redirect a user to a log-on page if they get back a 401, or present an explanation if they get a 403. A 5XX should usually display some sort of error message to the user. A 201 probably needs to add an element into the page, while a 200 might do nothing, or might alter something on the page.

    With the huge range of possible paths and desired effects, it pretty quickly becomes apparent that designing an HTML & CSS–only spec that can meet the needs is infeasible. There’s definitely a case to be made that JavaScript has become too powerful and can do too many potentially dangerous or privacy-invading things. And maybe a new range of permissions could be considered to limit a lot of that at a more fundamental level. But what we’re talking about here with the form submission stuff is the real bare-bones basic stuff JavaScript was designed to make easier—alter the contents of web pages on the fly in response to user actions. And it’s really, really good at that.


    • Your operating system
    • Your CPU architecture

    Agree. No reason they should have this.

    • Your JS interpreter’s version and build ID

    I can see a reasonable argument for this being allowed. Feature detection should make this unnecessary, but it doesn’t seem to be fully supported yet.

    • Plugins & Extensions

    This is clearly a break of the browser sandbox and should require explicit permission at the very least (if not be blocked outright…I’m curious what the legitimate uses for these would be).

    • Accelerometer and gyroscope & magnetic field sensor

    Should probably be tied to location permission, for the sake of a simple UX.

    • Proximity sensor

    Definitely potential legitimate reasons for this, but it shouldn’t be by default.

    • Keyboard layout

    As someone who uses a non-QWERTY (and non-QWERTY-based) layout, this is one I have quite a stake in. The bottom line is that even without directly being able to obtain this, a site can very easily indirectly obtain it anyway, thanks to the difference between event.code and event.key. And that difference is important, because there are some cases where it’s better to use one or the other. A browser-based game, for example, probably wants to use event.code so the user can move around based on where WASD would be on a QWERTY keyboard, even though as a Dvorak user, for me that would be <AOE. But keyboard shortcuts like J and K for “next”/“previous” item should usually use event.key.

    There could/should be a browser setting somewhere, or an extension, that can hide this from sites. But it is far too useful, relative to its fingerprinting value, to restrict for ordinary users.

    how sensors are used to fingerprint you, I think it has to do with manufacturing imperfections that skew their readings in unique ways

    It’s also simple presence detection. “You have a proximity sensor” is a result not every browser will have, so it helps narrow down a specific browser.