221–230 of 346 posts
Earlier quoted context omitted.
Email is OK. The point is that most conversations moved to other media (mainly chats) and so 90% of my mail is notifications, 9% is newsletters, 1% are real messages. They used to be 99%.
I really wish Google's Wave went somewhere. It was the real solution.
Respect. This is what Firefox could have been. In the real world, in the same line as the article suggests, there was a brief time when the "puts you back in control" browser needed you to change the following about:config settings to disable the force-pushed ai: browser.ml.enable, browser.ml.chat.enabled, browser.ml.chat.sidebar, browser.ml.chat.menu, browser.ml.chat.page, extensions.ml.enabled, browser.ml.linkPrevi…
Look, I absolutely agree it sucks they didn't deliver the opt-out/in interface day one, it was obvious people would want it, and yes, it's not the first time they've blundered. At the same time, they did listen to the feedback and deliver. It now has a genuinely good interface for it where you don't have to opt out of everything, but can opt-in where you want it. It's not just a big off button, it's a general out-out…
Some 10 years ago I was a Mozilla volunteer. I mainly worked on MDN, to the point of becoming a so-called "topic driver" for the glossary. Some of the work I did landed in the citations of a couple of papers about web technology. They flew me a whole week to Vancouver for an event where employees and volunteers worked together in the same room and they even made me (and the other volunteers ) attend a sort-of-corpora…
Dat feeling when reading "IRC (an open protocol)" on HN—the parenthesis being necessary to explain IRC. Makes me think in 10 years time the web will all be discord-like data silos behind infernal subscriptions and/or dark patterns with ads. What a wonderful thing we've created.
Who else would be likely to look at what a web page is trying to get the browser to do, e.g., trigger requests for ads using Javascript. There are a variety of places to look, it is not like this is seriously hidden from those with even the slightest curiousity
That a former MDN volunteer is apparently disappointed by ads on MDN yet satisfied with MDN anyway because of a community-sourced browser add-on. An add-on that can be rendered useless at any time by the browser vendor, including the one that puts ads on MDN
It is not unimaginable that one day uBlock Origin may cease to work on Firefox when Mozilla sells search data to Google as its primary source of income and is actively working on such things as "making ads more private"
I thank the volunteer for their past work on MDN, I'm not singling him out, nor am I holding it against anyone for thinking this way, but I wonder how many uBlock Origin users believe themselves to possess some "specialised knowledge",^1 for lack of a better term, but would be all but helpless against advertising without a solution provided by someone else, e.g., a browser extension
The point I'm making is that today it seems like "knowing which app to install and how to install it" is considered specialised knowledge instead of actually knowing how to avoid ads to an extent where if the app stopped working they could devise another solution
There are definitely some HN users who can do it, and you, dear reader may be amongst them, but it seems, based on the comments I have seen over the years, there are many, many more who cannot. In that sense the situation is a bit like the IRC comment
The more one understands about online ads, the more clear it should be that so-called "ad blockers" is only a temporary solution at best, and these only work with web browsers
IMHO it is important that more people who wish to avoid ads become more curious about how they work instead of only installing a browser extension and concluding the problem is solved for the long-term
1. Many calling themselves "engineers" for example
Earlier quoted context omitted.
I wouldn't want a browser without extensions. Ad blocking in particular. To me, ad blocking belongs in extensions. The job of a web browser is to show web pages as intended according to the standards. It includes all the ads, tracking, etc... the page has put in. If you want to block stuff or deviate from the standards in any way, that's what extensions are for. And extension like ad blocking are an arms race, websit…
Extensions are the primary threat to your security today. Nothing else comes close. Organizations are not basically competent if they are not restricting or blocking extensions, and you should not have more than one to three very trusted extensions in your browser. I'd argue the case for eliminating them in favor of in house code is significant. As a reminder: Extensions execute with post-decryption access to the web…
Now, that's a question of whether you trust those who write the browser more than those who write the extension.
And by the way, the argument you have is the same that justifies the much hated "manifestV3", which makes extensions less powerful for security reasons. But it also limits the blocking capabilities of browsers to a simple, less effective blacklist. That Firefox still supports the old "insecure" way is a big selling point over Chrome.
If you're burned out, no longer fun, we all get it. But don't leave your investment into a product just because some new direction took over unless you plan to kick their backside.
Earlier quoted context omitted.
Good for you. The point is that a lot of Firefox users actively didn't want these sorts of features enabled and pushed on them. That was clear and obvious to anyone paying attention to general reactions to unsolicited AI helper tools, going back decades. For Mozilla to turn this on without any respect for those users’ preferences was a huge mistake that they keep making over and over again.
More specifically: they chose Firebox because it doesn't have those kind of features. If the just wanted a (sorta-kinda) open-source browser filled with all the latest hype features they would've simply used Chromium. Using Firefox is a political choice. People use it because it's one of the few remaining traditional browsers which isn't a tentacle of Big Tech. Chasing the competition and adding the stuff your users…
I don't mind features existing, especially if I can switch them off if I don't want them. I definitely mind Chrom(ium|e).
I don't see how the existence of the Firefox AI sidebar gives Google effective control over web specs.
Earlier quoted context omitted.
With almost no exceptions, movies are never made by small teams beyond the student film level. Even then, dozens of people are usually involved in some way. Writing, acting, score, foley, editing, distribution, graphic design, color grading, wardrobe, effects, lighting, cinematography, scheduling, props, location scouting, set decoration, casting, mixing… the list goes on. Any one of those things sucking badly enough…
Not to mention smaller (successful) production teams are often comprised of veterans of the industry who have worked on large scale productions and bring that knowledge set with them. Same with many indie games. You have to play with the big dogs to understand what is and isn’t necessary for a product. You can’t just walk in with a plucky attitude and a dream unless you want to waste a lot of time and money. The part…
Not just knowledge but personal connections for favors. “Hey, [talented editor] it’s [famous DP], do you think you could tame a crack at this scene in your spare time? I’m trying to make something out of nothing and I’m positive you’ve got the chops.”
I don’t think anyone could reasonably call any of the exploitation self-inflicted. You have to take shit work a lot of times because a) nothing else is available and you still need to eat, or b) that’s the only way to get your foot in the door for the chance of being slightly less exploited. Unfortunately the industry collapsed when I graduated school as a career switcher getting into Houdini simulations. The software skill set is utterly devalued on the open market. I couldn’t get exploited if I wanted to. Now I’m a union tradesman. ¯\_(ツ)_/¯
Earlier quoted context omitted.
Not to mention smaller (successful) production teams are often comprised of veterans of the industry who have worked on large scale productions and bring that knowledge set with them. Same with many indie games. You have to play with the big dogs to understand what is and isn’t necessary for a product. You can’t just walk in with a plucky attitude and a dream unless you want to waste a lot of time and money. The part…
> bring that knowledge set with them Not just knowledge but personal connections for favors. “Hey, [talented editor] it’s [famous DP], do you think you could tame a crack at this scene in your spare time? I’m trying to make something out of nothing and I’m positive you’ve got the chops.” I don’t think anyone could reasonably call any of the exploitation self-inflicted. You have to take shit work a lot of times becaus…
The self-inflicted comment is a bit tongue in cheek because they do it to their own production to effectively “crunch” (to use video game parlance) but they also crunch themselves in the process. Difference is they have way more to gain. The sound mixer on an indie darling isn’t getting much out of it.
Earlier quoted context omitted.
Netsplits, missed messages and bot wars over channel and nick ownership were an integral part of IRC UX, and they were direct consequences the IRC protocol. If Discord was run on top of IRC protocol, it would have the same. Discord would probably be its own network and the people who prefer IRCnet, EFnet or QuakeNet would never touch it.
> Netsplits It's not inherent to the protocol. https://ergo.chat/ does not have netsplits (from having a single server) and https://github.com/Libera-Chat/sable replaces the server-to-server protocol to eliminate netsplits as well. And even when not eliminated entirely, they are infrequent and barely visible on well-managed networks like Libera.Chat. Many chat platforms have more (and longer) outages than Libera has…
IRCv3 missed the boat by years. By 2016, when the working group was formed, IRC was already well past its glory years. Even then, it took til the 2020s before any major network fully adopted it. Because - and I say this as a nerd who held an O line on two of those major networks at one point in my life - a bunch of nerds got hung up on arguing about implementation specs rather than looking at features and functionality organically. Ironically, in the quest to avoid becoming a closed Discord/Slack/what-have-you ecosystem product, they needed a product manager to remind them that what they needed to build in that working group was an evolution to IRCv2, not endless arguments over the format of configuration files for server daemons, for but one example.
> And ~15 years ago we got native support for authentication (https://ircv3.net/specs/extensions/sasl-3.1)
The IRCv3 WG was convened near the end of 2016, so 9 or so.