Prediction: RSS is coming back stronger than ever

RSS was removed from most sites (unfortunately) due to business, not technical reasons. Just like Web 2.0 era "mashup" friendly APIs, business started locking down their data despite it being an extremely user-hostile move.

.plan is really simpler syndication.

That is so cool!

Cool!

Neat project, I like the idea. One thing from a quick read: you launch Chrome with --no-sandbox. Is there a good reason for that? Security wise it's probably not a good idea. If there is no reason, I'd suggest leaving the sandbox on!

In any case, cool stuff :)

--no-sandbox is needed in docker, maybe they assume it will mostly run in docker?

Exactly. For downloading, Kage requires Chrome or Chromium. Running it inside Docker makes setup easier and keeps cleanup simple:

https://github.com/tamnd/kage/blob/main/Dockerfile

Btw, let me think the way to only enable this when running inside Docker.

Docker is designed to be undetectable by default, the best way I have found is to set env IN_DOCKER=True manually in your Dockerfile + check that there is no $DISPLAY configured + that you're on linux. Usually if all/most of those are true you can safely add --no-sandbox --disable-setuid-sandbox --disable-dev-shm-usage etc. all the docker-specific flags. Thats what we do in https://github.com/ArchiveBox/ArchiveBox/blob/dev/Dockerfile...

It should be fixed by https://github.com/tamnd/kage/pull/12

Thanks for nice trick.

Cool approach.

But, a compromise still lands on host's kernel, Docker doesn't provide kernel isolation (well it does on a macOS because it runs in Docker machine but thats a side effect).

I wonder if a better solution would be to play with seccomp or Linux capabilities so that Chrome is sandboxed even in Docker. Not sure how this would work tbh.

Answering here to get ideas, I saw your fix on Git and request for feedback (will try to review and give it some thought once I find some time)

I have never seen anyone pull off seccomp nested sandboxing of Chrome in Docker before, if you manage to figure it out please let me know!

- "Anyway, possible slight hiccups in the merge window aside, the news today is 7.1." - "nothing particularly interesting or scary stands out, which is as it should be."

So, a number.

He's just writing about the changes since last week. Not about 7.1 as a whole. No last minute scary things means 7.1 released as planned.

But 7.1 new features can still be exciting.

To be honest, I always wondered why variations of SSS haven't been seen commercial adoption more. For example, instead of storing API Keys in GitHub repos, the keys could be constructed on the fly by approvers signing their shares. I guess the UX of coordinating share-holders is what kills most implementations...

SSS does suffer though for some serious weaknesses, i.e. it trusts the shareholders. A cheating party can submit a fake share during reconstruction, corrupting the recovered secret, and honest parties have no way to detect this something that verifiable secret sharing fixes.

Anyway threshold crypto is a very elegant field and the math is there is really beautiful.

What I'd love to see is an e-ink reader, purpose-built for RSS. Think of getting your morning digests from select sources without touching your smartphone or PC. Heaven