I recently created a relay guide. It was specifically for mitigating spam, but it should be a good reference, regardless.
nostr:naddr1qqxnzde4xqerqdpkxuun2wfhqy38wumn8ghj7un9d3shjtnzwf5kw6r5vfhkcapwdejhgtmswf5hvct5v5pzpde8f55w86vrhaeqmd955y4rraw8aunzxgxstsj7eyzgntyev2xtqvzqqqr4gu5j8wws
And here's a regular URL if your client doesn't render the Nostr URI correctly: https://dikaios1517.npub.pro/post/1750204679597/
Nevermind, the one that I happened to click on appears to be a recorded previously live stream that is still showing as live.
I am seeing the same 0 viewers and nothing that is actually live loading.
I don't think it's so much a specific number as it is whether the tag is actually relevant to the content of the post. If the post is loading up on popular hashtags for visibility for a post that has NOTHING to do with any of the tags, then that's spam IMO. However, if there's even 5+ tags and they are all relevant to the content of the post, though, that's fine. Bonus points if they are just incorporated into the context of the post, rather than a list of tags at the top or bottom.
https://advancednostrsearch.vercel.app/
Put in your own npub and your search query. You can also specify date range, if needed.
anyone else having trouble with zap.stream? (in browser)
been unable to play anything live.
all live streams show 0 viewers
all thumbnails appear as just the zap.stream logo
if i click on latest videos, all the videos are greyed out, if i scroll down far enough (around 2 weeks back) then all of a sudden all the videos are not greyed out and i can play them.
#asknostr
nostr:npub1v0lxxxxutpvrelsksy8cdhgfux9l6a42hsj2qzquu2zk7vc9qnkszrqj49
nostr:npub1eaz6dwsnvwkha5sn5puwwyxjgy26uusundrm684lg3vw4ma5c2jsqarcgz
I am having trouble with thumbnails loading, but live feeds are playing when I open them.
Only thing I know of that sounds like what you are talking about is https://landlubber.coracle.social/
I've generally used Shipyard.pub, but it can be hit and miss at times. Hivetalk Honey also allows for scheduling posts. Might give that one a try.
Join me tonight on nostr:npub1z0lcg9p2v5nzg5fycxq0k56ze6snp42clmrafzqpn5w6u74v5x9q708ldk for the first #Shakespeare Vibe Coding Jam session!
https://honey.hivetalk.org/meet/Shakespeare_Vibe_Coding_Jam_Session
Start:
Jul 21, 2025, 8:00 PM EDT
End:
Jul 21, 2025, 10:00 PM EDT
🎭 Shakespeare Vibe Coding Jam Build. Share. Vibe.
Join us every week for an open jam session where builders, tinkerers, and prompt wizards come together to explore the power of vibe coding with Shakespeare. Whether you’re just getting started or have a few apps under your belt, this is your space to:
🛠 Collaborate on live builds 🧠 Share prompt strategies
⚡️ Get real-time feedback
🎤 Ask questions and swap ideas
No agenda. No pressure. Just creative energy and decentralized vibes.
Bring your ideas, your prompts, or just your curiosity. Let’s build the future — one prompt at a time. #ShakespeareDIY #VibeCoding
Going to try and make this tonight.
I absolutely love that more clients are including WoT these days. That said, not all are, and reading from WoT relays gives the user the benefits of WoT without being locked into using clients that provide it.
Also, WoT within clients is typically limited to the particular "logged in" npub's WoT. Meanwhile, I can use a brand new npub that follows no-one at all, and I can browse a WoT relay's feed on Jumble, leveraging that relay owner's WoT to still see content I care about, free from spam. Or I can use WoT relays for my public inbox relays, even though I haven't built up a social graph on that npub, and I won't see replies from spammers, but I will see replies from a large number of legitimate users.
So I still see a lot of use for WoT relays, despite clients adding most welcome WoT features, as well.
As with all public relays, you'll be fine until the next spam attack.
Love you nostr:npub1xtscya34g58tk0z605fvr788k263gsu6cy9x0mhnm87echrgufzsevkk5s, and public relays definitely provide an important service, but when it comes to spam it's always just a matter of time before it becomes a problem on public relays once again.
Have a look at my relay setup guide for mitigating spam, while maintaining the ability to see the vast amount of posts you would want to have in your feed:
nostr:naddr1qvzqqqr4gupzpde8f55w86vrhaeqmd955y4rraw8aunzxgxstsj7eyzgntyev2xtqqxnzde4xqerqdpkxuun2wfhlclwuc
URL in case your Nostr client can't read the long-form Nostr URI: https://dikaios1517.npub.pro/post/1750204679597/
It is definitely decentralized. How decentralized is debatable, but there is definitely enough above-ground gold spread around in enough hands to consider it decentralized.
Gold's problem is portability. This is why paper gold became a thing in the first place. It is far more convenient to trade IOUs for gold than to trade the actual asset. Yet, no one will see this as a problem so long as most aren't trying to turn in their IOUs for the real thing.
I may try to convince Utxo to include an official Dockerfile in the main repo again at some point, maybe something simply built with GoReleaser (no Compose files or anything like that in the main repo). I think we’re now at a different level of maturity, and I can shield him from all the support requests and red herrings caused by broken Docker setups. It would be great to have an official, signed image that folks can pull. But for now, people like you and nostr:nprofile1qqsq4hm8gawvch9y2m7nqghydaw4ym4s4a3gf0u9f9xqm4uy0ul9qvcpremhxue69uhkstnrdajxjmn8v9ex2mnp9e6x7up0da6hgcn00qq3vamnwvaz7tmwdaehgu3dwfjkccte9eshqup0qyghwumn8ghj7mn0wd68ytnhd9hx2tcht4zgq have been doing a great job providing independent builds.
As for getting easily distracted… this makes two of us 🤣
I got you. There’s definitely some interest in NIP-86, which could potentially be extended with custom endpoints. That way, someone could build a React, Vue, or whatever admin UI on top of it. If I’m not mistaken, nostr:nprofile1qqst6jhruelzn9jdf9qhyfsac3fetjyld0fwwary9cmxzfchrhacragppemhxue69uhkummn9ekx7mp0qy2hwumn8ghj76n9d3k8jenfwd5zumrpdejz7yj9f6t was interested and building his own Khatru-based stuff to enable this. Maybe one day we'll hage a NIP-86 GUI that can be reused by all Khatru relays? :)
My main concern with this kind of feature is, again, the attack surface. We'd need to be very careful that users don't expose it to the internet without properly securing the endpoints. Beyond auth + something like NIP-46, I’d also prefer this kind of interface to be limited to the local network (or exposed via VPN). Unfortunately, there are already plenty of bots targeting Nostr relays out there.
Also, Haven doesn't really have much to configure after the initial setup. This kind of UI might make more sense if I ever implement a PGP-like owner trust model. In that case, the relay owner might want a convenient UI to mark an npub as someone who follows bots, and therefore exclude their follows from the WoT. But honestly, that's way down my priority list. First, I want to fix some of Haven's and Khatru's concurrency issues. Then there’s a lot of Blossom work: redirecting, fixing the mobile mirroring on Primal thing, separating the Blossom database, etc. And then there's writing tests (we don't have any at the moment and at least in theory I'm supossed to be a TDD person… Having no tests makes me anxious :)), improving backup and introducing restore functionality, adding optional "open/whitelist" relays for NIP-46, Cashu, NWC, etc. And finally releasing the big v2.0. A lot of pedestrian work required on my side before I can get to the "fun" bits.
I am guessing a lot of these concerns are the same reason an Umbrel or Start9 package is not currently in the works? HAVEN really is the most incredible personal relay out there, and it should be as accessible as possible for users to run, so more folks can take advantage of its features. Yet, I understand the security risks of having a GUI, especially a web GUI, that could be exposed to the internet by unwitting users.
Pretty sure you can use your CLN node as the funding source for LNBIts, which has a NWC plugin.
The relay was seeded with a set of users who were assigned a number of shares. Every reaction, repost, or authored note is considered to be a vote with all available shares from that voter for a piece of content. The voting action can be made from any client. Currently, a note must reach 25% of all available shares to move to the main feed. Once a note meets or surpasses that 25%, it's author gains 1 share and becomes a voting/contributing member.
This one was initially set so that the seed voters maintain heavy voting weight for a longer length of time, since the goal is to create a welcoming onboarding space with some longevity. Over time, voting weight will shift & input from the relay's contributing community will take over control.
You can check the current list of contributors/voters at https://relays.land/spatianostra . Anyone who is listed there can visit the staging area linked on the page to actively cast votes for nominated content by reacting or reposting. Even if not visiting the staging area, voting is done passively as described above.
Shares are still quite low for most of the voted-in contributors but I encourage anyone who's interested in participating to try it out. I would love to hear what more people think of this concept. More so, I'd love to see people contribute content with the intention of earning more shares for themselves.
This is still very much in an experimental phase, so any input is great. If someone's reasoning & commitment is strong enough, we might be able to persuade the captain of this ship to make some manual adjustments, though the concept is to avoid needing to do that. Eventually the threshold of the community vote will outstrip that of the founding voters.
Wow! I love seeing interesting relays like this!
Definitely something I would browse as its own feed, rather than sticking it into a slot as a regular read relay.
Got it. I was still in my home directory when I ran the command. I THINK it worked this time. 😂
Ran the above and it couldn't find any "haven" command.
`Command 'haven' not found, did you mean: command 'aven' from deb survex-aven (1.4.4-1build1) Try: sudo apt install
So I ran what was listed on the GitHub instead; namely `./haven --import` and it gave me this:
`bash: ./haven: Is a directory`
Not sure what it doesn't like about it, but that command doesn't seem to work in either form.
wss://relays.land/spatianostra currently has 223 unique users contributing content to the voting pool and a collection of majority voters who passively create a positive, diverse, and engaging Nostr experience. Active voters are focused on maintaining a welcoming space that's not overwhelmed by any particular topic (except #flowerstr 😄).
It's available to new users in https://jumble.social as a default. If you've been reluctant to introduce your friends & family to Nostr because of "echo chambers" or the sketchy "global" feeds, check it out. It's a soft landing place for anyone who wants to figure out how to navigate Nostr.
Can you give me the low-down on how this works? How are other users able to "vote" for what content ends up on this relay?
“If you turn back your foot from the Sabbath, from doing your pleasure on my holy day, and call the Sabbath a delight and the holy day of the LORD honorable; if you honor it, not going your own ways, or seeking your own pleasure, or talking idly; then you shall take delight in the LORD, and I will make you ride on the heights of the earth; I will feed you with the heritage of Jacob your father, for the mouth of the LORD has spoken.” - Isaiah 58:13-14
It is the Lord's Day. Let us call it a delight and honor it for his glory and our good.
On Facebook. I just asked him a couple pointed questions about what causes inflation, and whether there is a distinction between deflation caused by debt-unwind vs deflation caused by improved productivity thanks to technological advancement. Then I suggested he reat The Price of Tomorrow by nostr:nprofile1qqsg86qcm7lve6jkkr64z4mt8lfe57jsu8vpty6r2qpk37sgtnxevjcpr4mhxue69uhkummnw3ez6ur4vgh8wetvd3hhyer9wghxuet5qyt8wumn8ghj7un9d3shjtnwdaehgu3wvfskueqpp4mhxue69uhkummn9ekx7mqux2c7y.
It is what is called a "blastr" service. It will find any events you have authored on any of the relays within its list of 40 or so relays, and it will then broadcast your notes to that same list of 40 relays, so all of your notes will be on all 40 relays, assuming they are online and accept them. Since these are relatively popular relays, chances are that most people are reading from at least one of those 40, and Primal certainly aggregates from several of them.
Sounds like a modified version of Pascal's wager.
I'll be using burners until it supports NIP-55 login. 🫡
Sounds like a good idea on the surface, but the song and dance of scanning a QR to get the unsigned event over to the signing device and then scanning another QR to get the signed event back to the broadcasting device would get old really fast since EVERYTHING you do on Nostr needs a signature from your private key, not just signing in.
Just try using Amber signer with zero automatic signing permissions to see what I mean. And the method you are talking about does not allow for automatic signing of any of them.
Give me a day or two and I can reach out to you about our setup at my church. I am still away at summer camp until tomorrow afternoon and have limited internet access.
I just looked that brand new npub I created up on all of those clients, and I have the option to follow it, even though it has no kind 0 event anywhere.
Amethyst:
Nostrudel:
Snort/Phoenix:
Coracle:
Kind 0 unable to be found via Luminostr, since I never created one:
Nor can I, which may mean it is someone we have both muted.
It's unique to Amethyst, which has edits for kind 1 notes and also allows other users to suggest edits.
Not much beats a North Idaho summer, except maybe a North Idaho fall.
I have taken to manually typing the "nostr:" prefix for all Nostr URIs since it is far more consistently handled by various clients. Leave it off and you may or may not get the desired result, depending on the client.
That said, I think client devs should be better about recognizing and handling URIs that are missing the prefix. Can't really count on that, though.
BREAKING 🚨
Prayers for the Firemen and police in Idaho 🙏
Active shooter / S
2 firefighters confirmed dead multiple on the mountain and cannot get out
Potentially 4 shooters with sniper rifles and other firearms.
______________________________________
#news #breaking #idaho #fire #police #shooting #dead #pray #active
https://blossom.primal.net/11262802fb0463f78711a8ab2e577e342a180b457bcab90737d05076d4ca32f9.mp4
Still an active and very dangerous situation. Number of shooters unknown but still on the run last I heard.
You can always take a peek at my latest stream recording on zap.stream to get an idea of what the combat is like.
The Nostr client you are using sends a deletion request note (kind 5) referencing the note you want to have deleted to all of your write relays. If the relay is configured to respect deletion requests (they are not required to do so), the note will be deleted from those relays. However, it is very likely already propagated to other relays that your deletion request did not get sent out to, so the note probably still exists and is viewable by others.
This is because there are relays that aggregate notes from other known relays, even though you aren't intentionally writing to them. There's not really anything you can do to prevent this, just like you can't prevent someone from screenshotting your post on legacy social media platforms. The best we have are lockbox relays, which flag notes that should not be rebroadcast to other relays or aggregated by other relays using a "-" tag, but even that does not have to be followed by other relays. If the note exists and is readable anywhere, it can be copied to other locations.
Whenever you post on Nostr, you should assume that the note will exist somewhere on some relay forever, even if you request deletion.
Are you sure it is actually using those recommended relays and not just recommending them to you?
I am using the nostr:nprofile1qqs83nn04fezvsu89p8xg7axjwye2u67errat3dx2um725fs7qnrqlgzqtdq0 release of nostr:nprofile1qqs24yz8xftq8kkdf7q5yzf4v7tn2ek78v0zp2y427mj3sa7f34ggjcpzamhxue69uhhv6t5daezumn0wd68yvfwvdhk6tcppemhxue69uhkummn9ekx7mp0qyg8wumn8ghj7mn0wd68ytnddakj703s8dt and while I see a list of recommended relays, the app is not using them unless I tap the option to "Add" them, and then they get added to the General Relays section.