Faux Tales - Atlas
opentelemetry I think is more targeted towards internal application tracing and cross-system interactions
You are legally (and imo also ethically) obligated to scan for and report CP
Don’t want it? Don’t host shit, or reduce the risk significantly (paywall).
Also, you release any expectation of privacy if you use a media host meant for public usage nostr:note1la533qs9pdg7wp75t8c4mmxa98flm0m4dfzk2rgehnemg0h9pjtq3p56kn
You will ingest the influencer propaganda and buy the overpriced HWWs and you’ll be happy
A quite significant amount of podcasts have economic ties to VC firms and entities that do not value Bitcoin ethos nostr:note1ws42ww6rvxlsfgt70c3zjlh2ussjflgjq7tanr2tq370uywurzrs6gxzjf
There was a “Verify Disk” option in disk utility app… Maybe check option & right click on backup symbol in task bar to verify your existing backups… https://osxdaily.com/2012/02/08/repair-boot-disk-mac-os-x-disk-utilit/
Out of disk space. That is it
tip:
ncdu /directory -o ncdu.json
let it run the background
ncdu -f ncdu.json
"Time Machine could not back up the disk “Macintosh HD” because a snapshot of the disk could not be created."
that does not sound good, at all
...
975GB/1TB used
also run cat /dev/sda, sometimes you may need to trigger a read
new NFDB test
Could just be a reposter, this is why we need to start using `i` tags from nostr:nprofile1qqs99d9qw67th0wr5xh05de4s9k0wjvnkxudkgptq8yg83vtulad30gpz4mhxue69uhks6tnwshxummnw3ezumrpdejqzxrhwden5te0wfjkccte9ehx7umhdpjhyefwvdhk6qgdwaehxw309ahx7uewd3hkcd5u7te 's NIP (forget the number of the NIP 😅)
NIP-39
Sorry, Rust is not performant enough, I want to replace my computer with an FPGA that runs hand optimized RTL nostr:note1tr33ayd55ya60a7xmzvmdfm5vczavjdwg0rhs8zrvwphzg9ws6dqnegw4z
abc is total fucking crap that is not timing or PNR aware
I am so fucking tempted to make my own tool nostr:note1xdgr724lfl7f58z4t9ejk4t8e4khrvytrqv8vluf6xtmt7a3smyszxdgr8
🐁
field programmable gate array
Goodhart’s law nostr:note1srrtezg5a732dhaccvpgpt5aezgjcl35ug2dl7gye96spl54rcts4fhtqf
I cannot give an unbiased opinion
What you have though works and is still secure
Client SHOULD authenticate with NIP-42 when they receive an AUTH as that indicates that there may be additional features available post-AUTH.
Such as prioritized responses, access to certain content (no, refusing an entire request with auth-required does not work, and neither does trying to figure out what requests want what with heuristics)
not bad though that is based off of a somewhat ancient platform at this point
doesn’t matter too much