Amethyst's Push server is connecting to 3088 active, IP-unique relays.
Citrine has 8000+ downloads.
So, it is possible that there are more relays running on Phones, Start9s and Umbrels than on the public web. 😳
There are a lot of (thousands?) of "hidden" ones. But Amethyst's push server is currently connecting to 3088 relays that our users have directly placed in inbox/outbox relays.
nostr:nprofile1qqsglv2qkn5dmmuhee9cy8fywfu2rfp4xd3xy0myqg2gfvmjl9yqqrqpzpmhxue69uhkummnw3ezumrpdejqzythwden5te0wghxkmm2d9exztnfduq3kamnwvaz7tmjv4kxz7fwvf5hgcm0d9h8qctjdvhxxmmdspqdww any chance you can see what's going on with this file?
Apple is pre-paying 1.1billion USD to retain 85% of Globalstar's satellite services capacity and buying 20% equity of the company for another $400million.
Globalstar provides the infrastructure for the Emergency SOS via satellite.
Looks like a lot of money for "just SOS" 👀
https://investors.globalstar.com/node/15606/html
You send the event in the body of a POST call to the service of preference. The service then connects to those relays and sends the events themselves down via Push Services, like Google/Apple/Unified Push.
The 10097 kind just registers which services the user would like to use for push.
lol. My doctor wrote me a new prescripton. I told him to send it to the hospital's own/internal pharmacy. Now CVS and Walgreens are msging me saying that the prescription is ready.
Fuck this system. Can't wait to Nostrify the shit out of this clusterfuck.
I know... It's ridiculous. I don't want that. I want the doctor to give me the prescription and I want to use it anywhere I so desire. My doctor doesn't care and doesn't need to know where I want to buy the medication.
There is a setting that the link is shown instead of the preview of the image. Is that what you want?
That's on Application Preferences, on the left menu.
You can do vanity npubs for corps in a FROST design where they can swap keys as needed without changing the npub. Key discovery/completion goes through the user's WOT graph.
Signers have to agree on a polynomial to sign. My understanding is that once the leaked key signs with the wrong polynomial, the other signers can just reject that share.
Thanks to nostr:nprofile1qqsqx84rqcvglmnrr2r0rg8ynnhg70tzty4ju7l9lr430z8ryldngzspzemhxue69uhkummnw3ezuun9d3skjtnpwpcz7h8dsdf for the amazing donation made straight to all Amethyst devs via the Zap the Devs button. #Value4value works.
nostr:nevent1qqsz7v0n4ynmq385h369g68zxjf0guc5wnawlr2cdaqmpn5qzm7zrnspz3mhxw309akx7cmpd35x7um58g6rsd3e9upzqqc75vrp3rlwvvdgdudqujwwareavfvjktnmuhuwk9uguvnakdq2qvzqqqqqqy09n9y5
But which did you use to submit the image?
The list can be as big as you want. On the new post screen, you have to select the server from the list. Sometimes they do reject content. Many of them require payment for bigger images or frequent uploads.
Who knew that in order to create a $50B business you don't need to have any good product. You just issue shares and debt to buy Bitcoin and everybody will give you their money.
Silly me.
No, regular companies borrow money to build products that take over markets whose profits push the evaluation higher. That's not what Microstrategy is doing. They are just holding. There is not risk to the company.
I really dislike when clients expose the relay settings as "read" and "write"... Those words make little sense to users.
In the context of the Outbox model, write is where your posts are located and read is where people send you their posts for your notifications.
Your client is "reading" from both at all times. It reads from the "write" relays to get your posts, and it reads from the "read" relays to get the replies to your posts. It also writes to your "write" when the post is yours, and writes to everybody else's "read" relays then they are tagged in your post.
On Amethyst, we use the words "home"/"outbox" for "write" and "inbox" for "read". I don't know if those are the best words, but it seems to make things a little easier to understand.
> You post to your outbox relays and find content from your inbox relays.
Not really. You post to your outbox relays + you post to all of the other read/inbox relays of anyone tagged in the event.
To find content, you have to use a mix between inbox and outbox. Your notifications come from your inbox. Your feed comes from every follow's outbox. The replies, zaps, and likes to each post come from the follow's inbox.
But how do we keep paid relays, or relays that restrict who can post, out of the inbox section?
Similarly, how to we keep relays that restrict who can download from the outbox section?
It's not even about restricting them because some users actually want that. For instance, if they use nostr.wine for Inbox, only notifications from paid users of nostr.wine will show up. Which is great if the person is getting spammed.
But the average person adding nostr.wine to inbox just gets pissed because they don't understand how nostr.wine works.
Explaining that has been our main issue. The Inbox/Outbox difference seems to be fine with users. But even when they understand the difference, they misinterpret what happens when setting up each relay in each section.
But then we need to make that info available to clients. In many relays, clients don't know if the user is being restricted or not. There is literally nothing to inform the client.
No, because if app can't figure it out by itself the UI teach the user to do it.
If we convert to your idea now, nothing is going to work because people will just add nostr.wine to the list and will never receive a notification.
Yeah, we were more upfront in the early days but users thought it was too annoying.
What I realized is Nostr seems fine with not verifying any attached content. Devs tends to be highly dismissive about it and leads to a userbase that is not used to verify attached content.
It is definitely very spotty. It looks like the invoice and payment request goes to Minibits but nothing happens. Sometimes it takes a long time. Sometimes it just disappears.
I tried about 20 zaps between my Minibits and Alby, half of them received a {"result_type":"pay_invoice","error":{"code":"INTERNAL","message":"Lightning payment failed."}} Back from Minibits NWC relay.
At some point, the relay was rejecting any zap from my phone, but accepting all zaps from the emulator.
All these tests with Tor disabled.
When succeeded, the payment took about 12 seconds from submission to the NWC relay to the response from the relay.
Is filtering notifications by location (those around you... say +/-50 miles) something interesting or not?
I don't know if I can find a good use case for it.
Send me your ideas
You don't need to share your location, you can just filter by it. That information doesn't go anywhere. And all relays already know where you are located if you are not using Tor or a VPN, so..
That will never be solved. Nostr is not consistent by design. Whatever number comes back is only a number of the subs that are visible to you and the relays you are using at any given moment.
It's impossible to know how many followers you have.
It would also be broken because many clients will not implement that, especially the new ones. So your follow counter will never resemble the real value.
Oddbean new post about login | logout
Notes by Vitor Pamplona | export
I tried about 20 zaps between my Minibits and Alby, half of them received a {"result_type":"pay_invoice","error":{"code":"INTERNAL","message":"Lightning payment failed."}} Back from Minibits NWC relay. At some point, the relay was rejecting any zap from my phone, but accepting all zaps from the emulator. All these tests with Tor disabled. When succeeded, the payment took about 12 seconds from submission to the NWC relay to the response from the relay.