n4bz0r

As the others have said, I don't think you can unknowingly break embargo. If anything, I'm grateful you posted - the timing was right for me:

- I've been able to notify the clients that we are going to have to take urgent action;

- Had some time to figure out what actually happened;

- Set up monitoring to know when the fix is out;

- Managed to compile the new binaries the moment they became available.

If the client cares for your craftsmanship.

We're about to land in kaka territory with this one.

Thanks for sharing the experience.

> As in the others that I _won't_ buy (which is what I meant)?

Correct. Sorry, worded the question a bit too ambiguously :)

What kind of trouble did you have with ASUS and D-Link? Security or the lack of configuration options? Haven't bought them in a while, but I remember them being somewhat decent.

I'm quite frequently in the market for a simple home router/AP for friends and family, and they'd rather have something simpler and cheaper, so that rules out Mikrotik (which I would normally go for). Would love to hear some stories about the issues you've had with all kinds of off the shelf stuff if you have the time.

Oh, I rather meant the brands to avoid. But it's still interesting to discover new ones, thanks.

> I'll never buy TP-Link (amongst others)

Been wondering recently what the others might be. Can you give a few examples among popular brands?

Are there any downsides to that approach? No custom CSS, for instance?

The gradient is part of the theme. Updated the post with how to roll back the UI changes for now. After rolling back, select an old theme.

The UI was tidy and nearly perfect, now it's all over the place: weird paddings, different border radiuses even within a single element, clashing background colors, and boy, do I love rainbow gradients everywhere.

Update: for those unhappy with the changes, you can roll them back for now:

  about:config -> browser.nova.enabled -> false

I absolutely despise when people commit their personal ignore patterns. My opinion is that the code in the repository shouldn't know anything about personal environments. The exception is when the entire team benefits from having their common ignore patterns in the repo - in this scenario, the environment details are no longer personal and it doesn't make much sense to not commit them. In any other situation, people are perfectly capable of ignoring their crap on their own and shouldn't pollute the repo. Glad .git/info/exclude is getting more exposure.

> Learn why the world wags and what wags it. That is the only thing which the mind can never <...> be tortured by

Right.

Poof!

Seems like a fitting area for government regulation and certification. But in order for a government to even begin to consider the lack of security in IoT a problem, the adoption must ubiquitous. I.e. the devices (or the number of thereof) should pose enough a threat to public infrastructure (think botnets) to be subjected to regulation. Is there such an incentive in any country at the moment?

I might be wrong, but I don't think people really care about the addictiveness in the first place. As I see it, the shorts were irritating to see, mainly because they were heavily out of tune with the rest of recommendations. But they seem to have tuned them to be more in line with the rest of the videos. Being not that different from the rest of the videos one gets recommended, there is not much point in hiding them? I'm not exactly protecting shorts here. My point is, you can, of course, cut some of the videos from the feed, but the rest would still be affected by the same algorithm. You still don't get to filter anything, really. So what's the point?

If addictiveness really is that much of a factor, I rest my case.