I don’t think I’m disputing your facts, I was responding to the scenario you presented which was, essentially, “what about email”. I would say it’s fair that my opinion on a canonical browser history is solid and unlikely to change, though.
I think the word ‘app’ was being used in place of ‘webapp’ there, which is the general target audience for this feature.
I don’t think that email and browser history are similar enough to make a meaningful comparison, honestly.
Maybe someone could say that, but I am not.
I see a specific instance of a specific bad feature being specifically abused. I don’t care to entertain whatabouts.
I accept that it’s how things are, I just personally feel as though the only way this feature could ever work as it does now is with the implementation it has now, and that the convenience of single page webapps that use history manipulation is not worth the insane annoyance of helping my grandma get out of websites that tell her that she has been hacked by the FBI.
I’m frustrated that removing bad functionality is being treated as a slippery slope with obviously bad and impossible jokes as the examples chosen.
I see a bad feature being abused, and I don’t see the removal of that bad feature as a dangerous path to getting rid of email. I don’t ascribe the same weight that you seem to towards precedent in this matter.
I’m a self-taught C# dev, I’ve found tremendous success specifically just describing what I want to do in dumb language that I’d feel stupid asking people IRL about and that aren’t googleable without knowing what both the terms “null-coalescing” and “non-merchandise supergroup” are describing.
There are a lot of patterns that don’t have obvious names and that aren’t easily described without describing a specific scenario in a way that might only make sense institutionally, or with additional context that your average person might not have. ChatGPT is fairly good at being the “buddy that you have a bunch of in-jokes with that can remember things better than you”. I can skip a lot of explaining why I need to do a thing a certain way like I can with my coworkers (who all aren’t programmers), and I can get helpful answers for programming questions that my coworkers don’t know the answers to.
It’s frustrating to see this incredibly advanced context-aware autocorrect on steroids get used in ways that don’t acknowledge the inherent strengths of what LLMs are actually great at doing. It’s infuriating to have that potential be actively misused and packaged as a service and have that mediocre service sold to you once a month as a necessity by idiots in suits watching a line on a chart.
Nano is the tool that people use when they don’t have a need for TUI editors in general and therefore don’t want to have to memorize how people with teletypes decided things should have been done 75 years ago and who also don’t want to get dragged into endless pointless bickering arguments about which set of greybeards was objectively right about their sets of preferences.
I’m glad people enjoy the editors they use and also I just wanna change a single fuckin line in a config file every once in a while without needing to consult a reference guide.
Life support for a monster set aside as insurance against the day that the monster needs it.
Agreed entirely, Mozilla doing nothing would be far preferable to me here then them helping extend our current experience with advertising by working towards a future with a minimal set of meaningless concessions that Meta’s involvement with suggests would not meaningfully negatively impact their business in any way.
To my mind, fixing advertising means making advertising a much less lucrative business. Doing anything else is only making the already dire problem worse.
Form, not function.
And to top it all off, release codenames are Discworld references!
It’s a bit more consumer focused, easier for Grandma kind of thing. Syncthing isn’t hard, but does have in my opinion a bit more difficult of an initial setup with features like introducers that can make things difficult if configured wrong.
But at least your pacman has candy
As far as I understand it, they’re given equal weight in the order of operations, it’s just whichever you hit first left to right.
Sounds like a you problem.
Funfact: Walmart pays the vendors (usually local person who rents their own truck and buys their own stock) on scan data. If it doesn’t scan, Walmart is also not affected.
There is a DVR product called SaleGuard that can detect this from existing or integrated camera systems. It tends to work fairly well.
I mean, they’re not gonna nab you for apples unless they get enough of a rolling tally on what you took to actually prosecute usually. That’s what most corps do.
I don’t have any idea what you’re on about and I want to call you rude.
The ones from NCR use the camera-based 7879/7895 scales with computer vision to check that you aren’t doing this. It’ll take a picture and require an override where it shows that picture to the attendant.
It’s called produce assurance.
Sorry, this comment was mainly just providing the previous user with a correction because they seemed to think that the other person that they were replying to was talking about forcing people to use phone apps, which I assume we all agree is bad and would likely work if there were a concentrated push for it.
Concerning your points after “using the browser”: I want websites to use replaceState and manage their own intra-page navigation with a cookie. They can still intercept the back button as they do now, but they should only get the single history entry until they switch to a new page, if they ever do.