When does it crash? When you go to notifications or the app doesnt even open? I wonder if it's something else from it because I am able to login with your npub and see it 😅
FYI. Your NIP-65 Public Inbox relay should not be inbox.nostr.wine. That is for DMs and zaps only. It will not receive replies, likes and other comments to your posts.
I would also add more Search relays to your list.
That everyone that received the event is also using a client and relay that support it. It's not about your app and your relays. It's about everybody else's.
Ohh it could be your inbox relays. Amethyst requires the NWC service to send the zap event to ALL your inbox relays. And many NWC relays will not support 30 relays. Many limit to 10 max.
Also, does primal show any error when things fail? My current understanding is that they always show the zap animation even before the zap was sent. I am not sure if they revert it when it fails.
Usually when the zap circle hangs in the last 5% of so, it means that Amethyst is still waiting for the NWC wallet to reply with the successful package OR the zap event to show up. Amethyst requests the zap event to be sent to ALL of your inbox relays. So, you can watch if the event gets there as well.
Wait, does it get to 95% and you don't see any lightning payment on coinos at all? Then, there might be something wrong with the request itself. Or maybe a budget limitation that was setup on coinos?
This other user seemed to have fixed it. But his issue was different. The zap wasn't arriving because of the amount of inbox relays and limits of coinos relay lists.
nostr:nevent1qqsz3q7ja09thcnq0s56hk22dgrg6hlqs00wegveng6kvf8alr89v7gppemhxue69uhkummn9ekx7mp0qgs8efvwljfdwa0qynp7n9dhqacf3llucdqtm9ge8kjv0dt40yw586grqsqqqqqp09f6fv
That is just used to get your home relays. We only use that if we cannot get your nip 65 relays from our bootstraping relays. Your nip-65 should be sent everywhere and thus it should be on our bootstraping relays too.
Algo relays are neither inbox, not outbox. Amethyst doesn't have a place for them yet. They shouldn't be on any of your lists. They are designed for Custom Feeds in clients that you can set up a feed for just one relay, like Coracle
nostr:nevent1qqs024hed0snc0yj9usjamh02xr6m8ezt6azqq86apfjfv6akj8v72gpzdmhxue69uhhwmm59e6hg7r09ehkuef0qgsw9n8heusyq0el9f99tveg7r0rhcu9tznatuekxt764m78ymqu36crqsqqqqqp333dv4
My 2 cents. It should ship with the noctua fan by default. The regular fan is way too noisy. It's not a good experience out of the box. It makes you question the entire purchase.
Yeah, it's about 10 to 20 dollars extra depending on where you buy. But finding the right model is an issue. It would be better if the store already solved that problem.
Imagine working at either campaign and having to find ways to sell their terrible candidate to an electorate that just want a better life. Worst job ever.
Algo relays are neither inbox, not outbox. Amethyst doesn't have a place for them yet. They shouldn't be on any of your lists. They are designed for Custom Feeds in clients that you can set up a feed for just one relay, like Coracle
nostr:nevent1qqs024hed0snc0yj9usjamh02xr6m8ezt6azqq86apfjfv6akj8v72gpzdmhxue69uhhwmm59e6hg7r09ehkuef0qgsw9n8heusyq0el9f99tveg7r0rhcu9tznatuekxt764m78ymqu36crqsqqqqqp333dv4
Nip-11 is irrelevant. You shouldn't do anything based on it at this point. Just talk to your relay operator. They will tell you if they support or not.
There is no point of using nostr if you dont want to manage your own relays. They are the services that give you the freedom promised by the protocol. If you want clients to choose it, Nostr is not very different than Facebook.
Every relay forces your follows to connect to another relay to get all of your content. The more you add the more duplicates you and your follows download. And the more you add, the more they need to connect to find all of your posts.
No need to be large relays on inbox. They just need to be open for people to post otherwise you are not going to receive it. You can either pay for them to post or use a free relay.
It's very cool to see how much Meta is pushing AR with this Orion prototype. My only concern is that they still have this mentality that AR is social, that you are going to use it with and around other people. That to me is wishful thinking. AR is isolating. And to take the best of it, you need to understand and build for that. https://image.nostr.build/28bd4222738edb73bf8b6190573935e15683870d916ec134788b7a0a1a996820.jpg
Agree. In the future, determining what goes in each filter and in each sub and to which relay can be fully automated. The UI just subscribes to an extended definition of the current filter spec (more like the Custom Feeds from nostr:nprofile1qqsf03c2gsmx5ef4c9zmxvlew04gdh7u94afnknp33qvv3c94kvwxgspr3mhxue69uhksmmyd33x7epwvdhhyctrd3jjuar0dak8xtcppemhxue69uhkummn9ekx7mp0qy2hwumn8ghj7un9d3shjtnyv9kh2uewd9hj7208x3z) and the merging algo can figure everything out.
If you configure it to use Orbot but Orbot is not there, it will use its internal Tor instead of crashing. No one wants to see a client that can't load anything.
That was not a good way of knowing if Amethyst was using Tor or not because so much of what the app does does not show up on the screen. Just because the feed is empty doesn't mean that Amethyst is only using Tor.
You can use something like https://www.rethinkdns.com/ to monitor connections that apps make, including Amethyst. Both form using internal Tor and Orbot.
It's because flare is not including the mime type of the video. So amethyst doesn't even download (we only download the videos we support and can play)
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.
Questions:
Did you pay for the consult out of pocket or are you using government funds or private insurance?
I noticed that this only happens when patients are not directly paying for the consult. They are delegating that to third parties and those parties are running free telling doctors what to do.
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.
I think "inbox" is a no brainer. Everyone understands what it means.
Outbox is not as easy because email clients never made "outbox" a real thing. For that, I do think "Home" could be a better name because it suggests that this is the relay that has your posts for others to see, your home on the web. And you should be very careful on the relays you select to be your home. "Getting posts from people's outbox" is a weird thing to say. And "Getting posts from people's home relays" is better understood.
FYI,
1. I use kind 10013 to your "unpublished write" relays, which I call Private Home as described in the Generic Draft NIP: github.com/nostr-protocol/nips/pull/1124
2. Your private inbox to me is not an inbox. It's either an index relay (like purplepag.es) or a new kind that could lists large relays on the hopes of finding events the client can't find anywhere else.
Oddbean new post about login | logout
Notes by Vitor Pamplona | export