DIDs do not specify keys should be written to a public chain, another commented mentioned the VC spec.
Another thing to look at is the did:peer method, it allows you to have a direct connection with a party for secure communication. Either party could root their did against a public key (eg a public organisation) but that is not required.
I'd disagree. They're better off getting some feedback on books that might appeal to their learning style and background better. Otherwise they may tire quickly and not learn well-enough.
Actually, having gone through multiple programming books, I disagree with that. I highly recommend HTDP because of their design recipes. The book shows you an approach to solving problems with programs rather than just the syntax of a language. This book has had the largest impact on my (very humble) approach to programming.
You need a DB of all of the dead entries that need to be deleted, and that’s a fine thing to have.
There are lots of problem spaces where deletion is expensive and so is time shifted not to align with peak system load. Some sort of reaper goes around tidying up as it can.
But I think by far my favorite variant is amortizing deletes across creates. Every call to create a new record pays the cost of deleting N records (if N are available). This keeps you from exhausting your resource, but also keeps read operations fast. And the average and minimum create time is more representative of the actual costs incurred.
My case was really simple. I was done with my ML pipeline and nuked the database, but pics in B2 remained with no quick way to get rid of them and/or to stop the recurring credit card charges.
IMO an "Empty" button should have been implemented by Backblaze.
A single pass: paginating through all entries in the bucket without deletion, just to build up your index of files. And then using that index to delete objects in parallel.
Backblaze currently recommends you do this by writing a “Lifecycle rule” to hide/delete all files in the bucket, then let Backblaze empty the bucket for you on the server side in 24 hours: https://www.backblaze.com/b2/docs/lifecycle_rules.html
Absolutely correct. I've got a cross-compile toolchain set up right now that needs Debian (Ubuntu won't do because of different glibc versions in the cross-compile toolchains). I used debootstrap to make a basic Debian Stretch filesystem, chroot into that, and apt-get the remaining pieces and run the build. Works like a charm, no Docker required. And, unlike containers, it's intentionally persistent so future builds go very quickly.
You need to read the _whole_ comment.. dingaling said it was a technical failure and didn't even imply it was due to staff, just commenting on the general public's opinion at the time.
I know people don't read the article, but at least read the comment lol
Worked a treat