Thanks for the response.

Of the (very few) times I did manage to login this past week, Relay groups (along with threads, chat rooms etc) worked great, but I was unable to send a single DM - Are you aware of/able to replicate any issue with DMs?

Apologies, I should have been clearer.

Blossom servers may or may not support NIP-96 - They are separate implementations of media servers that can work with Nostr.

One such implementation of Blossom that does support NIP-96 is nostr:npub1v0lxxxxutpvrelsksy8cdhgfux9l6a42hsj2qzquu2zk7vc9qnkszrqj49's Route96.

For NIP-96 servers, check out:

https://github.com/quentintaranpino/NIP96-compatible-servers

This is a great demo to explain Nostr to your frens.

nostr:nevent1qvzqqqqqqypzqwlsccluhy6xxsr6l9a9uhhxf75g85g8a709tprjcn4e42h053vaqqsqqqz2qeqt3f5u39chk775jleme636eha57ghpnrkl60ufltyw8es9nx32u

NIP-96 is the most likely route right now.

Check out Blossom servers.

About to vent.

I have to say, as excited as I am, and have been, about Nostr's future, I'm currently hugely frustrated with the lack of interoperability lately when #interoperability is THE number 1 killer feature of #Nostr.

Let me put it this way.

There is only ONE desktop/browser application out there that I've been able to find that does DMs properly (and it's not perfect) - #Gossip. All others are either borked right now, don't support NIP-44/17 (Yes, in late 2024), have been outright abandoned with websites still up, or a combination of those along with requesting direct access to your nsec (again, in 2024).

But I can't seem to use Gossip to onboard regular people as the UX is strictly functional.

My hopes as of late are on #Coracle and #Flotilla from nostr:npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn, but also as of late, both myself and others have had numerous issues, some of which are related to just logging in - Seriously, Flotilla shows HUGE promise for communities and is THE app that just seems to do it all (DMs + Communities!), I'm just sad I can't even log into it (also trying to self-host it, but getting other issues at build time I'll have to tackle another time).

Looking forward to nostr:npub1zuuajd7u3sx8xu92yav9jwxpr839cs0kc3q6t56vd5u9q033xmhsk6c2uc's MLS-based client but I'm expecting that will slow the idea of interoperability as it gets tested out and other clients adopt it.

In the past 13 days, I've been able to onboard 6 people, but solely on mobile. Many are asking for a Desktop alternative offering properly encrypted DMs and a modern UX.

#0xchat's planned desktop application can't get here soon enough - And yet is likely years away.

Patience.

Test

#NoCoiners are, by definition, #insane.

Doing the same thing over and over and expecting a different outcome 😬

#Bitcoin

Unfortunate, given whatever wasn't working for you on Linux would be solvable, and you'd retain all its inherent benefits.

One of things I disliked was the lack of self-domain support for zapping addresses (they want you to only use getalby it seems) and the multiple sub-accounts can't have zap addresses assigned to them (likely due to tbe limitation on the previous point).

You have two options, and they're both easy I would say.

1) Download the arch iso, boot up, run archinstall, select guided install, under extra packages choose the desktop environment you want and you're done.

2) There are Arch-based distributions. One such distro is EndeavourOS.

I'm running one of each of the most popular implementations of nostr relays (stryfry, nostream, nostr-rs-relay).

Happy to give any pointers.

I'd recommend using any used hardware you have lying around, as it's cheaper than a VPS, especially if you already have a domain (if not, there's also tor).

I also recommend you install these via docker - Super easy (couple commands) and quick.

Lastly, if you're willing to dish out some sats for an easy setup, check out https://relay.tools/

It depends.

I think most people jump around distributions (commonly known as distro-hopping) because there's this big misunderstanding that distributions != Desktop Environments.

Personally I settled many years ago with Arch - Easy, unbloated install. I install different Desktop Environments when I want to try something different.

There's also now the misconception that Debian-based = stable and Arch-based = unstable, which was true for a time but is no longer true - Bleeding-edge on Arch often means any rare bugs that come up get fixed in a matter of hours. I run Arch for literally everything at this point (servers, desktops) and it just works.

It's ok, take your time, we'll welcome you to Linux, inevitably 😏

I see metadata.nostr.com also uses kind 10002, so that should be a good starting point.

Ahh, I see, that makes sense and clarifies my confusion - Thanks.

What's the recommended way of updating the NIP-65 list?

Just setting the relays in a client that supports pushing the updated NIP-65 list to relays?

Face of a man who should probably start uploading his livelihood content on Nostr, or risk being deplatformed further.

Good luck to #BTCSessions

NIP05 has the optional relay list which can be pulled for users - Does Amethyst support this?

If so, yes my list is outdated. It was updated on my .well-known/nostr.json some days ago, and Amethyst hasn't pulled the updated list yet.

Thanks for the response.

Humm... 🤔

In that case I need to figure out why my Amethyst relays aren't updating accordingly.

nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z

Does #Amethst check and pull relays from a NIP-05 list when the user has it configured? If so how can this be "refreshed" or does it trigger periodically?

test