Picture this:
1. You type on Google "laptop won't turn on"
2. Google now knows you have a broken laptop and can estimate how desperate you are to fix it.
3. Because it knows how desperate you are, it can increase shop prices proportionally.
You are going to pay the maximum they get you to pay.
That's algorithmic pricing.
The more companies know about you, the more they can predict and sell how desperate you are to other stores out there.
An internet-connected car knows much more about you than you realize. A smart TV also knows what you like. Your Alexa knows if there is a problem in the home.
Privacy is much more than just sensitive data.
It's about not giving leverage away.
Because algorithms will use it against you.
Be safe out there.
It's already working on Uber and Lyft apps. Drivers are getting paid lower based on how desperate they are and users are getting billed higher by how desperate they are.
Yeah, ntfy doesn't send any warning after the free plan is over. It just doesnt deliver anything anymore.
Also, their server is constantly too busy to receive new notifications. There are timeouts everywhere.
Nip04 only uses general with the messages enabled as it was the way to work in the outdated nip04.
Nip-17, the gift wrap, is only sent to your DM inbox relays.
The receiver will try to send to your public inbox relays. They are not going to pay for an account on Eden, so you only have nostr.mom that works there. Maybe add another public relay to that section.
Yeah, that's going to be hard. If you have an SVG for the logo you want, send me over that I can add the SVG to the project first. Then you can connect to the hashtag later :)
It's great to see OpenSats going outside of Bitcoin and Nostr with Tor and now WireGuard
nostr:nevent1qqsdvd5h06w73nr8s0h9ey08cd4tvkgmpcfrjevc0gnn8dxhkcu0sdspr4mhxue69uhkummnw3ezucnfw33k76twv4ezuum0vd5kzmp0qgstnffh2gam5t7d46zhmyxc5asdunep88yljrvcda68ee7sasx3w0grqsqqqqqpd30mha
Has anybody onboarded friends/colleagues to your Alby Hub's via the friends and family app?
Would you add a friend to your hub/node if you are onboarding them to Nostr?
I am interested on a design to onboard new "family and friends" users with a complete lightning address + nwc connection out of the box, borrowing the alby hub account at the start and one-click spinning off from it into their own hub/node when they are ready.
How much time are you putting on this? :) Do you want to collab?
Are you sending old events? Those seem to be replaceables that the app has newer versions for but the relay keeps sending old ones. Every time the relay sends, the app will reply with the updated version.
I openened several channels when starting my Alby Hub to test out multiple LSP providers.
95% of your zaps came through Olympus by Zeus. All the others are rarely used.
Why is that? Are their fees that much lower?
You are the LNServer_Wave? If so, I have a 6M sat channel with you, but it never gets used.
I don't think all my followers are using Zeus wallet. Something is off
Not your relay, not your ecash.
nostr:nevent1qqsxamuxmhhw07s43chur365307vkyrxatj07a9ytmlqggdhmy3v4agpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhsygxtchhkkqwt68l69ju44920qnpct2fkcx5xuxaeen0jeu85a04vevpsgqqqqqqs60572z
Sim, vc pode usar o listr.lol e criar uma lista com todos os seus follows de forma privada. O unico problema eh que vc tem que adicionar 1 a 1 na interface.
Testing an old idea: NFC-based transient accounts: accounts that log off as soon as the app goes to the background, deleting all traces of the account from the phone.
It looks like this in debugging speeds: https://video.nostr.build/ef4274d150303fd28f5e7b6b02a7b0102176263dfb1b491969a0caab6b61e6ad.mp4
If you are an activist and if your phone is confiscated, they will never find anything on the phone. Not even your public key.
Walk around with Amethyst installed and an NFC tag hidden in your clothing. When you need to use Amethyst, tap the tag, insert your password and login. Lock the screen to delete everything.
The NFC has a NIP-49 password-encrypted nsec. If you need, destroy and dispose the NFC tag.
nostr:nprofile1qqswuyd9ml6qcxd92h6pleptfrcqucvvjy39vg4wx7mv9wm8kakyujgpypmhxue69uhkx6r0wf6hxtndd94k2erfd3nk2u3wvdhk6w35xs6z7qgwwaehxw309ahx7uewd3hkctcpypmhxue69uhkummnw3ezuetfde6kuer6wasku7nfvuh8xurpvdjj7a0nq40 did you think about decoy nsecs in the NIP-49 spec using the wrong password?
Can we create a Nostr filter where the client sends a bloomfilter instead of a massive list of pubkeys of the 1000 people an account is following?
At .01% error rate, the filter size drops from ~67kb to 2.3Kb. It looks like a good data-saving feature.
🤔
Leo, I need to define a bloom/cuckoo filter format for pubkeys so that implementation A creates the filter that implementation B will use. Do you have any recommendations on how to encode the resulting filter itself?
The filter will be saved in every event as a tag, so it must be something the other client can easily decode and apply.
Bonus if the writer of the filter can specify the precision. Any tips?
Oddbean new post about login | logout
Notes by Vitor Pamplona | export