Tesla’s “Full Self-Driving” sees pedestrian, chooses not to slow down
Comments ( https://news.ycombinator.com/item?id=35966550 )
Cannon fodder
I May be wrong, however there was/is a know Damus issue around event threading. At least one of those events has 3 e-tags, which may confuse clients.
If you can see the event below, it’s likely just a thread lookup logic issue.
nostr:note1z0de95jfdear3lce0l04nsdmzjfkcqrc58pd4vdy9qgry0pcwszqaqy569
Using alby, setup worked fine. Since then I always get timers on zaps and they don’t seem to even process.
Does the alby Nostr pubkey for the account need to match? Sounds weird to ask, however mine likely doesn’t due to dev work.
Mass produced food tastes very very different to local, organic and fresh in most cases.
Food science, but also social effects too - like coffee, smoking, or conversational drinks.
And a lot is about balancing them for consumption. Some vegetable dishes don’t result in a well balanced profile.
Private keys are meant to be air gapped or at least never leaving a device, especially not sent to the internet - no matter what alleged encryption or security is used.
Imagine to get access you need an email and password. They know your email. Now your password. You effectively transformed your secure private key into a short password brain wallet or low time brute force puzzle.
Ledger is not something I’d recommend to anyone, even if it’s fairly mature and nice enough general UX.
But the update did give 37 new shitcoins to love and go bankrupt holding.
#[0] where’d you go? Just read through your safer Nostr project code.
I was just looking for this too. No joy so far.
My zap on this post seems to have a yellow clock icon for over a minute - no transaction shown in alby web. Seems like a long delay, or it didn’t work.
Concern is most people may prefer someone to blame, over their self reliance. Second concern is there still doesn’t seem to be enough devs.. maybe it’s a financing issue.
Excited about wider adoption and easier p2p payments
Hey Joyo, hashtags often aren’t rendered in bios, but it depends entirely on the app. It’s a protocol, and all clients can choose most UI/UX decisions based on their desires.
There is no formal verification for Nostr accounts. Usually a post from an existing platform is an indicator. If you own a domain, you can also use that to prove control of that domain.
Lots is still new here.. so things can always be improved or reimagined.
Looks awesome 👏
It seems like their usernames may be dangerous to reuse as well - just like an email address. If someone takes it over in future, they could perhaps cause problems.
Imagine a decentralised protocol that suffered from username squatting 😰
Not a problem on Nostr everything in data is the hex key, and never pointers or aliases are used in event references..
Hopefully this week. My first approach was a bit destructive, haha. I’m refactoring it now.
Works for event view and overlay. Not for DMs as yet. Needs edge case handling improvements.
This code works as an example 402 payment required server. I’ve refactored it a lot locally too - but should work fine.
I’ve got a hackish Damus POC for Nostr HTTP Auth using NIP98. Basically for 401 Unauthorised and 402 Payment Required image requests with a WWW-Authenticate: NOSTR-NIP-98 header, we can optionally retry with a signed event base64 encoded in the Authorisation header.
This is exciting because we get to use the 401 header, have a nice way to retry requests with Nostr auth, and can optionally accept payment or perhaps offer a subscription to gain access.
For the UX, I’d like to have a UI to add a domain to a trusted Nostr HTTP Auth List, which allows ask, or always send auth (for domain).
If you’d like to help progress the swift code for Damus, let me know. I’d appreciate the help.. as it’s a little complex managing cache and retries using kingfisher with custom requests.
#[2] is this something you’re open to accepting into Damus? It should only matter for content that returns 401/2 and has the Nostr auth headers - otherwise it shouldn’t do anything. So it’s an extension in capability. 
PostgreSQL pooler and proxy (like PgBouncer) with support for sharding, load balancing, failover and mirroring - written in rust.
This is a cool project.
“Indra's production goal is to sustain up to 480,000 LN nodes per server over 10 clearnet IPs. This gives a cost basis of around $0.003 per month, down from $12-31 a month for traditional hosting. Around 4,000 to 10,000x cheaper.”
The good news is that it fundamentally cannot work - it’s vapourware, and will run its course. The downside is how many people get messed around until then and while it crumbles. Theranos 2.0.
He maybe has five years before it’s entirely irrelevant.