Source?

Anything that binds bile is going to help excrete PFAS, e.g. https://medicalxpress.com/news/2025-11-pfas-body-faster-medi...

Here's one, googling is probably faster than asking for a source: https://link.springer.com/article/10.1186/s12940-025-01165-8

At age ~11, I sent a MSPaint design of a phone with two SIM cards that you could switch between physically on a phone.

I sent it to Nokia over email :-D. They didn't respond.

Dual SIM phones apparently became a thing that same year: https://en.wikipedia.org/wiki/Dual_SIM#:~:text=The%20first%2... Not originally by Nokia, though.

Back when SIM cards were relatively new (and credit-card sized) ca 1997 or so, the vision was that you would plug your SIM card into a landline phone to be able to make/receive calls there. I was working for Motorola at the time and I remember coming up with a couple ideas that I never shared with anyone because I didn’t know who/how.

The first was essentially the iPhone but with a palm pilot type touch screen, the other was a PCMCIA card (which were also much larger back then) that you could put your SIM card into and plug into your laptop to be able to make calls or send/receive faxes on the computer.

Weird.

The main benefit for me to just know and primarily use mermaid is that it integrates with markdown in Azure DevOps and GitHub seamlessly. No need for a text to image build step or similar.

Same reason. I can add to this list Readme.com and Notion.

There are many overlaps with SolidJS. How is this project different, ignoring the obvious; that you don't support JSX.

I've tried to address the technical difference (as far as I understand Solid) at the top of this comment: https://hackernews.hn/item?id=43940144

This reminds me a bit of MSFTs Kusto language. Such an immensely useful way to slice and dice large amounts of structured data.

This is false. GDPR is not ignored, I can tell you that much.

Another checking in from the my company was and continues to be effected by GDPR.

If you were to build a library like `rill` in the Go-way, what would your Batch API usage look like?

How in the world did they come up with the obfuscated code for this? Surely they must be using a tool?

no, it was a thing back in the 90's (and likely earlier.) The goal was to write a program that was "impossible to read". Some of the winners are seriously creative. And it's very much just smat kids and their machines...

I remember one back in the day which wasn't obfuscated at all. It was clearly a simple utility. Except that it didn't do what you thought it did, it did something completely different. (alas I can't remember the details...)

> I remember one back in the day which wasn't obfuscated at all.

Perhaps it was the Underhanded C Contest[1][2]? It's another competition, entires there often seem simple and perform something unexpected.

[1]: https://en.wikipedia.org/wiki/Underhanded_C_Contest

[2]: https://www.underhanded-c.org

There are a number of blog posts online and StackOverflow questions explaining IOCCC entries, and they generally seem to be built/obfuscated by hand. It's an art and it's far from trivial, which is one of the reasons why the contest exists :)

For an example, see this StackOverflow question and its detailed answers for an overview of what obfuscation techniques can be used, although many more exist of course: https://stackoverflow.com/questions/15393441/obfuscated-c-co...

I was able to compile it on macOS, but had to include an extra flag to stop clang from being too strict (version 16):

    cc -Wno-implicit-function-declaration -std=c89 -o test test.c
    ./test

That's definitely a thing. Additionally, humans are surprisingly friendly in all the wrong ways when it comes to physical security (tailgating, "forgotten ID/credentials", etc.).

A compromised human is immensely more feasible than a physical break in, but almost all posts above fixate on the latter