increasingly my mac has critical issues that are undebuggable due to apple services (family sharing, etc)
For about 3 months my mac had 1second network delays when opening any new connections, but only sometimes? The console wasn't much help as the failing services were all secret apple things with error/failures but no usable logs.
Android 13 Chrome 117 here and it did not work for me. Menu popped open on the long press, but moving my thumb up or down resulted in the whole page scrolling. Ditto on Firefox 117. (Is that weird that both my browsers are on the same version number?)
There's some speculation that it's because of "trying to compete in the minds of users who actually think they can compare two totally different software applications by comparing their version numbers."
Tbh, none of them really attract me right now. They are too clunky and don't have many people to interact with. I'm slightly annoyed by Nostr's proposition and total lack of moderation controls. Even if its developers are well-meaning, I see this as a dangerous, undesirable position to take.
I'm really comfortable with Mastodon/ActivityPub. My personal profile is in a public instance[0], and for my Portuguese-written site I'm hosting a Microblog[1]. It's just great.
I met a guy in a Hawaiian shirt at a coffee shop; I awkwardly laid out thousands of USD on the small table between us. We made small talk waiting for block confirmations.
People check in fake private keys to git repos all the time for testing. My own tests have private keys too. They're just sample, unused, publicly advertised private keys I found online. They're useful to make sure your code is working end to end with some private key.
Checking in fake private keys is fine for testing. Why is it bad, out of principle, just in case you check in bad private key? I think that's a bad argument because there are a lot of benefits to being able to run end-to-end tests with some key.
Care to explain? Keeping private keys inside the repo sounds fine for me as long as these keys are only used for local development, they are rotated regularly and are only valid for localhost (in case of TLS certs).
Not GP:
If you make it normal to check in credentials and keys, then the risk of accidentally checking in prod secrets increases. It's basically making it comfortable for devs to deal with keys in repos and I think that's inherently dangerous.
You should be using automated checks to keep credentials out of your repo, not relying on individual developers. And those checks can have explicit exceptions for known safe/public/test keys, just like you might explicitly allow testing or fake credit card numbers.
Fixed twitter perms. FC farcaster
I also emailed you