cxcorp

I really like how GitLab has implemented this. Using code blocks but just with "math" as the language is so much clearer, and avoids having to do awkward dollar sign escaping.

I would guess that the markdown parser does some overly eager escaping before handing off the input to the latex renderer. If I change the "\left\{" into "\left\\{" and the "\," into "\\," it renders like with LaTeX.

That first one doesn't compile in LaTeX (assuming \ce is from mhchem?). Perhaps the inline mode $'s shouldn't be in there? i.e.

$$ \ce{ \underset{global coordinate}{(x,y,z)} ->[\mathcal{R}][rotation] \underset{local coordinate}{(x',y',z')} -> \underset{descriptor}{\{\mathcal{D}_{ij}\} } -> E_i } $$

There does appear to be a bug though where the LaTeX expressions don't render if they're in markdown lists or tables.

I hope they don't have catastrophic data loss. I quite enjoy reading the SCP Foundation stories, and I suspect that they're probably one of the biggest sites on Wikidot.

Now that I think about it, I recall there being conflict between between the SCP Foundation's community and a Russian businessman who tried to copyright SCP in Russia.

Wow, there's an ad after literally two lines of text. Absolutely unreadable.

The hi-fi audiophile world is certainly an expensive one.

I love their products, but their sales hasn't really convinced me either. I contacted them while our web service was getting hammered by a TCP SYN flood. They asked me which layer the attack was on, and I told them L4. They proceeded to try to sell me some TCP proxy product of theirs for $$$$, and despite my protests, just wouldn't listen when I told them that their HTTPS proxying/load balancer/CDN/whatever product would probably be enough.

I left that call and activated that free tier product and it has been enough. No wonder their sales reps need to resort to such tactics when their $0/$20/$200 product is enough.

Or coating entire walls and ceilings to track people with ultrasound without them even knowing. Depending on how good the resolution is, maybe even identifying people?

> Because the tiny domes are vibrating, rather than the entire film, the loudspeaker has a high enough resonance frequency that it can be used effectively for ultrasound applications, like imaging, Han explains. Ultrasound imaging uses very high frequency sound waves to produce images, and higher frequencies yield better image resolution.

> The device could also use ultrasound to detect where a human is standing in a room, just like bats do using echolocation, and then shape the sound waves to follow the person as they move, Bulović says.

Which would be less than the 20€ they've offered?

I feel that using a password manager makes it easier. Although, it definitely took some time back when I started using one to dig through the services I had registered for from my emails.

CSS has a concept of "specificity" [1] which is applied also in the case of !important. Basically the most specific rule wins.

[1]: https://developer.mozilla.org/en-US/docs/Web/CSS/Specificity

CSS stands for Cascading Style Sheets. The cascading part refers to the fact that when you have a HTML element which is targeted by multiple style rules (e.g. browser defaults, style sheets, inline `style=""` attributes, inherited from a parent element's rules, etc.), there's a well defined priority order which decides which style "wins" and is in effect.

For example, you might define that all body text is black, but then also have a rule that says that if it's a link (an `<a>` element), it's blue. Suppose you want other links to be blue, but the links in your navigation bar should also be black. Can do, just specify `nav a { color: black }` - now rest of the links are blue, except inside your navbar.

This is neat, because with relatively concise notation, you can specify styles for the majority of your site, but can also easily specialize styles when you need to. Compare that to manually setting `style=""` attributes on every single HTML element!

So what's the problem with !important then? !important is #1 in the priority order I mentioned previously, so when you add !important to a CSS declaration, you throw out the first C from CSS. You're saying "I don't care what any other stylesheet or style rule says - ignore them and use this rule". To beat !important, you need to also add !important, and additionally make your CSS rule more "specific" than the other, e.g. `nav a { color: black }` beats `a { color: black }` because it's more specific - "target <a> inside a <nav>".

This becomes very problematic if e.g. a third party component uses !important in its rules. Let's say that third party component's stylesheet overrides all <a> elements to be red. Great! Every single link is now red - including the ones in your navbar. You'll now need to go back to your own rules and add !important there - meaning now you need to use !important in every single declaration to get the C back into CSS.

Luckily browsers are nowadays shifting towards making the initial request via HTTPS. Chrome, for example, has been using HTTPS when typing an address into the address bar without specifying http:// explicitly [1].

[1]: https://blog.chromium.org/2021/03/a-safer-default-for-naviga...

This is linked to in the second paragraph of the post

I would think that mail to a federal authority would go through an x-ray and mail including suspiciously hidden electronics to get nabbed for forensics.

I'm not sure it's fair to call WSL2 an escape hatch. I use Windows for work because I like the more polished experience of the desktop, but I can just open up a Windows terminal instance and I've got a linux shell (via WSL2). And best of all, I can access the files directly with `explorer.exe .` if I need to.

I wonder if this contributes to why Docker's file operations are terribly slow on macOS.

I usually use the Prettier extension with VS Code to autoformat JSON locally - then again, I already use both anyways on a daily basis.

Some stuff I use often:

- Finding out what a linux command line tool's flag does without having to CTRL+F through multiple matches in the manfile (https://explainshell.com/)

- Test and visualize JS regex (https://regexr.com/)

- Render PlantUML class or sequence diagrams (https://www.planttext.com/)

- Unicode code converter (https://r12a.github.io/app-conversion/)

- Unicode codepoint viewer (https://r12a.github.io/uniview/)

Probably related to AWS us-west-1 and us-west-2 having issues: https://news.ycombinator.com/item?id=29567170

Unfortunately, as is often the case when one learns of a new CSS property or a Web API, the browser support is just not there yet. Safari, for example, doesn't support this at all: https://caniuse.com/mdn-css_properties_contain

I find it interesting that XSS has been in the top 5 since the first Top 25 to include a table with ranks in 2010 (archive: https://cwe.mitre.org/top25/archive/).

I know Content Security Policy can help mitigate XSS, but I wonder if there are any existing tools to help you discover what kind of rules your website would need currently to even function as intended?

Same as Bright Data (https://brightdata.com/), formerly Luminati Networks, who apparently use or used HolaVPN customers [1] as exit nodes for their proxy networks and data collection infrastructure. Their current website sheds some light into how they get their residential and mobile IPs [2] (emphasis mine):

> Bright Data attains its peers (Residential and Mobile IPs) through the Bright SDK, which is integrated into applications as another form of app monetization.

> App users are presented with the option to opt-in to the Bright Data Network and become a peer (share their device idle resources) in exchange for an ad-free or free application. All peers sharing resources with the Bright Data residential network have personally opted-in and may opt-out at any time.

It would be nice to know which applications have their SDK integrated, so I could avoid them.

[1]: https://www.trendmicro.com/vinfo/hk-en/security/news/cybercr...

[2]: https://brightdata.com/ethical

Yes, but isn't it more about the message? "We can get anyone, anywhere, and get away with it?" If nobody knows it was them, does it then work for making an example out of someone?

I think it's so exciting that there's an online encyclopedia of integer sequences (linked to in the article: https://oeis.org/A000127)! Enter practically any sequence off the top of your head, and blam, there's a formula for it and background about it!

You are right, I was quick to judge without knowing. Thanks.

I wonder if the Quebec government tested the masks for things like this? Especially, considering:

> Back in December, the Quebec government revealed that masks it had been distributing for months to more than 15,000 daycares across the province did not meet safety standards, and daycare staff were ordered to stop using them.

> Between May and November, the ministry distributed 31.1 million MC9501 masks throughout the network to protect staff from COVID-19, but they were determined to be unfit for use.

Fool me once...

Definitely! I would love to hear what kind of replacements they had to make:

>As part of our goal to optimize dependencies, we also updated and/or replaced npm packages that were marked as deprecated by their authors – even when they were deeply nested in the dependency tree.

I wonder if they just rewrote some smaller packages themselves, or if they managed to find a maintained alternative for all of them?

> The hackers’ methods were unsophisticated: they gained access to Verkada through a “Super Admin” account, allowing them to peer into the cameras of all of its customers. Kottmann says they found a user name and password for an administrator account publicly exposed on the internet.

So you're telling me that the interface that grants you access to ALL of your customers' (including hospitals and schools) data and shells to the cameras doesn't even require 2FA? W...w-what?

Unfortunately I would imagine that it's still easier to spread a narrative blaming the EU than to attack the real problems.