It’s odd that this hasn’t got more attention. It should be easier to write backends that tie data access more closely to user credentials without the backend trying to enforce that itself. Is there anything out there that makes this easy to do?
3,597 karma · joined September 18, 2014
[ my public key: https://keybase.io/grahame; my proof: https://keybase.io/grahame/sigs/6dBCi0Tz9tPB9Ol-1vfm3GzBKcerqzjiH57YFG_hpOs ]
It’s odd that this hasn’t got more attention. It should be easier to write backends that tie data access more closely to user credentials without the backend trying to enforce that itself. Is there anything out there that makes this easy to do?
It felt like busy work at the start, but it's a surprisingly powerful way of focussing the day upon a particular intention – in my case, putting everything I do in the day into the context of my religious tradition.
Personally I've always struggled with habits and routine, but I've now got quite a powerful experience of what persistence can do, with a fairly small commitment in time.
Paged shared libraries, signalling by ramping up and down CPU usage, there are an enormous number of possible covert channels.
Yeah, this. I've found myself drifting over to OneDrive for personal use; it's pretty good at least on macOS, and Dropbox is just one-more-thing running all of the time.
But also, almost every time I log into their service I get popups bugging me to upgrade, it happened just now. I pay ~ $100/yr at the moment and I guess I've been too lazy to eliminate that expense by moving everything to one provider. Today might be the day to change that.
> All the current trends are making it easy for developers to ship code directly to users. Which encourages more isolation instead of collaboration between projects.
This is where I would respectfully disagree. As a dev, packaged libraries from the system are often fine – until I hit a snag, and need to work with the devs from another project to work out a fix. With cargo/node/yarn/poetry/gopkg/... I can send a PR to another project, get that merged, and vendor in the fix while all of that is happening.
If I can't do that, I'm left with hacky workarounds, as upstreaming a fix and then waiting up to 12 months (if I'm on a six-month release tempo OS) for the fix to be available to me is just not practical.
Being able to work on a quick turnaround with dependencies to fix stuff is one of the huge wins with modern build tools.
NFS is in the category of works well enough, but the edge cases are a mile wide!
Seriously – if you use Docs or Sheets and want to move off, you've either got to manually export everything to an interchangeable format, or just give up and leave a bunch of stuff behind.
This is a particular pain when shifting between Google accounts, or closing an account down (for example, at the end of a job.)
Male-to-male cables absolutely should not be made up.
Apparently some people make them for plugging caravans in to external power as a sort of hack.
Say you are running OCR via some C library you have compiled to WASM: wrap that functionality up with an interface, compile that to WASM, and only pass it the image data you're happy for it to see. If someone exploits that binary with a malicious image, there's nothing inside the container except the code and the image itself, so hopefully the damage is contained.
If folks start compiling large amounts of their functionality into one single chunk of WASM, which has a complex interface with the DOM/JS, then I can see how these exploits could become an issue.
It looks quite periodic when you zoom in: at first I thought it might be different adoption rates in different timezones, but there's only one sample available per day so that doesn't explain it. Anyone know what might be going on?
https://www.cloudflare.com/dns/dnssec/dnssec-complexities-an...
I suppose you can get around enumeration concerns with CT by using a wildcard cert. It's always seemed odd to me to worry about information in a public database like DNS being retrievable on bulk anyway - that approach is just security by obscurity.
I spent a few years as a scientific programmer and this is exactly the sort of thing that just bites you on the behind in C/C++/Fortran: the undefined behaviour can actually manifest as noise in your output, or just really hard to track down, intermittent problems. A big win to get rid of it.