nostr:nprofile1qqsf03c2gsmx5ef4c9zmxvlew04gdh7u94afnknp33qvv3c94kvwxgspz3mhxue69uhhyetvv9ujuerpd46hxtnfduq3xamnwvaz7tmjv4kxz7tpvfkx2tn0wfnszxmhwden5te0vd58y6tnw3cxjmrv9ehx7um5wgcjucm0d5w28rcn coracle does not display links in angle brackets appropriately
So Far, AI Is a Money Pit That Isn't Paying Off
Comments ( https://news.ycombinator.com/item?id=37846727 )
https://gizmodo.com/github-copilot-ai-microsoft-openai-chatgpt-1850915549
just another shitcoin, what a surprise
Hostile design much? The icon is incomprehensible, it lacks a tooltip to explain itself, and you can't even figure it out by inspecting it with dev tools.
This is definitely something that belongs in the details view with a clear explanation, not just randomly thrown out next to a few user profiles. (it doesn't even show for most users???)
Have you used <https://artifact.news>? Good or bad?
Or email, or matrix, or lemmy, or kbin, or pixelfed, or peertube, or…
Or misskey, or Bluesky, or threads, or tumblr, or…
alex@gleasonator.com@mostr.pub -> look up pubkey at https://mostr.pub/.well-known/nostr.json?name=alex@gleasonator.com
Alex IS associated with both domains, but there is only one NIP-05 identity here. Is there really an issue with having more @ signs? If he wanted to go by `@lex_gle@son@nostr.com` would it be any harder to look up than `alex_gleason@nostr.com`?
Of course I don't care about giving Alex his leet hacker NIP-05. I am wondering how we might proxy NIP-05 identities like Alex did for events with NIP-48. Allowing for @ signs would be unconventional, but seems like the simplest way to do it. Whether it is reasonable is another question.
nostr:npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6 nostr:npub1acg6thl5psv62405rljzkj8spesceyfz2c32udakc2ak0dmvfeyse9p35c nostr:npub108pv4cg5ag52nq082kd5leu9ffrn2gdg6g4xdwatn73y36uzplmq9uyev6
Is there an obvious reason why `@` is not allowed in the local part of a `nip05` key? It would be nice to have proxied names like `alex@gleasonator.com@mostr.pub` instead of `alex_at_gleasonator.com@mostr.pub`. Assuming it's not allowed in the domain part, there should be no ambiguity in how to look that up.
s/key/value
nostr:npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6 nostr:npub1acg6thl5psv62405rljzkj8spesceyfz2c32udakc2ak0dmvfeyse9p35c nostr:npub108pv4cg5ag52nq082kd5leu9ffrn2gdg6g4xdwatn73y36uzplmq9uyev6
Is there an obvious reason why `@` is not allowed in the local part of a `nip05` key? It would be nice to have proxied names like `alex@gleasonator.com@mostr.pub` instead of `alex_at_gleasonator.com@mostr.pub`. Assuming it's not allowed in the domain part, there should be no ambiguity in how to look that up.
You cannot edit your username on mastodon.
lol
I even made a working branch that would fix this dumb policy but I hesitate to submit it because I doubt they would accept it.
Unfortunately the cask won't be accepted, I already tried and it was immediately rejected for failing automated testing due to lacking an apple developer signature.
That only applies to new cask submissions. Casks that existed before that policy get a pass.
Yes it is a braindead policy.
Thank you all for the support! Really appreciate it.
It is "done" but I don't have permission to push it through. A member still has to request bottles and then the bot will queue it for merge.
Stonewalled review is driving me insane. If anyone wants to chime in here about getting gossip in homebrew-core I'm sure they would be appreciate the nudge.
cc nostr:npub1acg6thl5psv62405rljzkj8spesceyfz2c32udakc2ak0dmvfeyse9p35c nostr:npub1wtuh24gpuxjyvnmjwlvxzg8k0elhasagfmmgz0x8vp4ltcy8ples54e7js
scoop is way way worse and probably never happening at this rate. but you can always use our repos anyway.
Stonewalled review is driving me insane. If anyone wants to chime in here about getting gossip in homebrew-core I'm sure they would be appreciate the nudge.
cc nostr:npub1acg6thl5psv62405rljzkj8spesceyfz2c32udakc2ak0dmvfeyse9p35c nostr:npub1wtuh24gpuxjyvnmjwlvxzg8k0elhasagfmmgz0x8vp4ltcy8ples54e7js
