In Australia we call them “seppos”. Short for “septics”, which comes via rhyming slang from “yank” -> “tank” -> “septic tank”.

Reread the comment you replied to. Not one word of it was in there accidentally.

Oh yes, that’s a very good point, actually. That actually seems such a fundamental use case that you could almost justify it being available without a permission.

Maybe, but I’d like to see a concrete example of how they are “designed to talk to each other” that couldn’t be achieved by the extension just reading the DOM.

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.

Collapses? Wish Amazon would collapse after it was revealed their magic grocery store where you just walk out with what you want was just Indians viewing CCTV.

I asked elsewhere, but this is probably a better place for it.

Wait, Piefed migration doesn’t just work from Piefed to Piefed, but even from Lemmy into Piefed?

Wait, Piefed migration doesn’t just work from Piefed to Piefed, but even from Lemmy into Piefed?

That’s quite a small view of temples. Seems mainly restricted to stereotypes of Catholic/Christian abuses.

I agree. When I hear “temple”, the first thing I think of is ancient Greek, Egyptian, or Babylonian places of worship. To gods like Isis, Athena, or Enlil. After that I might think of the word being used by some Jews for the thing other Jews call synagogue or shul.

I would never call a Christian place of worship a temple. It’s a church in the generic, or sometimes more specific terms like chapel, cathedral, or monastery.

edit: actually, immediately after writing the above I remembered that Mormons call their equivalent of a Catholic Cathedral (i.e., the grandest and most important of churches, where important sacred ceremonies are carried out) “temples”.

I think the broad picture of this is really interesting, but I’m struggling to understand exactly how it matters.

State government legislation controls retailers, so they must act to incentivise or require retailers to act aggressively to identify and help them to cut both gas and electricity consumption in cold weather

Is it all just a roundabout way of saying “houses need better insulation”?

if you’re an excel power user, you’ll need to learn Libreoffice Calc

Let’s be honest…most people who are Excel power users probably need to interact with other users. Sending and receiving documents and templates, etc. Simply learning Calc yourself isn’t going to suffice, you’d have to convince your entire business to switch.

I never actually put any serious effort into using MuseScore myself before the changes, so I can’t comment from extensive personal experience.

But as a musician, I did use scores written by someone in MuseScore, as well as ones written in Sibelius. And I could always tell when it was MuseScore. I’m sure it was possible to write good looking scores in MuseScore 2, but it clearly did not make it easy. The scores were obviously inferior in terms of layout and design compared to those produced in Sibelius. Basic things like spaces between notes not being the right proportion, or dynamic markings appearing as plain italic text instead of the usual bold dynamics would be wrong in MuseScore far more often than in Sibelius.

As a general rule, a good UX should:

1. Make it very, very easy to do (or discover how to do) the most common basic things, and should result in them being done in the way a user expects
2. Not slow down a power user from accomplishing basic tasks at speed
3. Allow easy discovery of and access to less common tasks

A lot of designed-by-software-engineer FOSS applications do a good job of 2 and an ok job of 3, but fail at 1.

Interesting. That would make his survey of rather limited value, in my opinion, because just by doing notes (including rests), durations (just from semiquaver to semibreve, including tie and dot), and accidentals, you get 18, right off the bat. Considering the ranges offered in the poll he made were 1–5, 5–10, 10–20, and 20+ (never mind the overlap if you happened to use exactly 5 or 10…), that makes it very hard for anyone who types their note input instead of hunting around slowly with the mouse to get into anything other than the top bucket. Especially since he quite explicitly said “including typical ones (like Ctrl+S, Ctrl+Z, etc.)”

Sponsorship? This is the Nebula version, there wouldn’t be any sponsorship. Did he accidentally leave it in and I just blanked that out?

Unfortunately Sibelius’s development has basically stagnated since 2012 when the new corporate owners fired the entire original development team, with only one noteworthy release of the core app (not counting side-projects like an iPad app) since then, in 2014.

I first learnt Sibelius on its pre-ribbon interface, which I think was much better (even though I loved the ribbon in MS Office). That certainly made the transfer to more modern versions easier. Still, although Sibelius has a number of specific hangups in its interface that make fairly common activities awkward and unintuitive, I really do think it has the best basic flow. When you’re just in the zone inputting notes, it’s so easy to use in a way MuseScore isn’t.

I actually take some issue with Tantacrul’s design process, because it feels like he fundamentally doesn’t understand how intermediate users like myself use the app. At one point he sent out a survey asking “how many keyboard shortcuts do you use?” in Sibelius/MuseScore etc. The problem was that he didn’t define what a keyboard shortcuts is, and when people asked for his definition, he just snarkily responded that it would be obvious. But it’s not. In Sibelius, you use your left hand on letters A–G to enter the note pitch, and your right hand on the notepad to enter rhythm values and common articulations. Slur lines and some other things can be entered during this process as well (slurs with the letter S).

Does this count as keyboard shortcuts? To me, everything I described above except maybe the slurs is actually the musical equivalent of typing text into a word processor…or a browser text box, like I’m doing right now. Does it become a “keyboard shortcut” just because it can also be done by clicking a rhythm value in a toolbar, and then clicking a location in the staff to choose pitch? I have no idea if Tantacrul thinks so, because he chose snark rather than clarifying.

Incidentally, his MuseScore design replicates this flow, but without the visual reference of the keypad toolbar that lets you learn and easily see what number to press, without requiring sheer memorisation. It’s been a while since I last tried it, but I vaguely recall having other issues with the flow being hard to work out with a keyboard. Great if you’re just slowly mousing around everywhere, but not for the intermediate user trying to get in the zone.

Which is such a shame, because he did such a fantastic job of the other stuff. The user onboarding, score setup, page layout management, etc. The attention to detail even with small things like music fonts and symbol design is impeccable.

That whole series is absolutely brilliant, but it’s hard to go past the Sibelius one if I’m gonna go back to one. And I say that as a long-time Sibelius user who can comfortably work much faster in it than in any of the alternatives.

The open source music notation software MuseScore used to be really, really bad. A musician and UX designer gave it a scathing review in a humorous YouTube video. And then the company behind MuseScore hired that YouTuber and spent a lot of effort doing a major redesign, and now it’s actually quite good.

All it takes is for the people in charge of the project to put aside their hubris and trust that sometimes, programmers aren’t the best designers, and to get people who are trained in designing and evaluating user interfaces to do the job. And to perform adequate user testing.

Ah, but have you considered: we could not do that?

—Labor supporters, probably.

My read of the meme was that the similarity is the point. “You vs the girl he cheats with”, if one was significantly more attractive than the other would probably imply that it’s the woman’s fault for not being more attractive. But by showing them both basically the same, the message is “if he’s a cheater, he’s gonna cheat, no matter what you do. It’s on him.”

But maybe I’m putting too much thought into it.