Last Notes
Sorry, 195 npubs and 1 muted hashtag.
Don't blame you on that particular hashtag, either.
So, it looks like there are 196 npubs on your mute list that are not encrypted at all, visible to anyone who cares to look. Then there is a chunk of encrypted information in the "content" tag that likely includes other npubs none of us can see, but you alone would be able to see if you go to your mute list in your settings on Amethyst or Coracle. Damus will not show these encrypted entries on your mute list. Most clients don't.
It looks encrypted if I view it in Damus, but if I open the note on nostrapp.link it shows around 200 muted npubs. I think it just comes down to how each specific client is coded to read or display the data.
https://nostrapp.link/#nevent1qqsy4dwqt5z3v36ysek9jj9q7w86cy3qpf2ark6rckxvsx0648xuydqm5z905?select=true
NICE! Thanks for the head's up!
So paying for nostr.land eliminates the need to have hist.nostr.land in my write relays?
hist.nostr.land as an inbox relay?
There's definitely some interesting choices in your 10002 as well. 😂
What client do you use primarily?
Tracked it down. Looks like the list of relays Damus uses are found in the user's kind 3 follow list. Specifically under the "content" tag.
Why is Damus using this as the primary source for a user's relay list, instead of kind 10002, and why does the user have no control over which ones are read and which ones are write?
Really? From the looks of it, the content section of @nprofile…rvcc's mute list is encrypted.
I just popped over to Damus, though. It looks like it isn't using this list at all.
@nprofile…5cp7 what relay list is Damus using? It looks like it has only populated the relays from my "General Relays" list in Amethyst, and isn't using kind 10002 at all. What's more, I have no way to set which ones are read and which ones are write. Does Damus treat them all as both read and write?
That's a start. We need to talk about this though:
https://relay.brightbolt.net/0112c4abdb404e83770eff6b44e3f873f3dff9ab97091c8154d3a2e4812129b8.jpg
That's your list of inbox and outbox relays. It could use a clean up.
What client are you running?
There’s a special place in hell for the creator of these word jumble reply bots 🤬🖕
Yeah, that's expected. Mute lists are saved to the author's outbox relays like any other note and most clients don't encrypt their contents, so anyone can readily see who is on them.
No I'm seeing the content of the note.
lol, what?
So, there is a client notifying people when they have been added as a "p" tag in a mute list?
Not only that, but you are still seeing his note tagging you, even though you have him muted, so your client is ignoring your mute list?
I suppose this is a case in point why having the option to add muted profiles privately (encrypted mutes) is important.
Since you're using Amethyst, make sure you take a look at your "General Relays" too. These are not saved to a public-facing relay list, so you may have some public relays there that you are reading from that you may need to give the axe.
Ser, that's what meetups are for.
Do you have any relays you are reading from in the "General Relays" section? Any with the green downward arrow lit up in that section you will be reading from as well.
You bet, my friend!
Maybe I should open a relay selection consulting service... 😂
Indeed. A debit card is really the same principle, but attaches to a checking account instead of a credit line. Therefore, it is subject to the same KYC regulations and much of the same charge-back risk.
Indeed, you can. Kind 10000 mute lists support muting npubs, hashtags, threads, and words. Which of those types of items your client supports muting may vary. I had a rant about discrepancies in the way Nostr clients handle mute lists yesterday:
#nevent1q…5deh
We're building sth really cool with #hypernotes to let Service providers do just that:
Market themselves, beyond just some text.
Plus, it solves the in-app payments etc....
There anywhere that performs testing of such things that could be pulled in by the marketplace? If not, that will be on the relay owner to market why their paid relay is better than the competition.
Might be sth there yes. Will check in detail later.
Don't even need to do all that.
Just add `randomuser.me` to your muted words, assuming your client supports that. Aside from that, you can also read from better relays. Right now, your kind 10002 shows your are using 11 relays, including 6 public relays, as both inbox and outbox.
You're also using an indexer relay (purplepag.es) as an inbox/outbox relay for some reason... That one is usually just used by clients in the background. You shouldn't need to add it as a read relay manually. It aggregates kind 10002 events from other relays, so you should not need to write to it manually either.
Looks like you have auth.nostr1.com in there as a public inbox/outbox, too. This relay is for DMs, so it should go in your kind 10050, not your kind 10002. In Amethyst, that would be the section for "DM Inbox Relays." Looks like you have it there already, so you can remove it from your inbox/outbox relays.
Nostr.band's relay is much better suited as a search relay than an inbox or outbox. It's an aggregator, so your notes will very likely end up on it whether you intentionally write to it or not, and that's also why it is full of spam. No need to write to it directly. Good news is, you have it listed as a search relay, too. You can go ahead and remove it as an inbox/outbox relay.
You can keep writing notes to the public relays if you want, but cut your read/inbox relays down to nostrelites.org, wot.utxo.one, and I would recommend nostr.wine as an additional read relay, even if you don't pay for write access. You could always add another WoT relay into the mix to read from as well.
That said, a brief review of the public relays you are using shows that most of the reply spam is on nos.lol, nostr-dev.wellorder.net, nostr-pub.wellorder.net, and offchain.pub. Remove them as inbox/read relays and you'll be much better off.
Very useful, yes. For filtering the announced services.
My main question is:
How to announce them 😉
@nprofile…v40v
TF is this?
#nevent1q…5mx3
As soon as you added "credit card" you eliminated the possibility that it exists.
That's a very good point.
A marketplace where those offering services have to list them could still integrate WoT based rankings, though.
Say nostr.wine, nostr.land, and jellyfish.land each listed their paid relays in the marketplace and the user could pay for them directly within the app. They might still find it useful to see which of them was used most by those in their WoT.
"I'm going to forge ahead anyhow."
Translation: The push back is not compelling.
Thanks for the update!
Your time is more scarce than Bitcoin, so I get it.
Yeah, not sure if the seller was using Shopstr for DMing me. May have been, or may have been using another client with NIP-17 DMs.
Either way, even after providing tools that allow media to be encrypted, users will still need to take advantage of it. I could 100% still see some users uploading directly to a public Blossom server and copy/pasting the URL into the DM, thinking they're all good because DMs are encrypted.
Not really anything that can be done about that.
They have a few different options available, but I can't picture a scenario in which it would be worth it.
For instance, buying instant hashrate to point toward your pool currently costs 73 sats/th per day, but my home miners are only earning me about 60 sats/th per day. Assuming I would earn about the same amount per TH purchased, I would be losing 13 sats a day on the deal.
Taking a look at the hashrate auctions (bidding on hashrate to be delivered at a later date) it looks like you may be able to score a bit better deal there. A lot of the auctions seem to have been closing at around 50 sats/th per day, which would translate to about 10 sats profit/th per day, assuming you win the auction at or below 50 sats/th.
They also have the "Fixed Return Mining" option, which costs about 47 sats/th per day. However, this option you just keep mining until you receive a set return with an estimated profit of about 67,500 sats... over a period of 95 days... Though it could be a shorter period if you reach the target sooner, or it could be a longer period if you still haven't reached the target in 95 days. That works out to around 1.42 sats/th of profit per day, before taking pool fees into account. And remember, pool fees are calculated on your total revenue, not your profit. So your revenue is estimated to come in at about 2,318,000 sats for the full 95 days, the cost of purchasing the hashrate is about 2,250,500, and a pool fee of even a minimal amount of 1% is 23,180 sats. Meaning you would only actually make about 44,320 of profit, or about 0.93 sats/th per day, or 0.45 sats/th per day if your pool fee is 2% instead. Oh, and there wasn't any available hashrate for this buying option at the time I looked, either.
Sound enticing yet? Not to me.
This cookbook from 1936 is wild. https://nostr-relay.derekross.me/421d0d31ecf9151440e9196b4017c5a40891c7fee64005470071d035fa125baf.jpg https://nostr-relay.derekross.me/953f92283f93ef72ca79548a617d117f58e6708bd47cf12a9dc1d2789e9bfc28.jpg
The largest bank in the world just bent the knee to bitcoin. Not priced in.
https://m.primal.net/Qywx.jpg
One combo I like is using Algo Relay by @npub1utx…50e8 paired with Jumble.social or Coracle.social, which both allow you to view a specific relay's feed. You can go to https://algo.utxo.one to set your preferences for the weighting of the algorithm, then view its feed in Jumble or Coracle.
Amethyst also can display DVM-based algorithmic feeds. The same ones Primal uses. I think Coracle can access those DVM feeds, too, but I haven't played with them there, as Coracle doesn't give you an interface for browsing the available DVMs. You have to search for them by name or key word.
Here is the updated agreement (Section 3.K).
✅ We work with partners to facilitate the loan
✅ Your collateral is securely held in segregated wallets with us and partners
✅ Your collateral is NEVER rehypothecated, on-lent, or used in any other way
Our goal is to offer the best possible terms and experience for Bitcoiners. We will continue to iterate with you all based on feedback. Next up, we plan to provide proof-of-reserves based lending.
We work for you, #Bitcoin. Thanks for the feedback.
We want to be the most customer focused company in the world. Built by Bitcoiners, for Bitcoiners.
https://blossom.primal.net/1c24864b9937095389c5d0b485b723b0690aab59408f9339850ee0622afe4b71.jpg
#nevent1q…ltd7
Deletion can never be proven anyway, so one should always assume that the data is still living somewhere. A request to delete is the best you're going to get.
It would still be nice if more relays supported NIP-62, but even then, your data may have been mirrored to other relays you don't even know about and that your deletion request never makes it out to.
I couldn't care less so you shall have the option #bip177
https://blossom.primal.net/53ae162b41a157a265513270e5644f9103a076066fcf7faa9aff59d0ee3ff0f2.png
Posting Killdozer quotes to LinkedIn to help build my professional network.
Collecting and drying various things from the garden at the moment:
- calendula for bathtime
- chamomile for tea
- lemon balm for tea
- tulsi/holy basil for tea, also used fresh in thai dishes
- dandelion for tea in the winter
https://blossom.primal.net/d2650490934c2def63b07117ee204c4c5f2e137b3ea244b58fe65ad2194b6f72.jpg
Right, it needs to be conscious as it were. That said, on iOS there really is no tradeoff if going the cloud enclave route, assuming it's engineered right. In fact even for Android I think the enclave route would be preferable to Amber in many ways. (Not being on Play is already some amount of friction for Amber.)
That makes a lot of sense. Quite unfortunate for those who would like to have a tool like Amber on iOS, but it kind of needs to be awake in the background waiting for signing requests in order to work locally.
It's fine. You're working on encrypted media in private communities and DMs right now, right? That's HUGE!
Example: I had purchased something via Shopstr and the seller sent me a screenshot back, confirming my address before shipping to me. Thing is, he was using nostr.build for media hosting and so, even though the image was sent in a DM, it was not encrypted and was there for all the world to see in nostr.build's free image gallery.
Thankfully the guys over there at nostr.build were quick to take it down at my request, but it's a good lesson in why we NEED encrypted media in DMs.
Interop for muted words can wait.
I'm not sure, looks like it's either paused or abandoned from the github link. Whatever the state of it, there are fundamental limits that neither it nor anything else can overcome on iOS, the main limit being long-running background tasks; those can only be used for 7 or so specific things, and nothing on that list of specific things corresponds to signing Nostr events. (You have to use some clever workaround to keep the process going in the background, like playing silent music, which is cool but won't scale out of test flight as sooner or later a reviewer will see that.) And even if you go that route, you still run up against limits like the need to run the signer app every time you restart your phone etc. You basically need the cloud involved *somehow* for it to be a scalable and user0friendly UX, just no two ways around it.
Thank you sir!
I really think this encrypted mute list issue may be more of a source of the mutes not working in Pokey than the relay issue. Most users have at least one relay they use as both inbox and outbox, so the chances are that Pokey is finding the mute list just fine.
However, I would wager that a vast majority of Pokey users are also using Amethyst, which is encrypting ALL mute entries. If Pokey isn't able to see those mute entries, then no wonder people are still getting Pokey notifications from people they have muted in Amethyst.
Not at all, I've been meaning to fix this for ages, just haven't gotten to it (and probably won't for a while either)
You mean "thorn in the side"? 😂
I only noticed this discrepancy between clients because with all the adding of muted words to banish the reply spam lately, I saw that adding a muted word in Amethyst didn't translate to it being muted in other clients, even if they supported muted words.
Me being me, I had to dig into it and find out why that was the case.
Thank you for the response with insight into your reasoning for going the route you have with Nostur.
I think I would disagree with the approach, but I definitely understand why you have gone that route.
That said, I do fully agree that a mute list is data that does not need to be public. At the same time, I also see the value of having certain types of mutes public, such as muted scammers and spammers, so that those who have me in their WoT can also benefit from my having muted a scammer or spammer, even if they have not yet done so.
When it comes to "let relays be relays, not personal storage," I think you might have a case if we were talking about using relays for storing media or something. But we're not. We're talking about storing a long-standing standard event kind that is defined in a merged NIP and utilized by most major clients. Moreover, if public relays are not on-board with storing that information, they can reject that event kind.
You mentioned that "last seen" metadata is still leaked, even in encrypted lists. I am not familiar with that means. Does the npub that was muted somehow have leaked to them that you muted them, even when the entry is encrypted?
The temporary blocking/muting I absolutely understand needing to do locally. I agree that there is probably not another way to do it. However, other clients, such as Damus and Nostrudel have temporary mute options while also utilizing kind 10000 for permanent mutes. My guess is they do the temporary mutes locally, and honestly, a user probably wouldn't want temporary mutes used for influencing other users' WoT filters anyway.
In my testing so far, the only culprit that nuked my mute list was Primal, and it didn't nuke the whole thing, only the encrypted mutes. There will be no nuking of mute lists if clients are all on the same page about what sort of content should be expected to be found in the list, and then including that data when replacing the previous list, even if their client doesn't use the data for anything.
I am definitely liking your approach to doing a lot locally, and having a manual option to "announce," such as how you implemented the relay settings. I have seen it be a bit confusing for users, but having that ability to read from or write to relays you haven't announced in your kind 10002 is ideal. Moreover, I feel like Nostur is aiming at being a gorgeous client for power-users, rather than a dumbed down client for newly hatched nostriches. Take that approach with mute lists, too, as mentioned above, and I would say that's a near perfect approach.
How do you plan to handle the encrypted data in the kind 10000 at the time of import, if there is any? Decrypt it and store it locally and on iCloud unencrypted? Ignore it so that only publicly listed mutes will be muted in Nostur after import? Import it and use it, since the user presumably would not want to see notes from those they have muted, even if they did so through a client that stores the entry encrypted?
Whatever approach you take, when "announcing" the mute list that is stored locally, is there a way to make sure that Nostur only adds the local mutes to the new list, without removing entries (particularly encrypted entries) that are already on the standard list? It would be a shame to announce some mutes that were added on Nostur only to lose half of the mutes added in other clients that use the kind 10000 directly.
I’ll take a stack of Orange backs!
https://blossom.primal.net/f3c2b6ea7f1bf8651c765b870bb142d96162cd21745c15ab418fe662ed93021f.jpg
Do you know how Yeti, being worked on by @nprofile…tkd5 differs from those you mentioned, including your own approach?
this always makes me laugh
https://i.nostr.build/BRXCqKNQRur1kRSa.jpg
good morning the government hates you
https://i.nostr.build/ZSa17okqH7R56vtO.jpg
There is so much taste inside of elderflowers. Last year I dried about the same amount and my stocks go empty now. Time to restock 🌸 No need to add sugar!! 🤍
https://image.nostr.build/4e1bb539695b0b39ae4069496ac61f75d9d9b518a20c23a1a71b0c28d8261c52.jpg
Today is June 4th, which marks the 36th anniversary of the Tiananmen Square Massacre. But you might not know why Tiananmen is still an enduring symbol of Internet repression.
Tiananmen was part of the reason I got into Bitcoin in the first place. I used to be part of commemorations of the event - I remembered that many of those who attended wore masks - afraid of agents of the Chinese state that would harass them and their family back home. I wondered about the dystopia of never having ease even 5000 miles away.
Tiananmen is still censored in the Chinese Internet, with even mentions of the date getting wiped off. This has led to a cat and mouse game where June 4th becomes May 35th and other variants to trick censors.
One of the first things the Chinese authorities did when they effectively took over Hong Kong was to ban public, non-violent rallies in Victoria Park in commemoration of the victims of Tiananmen.
One author has described his books as “June 4th” (China in Ten Words, non-fiction, banned in China) and “May 35th” (Brothers, fiction, not banned in China). Even today, to get literature or books published in China, you must strip away mentions of Tiananmen.
Tiananmen marked the crossroads between a faction of the Chinese Communist Party that wanted to grant more liberty and those who wanted to let markets run more broadly - at the cost of strict state control. That latter faction eventually led China to build the strongest version of Internet control possible - the Great Firewall that cleaves the Internet in two, and the same surveillance playbook of company, platform and government that now reigns as the default Bitcoiners and Nostriches fight against.
I’m happy to say that Nostr is one of a few pockets where open discussions like this can happen and that can actually cross borders throughout the world, backed by relays that can fortify this content how they choose - and that Bitcoin is playing its role to erode the systems of control that came partly because tanks met innocents that bloody day.
https://blossom.primal.net/49a4a9f2d4a243423cc3a89db86c56af10ba1b16153acc778a91861ac707eeaf.jpg
cashu.me now has translations for 8 different languages
https://blossom.primal.net/aa0ad8b52cf9bf8e3a42206ffb9fcd683e939da192568c96bd0f4646236feef8.png
translations were done by an AI agent.
this used to be one of the worst software development experiences *EVER*: replace every string in your application with a translation placeholder varaible and move all into a localization file and translate.
this was pure PTSD before AI.
https://blossom.primal.net/fcce3498588ac9191d38c4c758865df3e22543433fde5bb988e8bc7057712da2.jpg
Data Guy:
This is as intended, imo. When you see something like this, realize there are knobs, buttons, and sliders in the system that can adjust these things. Someone has their hand on those controls. It's not the poor people, huh?
Why do you think we — the richest country — have this curve?
Did you vote for that outcome?
Or did someone else tune it in?
@nprofile…fmt5 2025
Proof of Reserves helps protect you and your family from paper bitcoin, empty words, and rehypothecation.
Demand that your Bitcoin exchange implements it.
Switch if they drag their feet.
All bitcoin held on River is in proven full-reserve custody.
We prove to our clients each month that their unique balance is part of the total assets under custody.
You can walk through the flow on our page https://river.com/reserves
https://blossom.primal.net/dee9cd30b2f01d9df55f7f633f3586dcd2dac07422c163cf009a4cb580821cc0.png
For many years I had never seen the extraordinary fully zoomed out Tank Man photo
Today in China even the tiniest reference of Tiananmen Square or 6/4 (June 4) is live-censored by the CCP’s dynamic AI-powered surveillance system. Slowly erasing the event from people’s minds and family histories
Even imagery (for example a photo sent of 6 leaves and 4 flowers) is instablocked, with punishment sure to follow
THAT is the technological environment we must find ways for freedom to survive in
I absolutely believe it will happen. Life finds a way. Tyrants and empires always fall. But it won’t be easy or handed to us on a silver platter
https://image.nostr.build/0e939bd20b72e6e1111072d6ba4a01e7b7c8bbfefd9c9096f82286eca0892d59.jpg
https://live.staticflickr.com/6112/6222387752_5ef3b8c8e5.jpg
⚡️💬 UPDATE - 160 days on Nostr. That's 5 months and 9 days of hard work, every single day, to earn your trust and respect.
I started from scratch. An unknown. No contacts, no connections, the friend of no public figure, just the desire to make a place for myself on Nostr.
➤ 160 days donated.
➤ 159 nights sacrificed.
At 10,000 notes, I'll take stock: success or failure? In the meantime, I remain focused on one thing: achieving my goal - to live off Nostr.
Just hard work.
Late nights.
Early mornings.
And the kind of hunger you can’t fake.
This path isn’t easy.
But it’s real.
And when you make it—
you’ll know you did it.
Thanks first of all to God, without whom nothing is possible. And to those of you who follow, support and believe in me... thank you.
This journey may be mine,
but it wouldn't mean half what it does without you.
https://blossom.primal.net/d2e7ae87460cbe157a2355708da0d6d6eb7408a98caf47ed99b239f0c8d0ba85.jpg
https://i.nostr.build/c31czUUOAIiSNgxR.jpg
https://www.axios.com/2025/06/02/iran-nuclear-deal-proposal-enrich-uranium
It's hard to overstate how pathetic Trump is.
It's Iran. We can just destroy their pathetic, violent, county. We don't need to negotiate, let alone allow them to enrich uranium.
Tell Israel to destroy their nuclear power plants and oil/gas production by any means necessary and Iran's nuclear program and genocidal ambitions are finished. We don't even need to get involved.
It's the exact same pathetic weakness that has led Trump to accomplishing precisely nothing with Russia.
Gm nostr, i gotta get going early today, as i have alot to do. I'm wishing everyone a great wednesday, and remember to do your work with a happy heart. #coffeechain #homesteading https://image.nostr.build/b49b443936249af004be6fd747dcbf5e7c3760e418a7d27543d3d755ae22e3ef.jpg
Good morning to the greatest ppl on the internet! 🫡🫂💜
Did a test batch of "mechanics" soap yesterday, and cut this morning. This is regular Tallow soap, with charcoal and pumice added. https://image.nostr.build/eeb7d9b560e030e8e4057e2fd2508d73a525a4cedcdf9f5bed88711c99a325f1.jpg
Doing a Bitaxe giveaway at our monthly bitcoin meetup this evening at Waitabit Coffee.
https://image.nostr.build/7783408eb9b0a24475fb7d107127b2259b524e98fdad113436d80d23215c8534.jpg
cashu.me now has a unified list for all transactions https://blossom.primal.net/ba994cc7dede5a67e09c24bd113e0d31953ebc1ef6a6ff684d88b39447b7480f.png
"THERE WILL BE NO RE-HYPOTHICATION".
https://cdn.nostrcheck.me/2f5de0003db84ecd5449128350c66c7fb63e9d02b250d84af84f463e2f9bcef1/f157e841271cdf85365340409a20d882b059cfbe54cac20c55f72257e187a362.webp
https://cdn.nostrcheck.me/2f5de0003db84ecd5449128350c66c7fb63e9d02b250d84af84f463e2f9bcef1/0ffd0f1d9b5685c46140b341d50024e9125c58f96265225066d08fdd2e271015.webp
Wat dis?
New blog dropped!
Expect monthly-ish post going forward on merchant adoption and what we're up-to as a team.
https://npub1864jglrrhv6alguwql9pqtmd5296nww5dpcewapmmcazk8vq4mks0tt2tq.blossom.band/53bbef6801cf0ba29acce9bf655d7d221eef843fdde7db8e4598da936c1748f5.png
You can check it out here:
https://blog.btcmap.org/
Tanning is good for you ☀️
https://blossom.primal.net/c0532554d9c2204495297a8f7d5e6158ee9241c7db61ce17e455a195927b68a6.jpg
We're working on a platform for this, though for business us case first. Essentially the only scaleable options for iOS are those that are Nitro enclave based. No local options are scaleable. There are some neat workarounds, like Aegis or Nosskey, but if someone says there will be an Amber for iOS, there won't be, there cannot be.
Here's where this meme comes from.
Charlie Chaplin's Pay Day (1922)
https://blossom.primal.net/0b13b60c2870d8e0df03836dbd45e3ef21997668b23125b7b9fae300b04d3f8d.jpg
That’s my implied question.
What other method is there on iOS? There is no Amber equivalent on iOS yet.
In-app Hosting purchase.
That's what we're doing.
Will build on marketplace spec.
How about the encrypted mute items? Is Pokey decrypting and muting those, or ignoring them?
PoW Completed ✅🍶⛏️
36 bottles of homemade elderflower syrup.
Handpicked. Handcrafted.
This is my go-to drink.
Produce it now for the entire year.
My daily lineup looks like
💧 Water
🫐 This juice
☕️ Coffee
☕️ Maybe a few more coffees
That’s it.
No alcohol.
No sugar bombs.
Just clean fuel to stay sharp.
GM Bitcoin fam ☀️
Stay healthy. Stack hard. Live free.
Timestamp of freedom 899,738
Makes me think…
Since high-quality elderflower syrup is expensive as fuck and packed with sugar bombs…
I wonder…
Could I offer this self-made drink for worldwide shipping,
paid in sats,
on Nostr only? 💭
https://blossom.primal.net/357e005c85a395d8225ba1c2c836455c0c9fa60a8c0d5d244b33bbed5c2ab7bf.jpg
I don't know of anything like that.
Some sort of Nostr services marketplace where devs can promote their latest client, or users can compare the services provided by various paid relays?
It seems like a tool a lot of folks would find useful. I could even see it being worth having dynamic suggestions, based on your WoT.
Say you wanted to see recommendations for a Nostr address provider. If you're logged in, it could look at the domains that are most popular among your WoT, pulling the info from their kind 0, and display a ranked list to the user.
Similarly, if you wanted to see recommendations for Blossom servers, it could look at the kind 10063s of those within your WoT. The same could be done with relays, pulling from their 10002s to determine which ones are most popular.
GA👋🏽, Today I made garlic & pepper pork.
#foodstr #zapcooking #siamstr
https://image.nostr.build/ec644794ad63aa33baa3af9f726063356aecb05834c8815863c262da1e7e1444.jpg
look at this fat wild strawberry. Tasted fluffy like a marshmallow 🍓
https://image.nostr.build/82dcc27938e527fe016d6aa10ad2ee86b46605f81b89bc4af0dc20101ab3cb12.jpg
The ones I have I outlined here:
#nevent1q…q2m6
The first idea probably hinges on DMs working consistently for the notification when someone signs up that you invited, and DMs are quite a mess right now.
The second idea hinges upon more clients supporting PoW. The only one I know I can add PoW with right now is Coracle, but it's off by default.
I am also interested in hearing any ideas you might have about bringing the incentives of paid relays into alignment with participating in the guardianship of the network overall. You had mentioned that the way Bittorrent accomplished this was an example to follow, but I am not terribly familiar with the incentive structure there.
I just ran the numbers.
LEATHERMINT is more than 200 orders fulfilled and ~300 unique items owned by sovereign individuals.
GM #nostr, quick reminder to study #bitcoin.. 💜🧡
It happened in 1923 Weimar Germany. And it can happen again…
“There were stories of shoppers who found that thieves had stolen the baskets and suitcases in which they carried their money, leaving the money itself behind on the ground; and of life supported by selling every day or so a single tiny link from a long gold crucifix chain. There were stories (many of them, as the summer wore on and as exchange rates altered several times a day) of restaurant meals which cost more when the bills came than when they were ordered. A 5,000-mark cup of coffee would cost 8,000 marks by the time it was drunk.”
- When Money Dies: The Nightmare of the Weimar Collapse by ADAM FERGUSSON WILLIAM KIMBER — LONDON, 1975
https://image.nostr.build/88e429170fd45ce1b74b82ff17e24f47ea5ff36aa02c99b293cae424c3a7b120.jpg
I had never heard of this tool for restoring replaceable events! I have used a couple others, but this one is really versatile!
I was testing out mute list discrepancies between various clients earlier today and Primal nuked all my encrypted mutes from my list. Was able to restore them all!
THANK YOU!
on this day a year ago
https://blossom.primal.net/f3538187f4096c5e3255bd24eb0b964f7c1bed56ef3e21c413b4de28de7ff3db.jpg
Yeah, it really doesn't weed out much that you might want to see, unless you have a very small web-of-trust.
Coracle also has the ability to display notes from those outside of your WoT that meet a minimum proof-of-work you configure. Very limited usefulness, though, since most clients don't support adding PoW to notes.
I also lean toward private mutes, but I am also sympathetic to use-cases like @nprofile…u0w6's web-of-trust scoring that deducts score based on how many within your WoT have muted a given npub.
That's another way that choice is advantageous, though. The ones you would most want to be taken inter consideration for WoT scoring would be muted scammers and spammers, which a user probably has no issue being publicly shamed. Whereas the mutes you most likely want to have kept private are just people who you don't get along with, and that sort of reason for muting probably doesn't need to be taken into consideration for WoT score, as others may get along with them fine.
Serves me right for testing using my main npub... 😂
I like what @nprofile…n0c5 is going to do with Jumble, giving users the choice between "private" (encrypted) mute or "public" mute.
I can see there being situations where a user might want to use one or the other.
Looks right up my alley! I'll hop in and take a look later this week or early next.
I have to go dark on Nostr for a couple days to prepare a couple messages I will be delivering this weekend, then I should have some time available to dig in.
You've got a couple things going on here.
As @npub1qqq…eecw mentioned, your npub stays the same no matter what else you set up on your profile. You can change your display name, change your Nostr address, change your Lightning address, and change your bio information all you want and your npub will still be what it is now. It's like a unique fingerprint for finding your notes.
That said, it's not exactly something people can easily type in when trying to find you. They could try searching for your display name, but there might be a lot of Neals out there in the Nostrverse. They are just as likely to find another Neal as they are to find you that way.
To make it easier to find the correct npub without having to type it in, Nostr addresses were created. This is a way to register your npub with a particular domain. That way, someone doesn't have to know your npub. They can instead search for [name]@[domain.com], which is much easier to write down for someone, or to remember. When this search is performed, the Nostr app reaches out to that domain and effectively asks, "Hey, do you have a 'ModernChains' registered with you, and if so please give me their npub." There can only be one "ModernChains" registered with a given domain, so the Nostr app will only get one npub back as a response. The Nostr app will then check that Nostr profile and confirm that the Nostr address matches the domain it reached out to. If it does, it will be displayed in the search results to the user. This sort of address, defined in NIP-05, is what you got from nostrplebs.com.
The next thing is a lightning address. This is completely separate from a Nostr address and is used for receiving sats on the Lightning network, utilized on Nostr for zaps, which you are likely well aware of, given that you have been sending and receiving zaps.
Here's where things can become a bit confusing. Both of these addresses (Nostr and Lightning) can be the same. Nostrplebs allows you to use your Nostr address with them as a Lightning address by forwarding any Lightning related requests to a different Lightning address you give them. For instance, my nostrplebs address forwards to my coinos.io Lightning address at the moment. Primal, on the other hand, has their own Lightning wallet. So you can use your primal.net address both for receiving zaps to your Primal wallet AND as a Nostr address to make it easy for others to find you on Nostr. However, Primal does not allow you to forward zaps sent to your Primal address to a different Lightning wallet.
Now, you are probably still registered with nostrplebs.com, even though you have updated your profile to use your Primal address. However, you can only have one of them active on your profile at a time. If there was a monthly subscription required for nostrplebs, I might suggest you make sure you cancel it if you have decided to use your Primal address, but they're a one-time cost to register, so it doesn't make any difference.
nostur has a web of trust spam filter built in to the app
works incredibly well
there is no spam
https://nostur.com
I just created my own fucking payment card network. #nostr #safebox
GN
https://image.nostr.build/b33db1e132d1077e7486322f4e7fd7a6546e40372b11feb6414bcd4a847b0ddc.jpg
Not bad for a Tuesday.
https://blossom.primal.net/41783e4b37c95066da6b71c021dfef1d21282aa9cc8d4e059064cbe51974c6d8.jpg
Coracle is easy, and it works for all future spam attacks, too. Go to Settings > Content and set the Minimum WoT score to at least 1.
Not a one. I don't read from public relays.
You can add muted words, too. Just recognize it will only work for this particular spam attack and you'll have to figure out what words you should mute on the next go-round.
This time, adding "randomuser.me" will get the job done, since that's where all the spam bots' profile pictures are hosted.
Of course, you also have to be using a client that supports muting words.
Yes. Inviting someone to Nostr should come with some way to be notified if they accepted the invite, so you can immediately follow them, bootstrapping them into your web-of-trust. I believe @nprofile…9wgx is working on something like that with https://nostrmeet.me/
Another thing clients could do is default to adding a certain amount of PoW to new users' notes, defining new users as those with no kind 10002 relay list, or no notes on their outbox relays with a timestamp older than X number of days. The exact number of days someone should be considered new is debatable and each client could use a different length of time. Then, clients could default to showing notes from npubs outside of the user's WoT that meet the minimum PoW. Coracle has the latter option, for instance, but no default PoW added to notes for new users.
The above could even be paired with a feature like Nostur has, where you have a few seconds to cancel a post before it is written to your relays. That way if you see a typo, you can cancel and fix it before it is permanently on display. During that few seconds, the client could be performing the required PoW.
Yes. All entries added to a kind 10000 from Amethyst are encrypted, as far as I can tell. Whether npubs or muted words. Which means other clients that don't support private entries on the mute list won't have those npubs or words muted at all.
oh right, and it's all private too
No. Just "block," which is really "mute" by a different name.
This is a good point. Muting spammers and scammers is probably fine to be public. Meanwhile, muting people who annoy you for other reasons might be better private. 😂
I might be remembering wrong... does it have both mute and block?
Amethyst allows you to choose whether the mute is public or private? I am not seeing any option to select that.
some combination of invites and WoT is the only way I see short of imposing a direct cost
Hadn't thought about it that way, but you're absolutely right. So long as spam isn't an issue, there's no demand for paid relays. No one feels any pain from not having them. Therefore, the best way to drive demand for paid relays is to generate spam.
That said, I wouldn't accuse any particular paid relay operator of being behind the recent spam attack without some pretty damning evidence, and I don't think anyone has accused any particular relay operator. At least not that I have seen.
Chances are that the bulk of what most of us would consider spam is just being perpetrated by people who like to cause trouble simply because they can, or because they think they are making a point.
Spam on public relays is inevitable, no matter who may be behind it. You will find it on any sufficiently large network where the following are true: 1. It's free and easy to create new identities on the network. 2. New identities can write data others will see without a cost.
On Nostr, we're not able to make it difficult to create a new identity. Nor would we want to. That means our only option for mitigating spam is to impose some form of cost for new identities to write data to relays that others will see. Public relays impose no cost at all, so they are guaranteed to have spam.
The three typical means of imposing costs to writing data to a relay are social, computational, or monetary. WoT relays would be an example of social cost to gain write access. PoW relays would be computational cost, but we hardly see any of these in the wild since most clients don't support adding PoW to notes. And, of course, paid relays come in as the monetary cost option.
It's a tough nut to crack, though, when you are trying to encourage the network to grow. We WANT new users to come here, and we want them to have a pleasant experience so they will stay. Adding social, computational, or monetary costs in their way is antithetical to that goal. Yet, new users are also the ones most likely to be spam bots that will make the experience of new and existing users alike unbearable. Costs should therefore be imposed in such a way that they are virtually unnoticeable to legit new users, but are prohibitive to spammers.
I have a couple ideas how that might be achieved.
There's dumb. There's stupid. Then there is the fucking retarded.
https://blossom.primal.net/9360ecfe220879cfc796233fde2092046358e900856f41ee03542f019dc14c01.png
Bull market present to myself. Custom chefs knife.
Could not be more pleased with the way this came out.
The bladesmith is https://www.bushkillblades.com for anyone who’s interested.
https://blossom.primal.net/2304abc6a147469324f89a49a2dd94a1d6df807f0860f90a6f310ca67831ecc3.jpg
https://blossom.primal.net/7b88ffe5499e17a1ce080ba82666f01be0c7bb424e946b9b39476e13798729c5.jpg
https://blossom.primal.net/33f06be6fddc335d55d7178ae2a47c0a5aa9e3244d195bb100c3df306d950e23.jpg
Keep On Movin’ full music video! Got to explore some pretty fun spots around Kelowna, and re-live my hockey playing days while shooting this video. Enjoy!
@nprofile…q275 5000
https://wavlake.com/track/de2ea7f4-3d5c-4933-b89f-2e4edec8186f
https://blossom.primal.net/70f88b2e3408b6de5d3106cb9b034aa42bfe9bbdaba613ec618396378ae93810.mov
I think @npub1syj…f6wl will implement an option to mute public or private.
I can't believe I didn't even check Jumble...
Jumble appears to add encrypted entries to your kind 10000, similar to Amethyst. Which is great for Jumble, but whoever you mute there won't be muted on any client that doesn't support it.
It’s so over… 🥺
https://image.nostr.build/1b8127129daabac3254271e24ca0f530a1b063c6e79348d9a390d45454c4735a.jpg
Ok, it's time to gripe a little bit, as I discovered an annoying lack of interoperability between various #Nostr clients that really ought not to be the case:
Mute lists.
Beware, this is a bit of a long one...
When a user mutes an npub, or a word, they don't want it to only be muted in Amethyst, and not muted at all in Primal. They want it to be muted across all Nostr clients they use.
The standard mute list, according to NIP-51 is kind 10000. All users should have exactly one of these, and relays should only keep the most recent version.
Mute lists may contain a few different types of muted content:
1. Muted users/npubs, designated by a "p" tag.
2. Muted hashtags, designated by a "t" tag.
3. Muted words, designated by a "word" tag.
4. Muted threads (such as hellthreads), designated by a "e" tag.
Some clients also encrypt the entries added to the mute list. While not required, it is part of the spec that clients should expect to see within a kind 10000, and I think it should be preferred. A given npub should not be aware that another npub has muted them and unencrypted mute lists are readable by anyone, unless we move to only saving mute lists to relays that can require AUTH to read them.
Yet, I see a wide variety of handling of mute lists by clients.
#Amethyst uses kind 10000 as expected, and encrypts all content saved to the mute list (hooray!). It seems to support muting npubs and words, and has no support for muting hashtags or threads. @npub1gcx…nj5z, please chime in to correct me if I have misrepresented anything here.
#Coracle uses kind 10000 for muted npubs and also decrypts the muted npubs that were added by Amethyst, so they are also muted on Coracle. However, users muted on Coracle are not encrypted. I imagine this is because Coracle is trying to use mute information for the sake of building web-of-trust scores (mutes by those within your WoT count as -1 in the scoring), and any encrypted mute information cannot be used to calculate those scores. Also, though Coracle supports muted words, it does not seem to see the words I have muted from Amethyst in my kind 10000, and seems to be keeping a separate list, because words I have added in Coracle don't show up on my kind 10000, and are therefore not seen by other clients. @npub1jlr…ynqn, can you offer some clarity on how Coracle handles mutes, especially regarding muted words?
#Primal web seems to have an old kind 30000 list with only two npubs listed, while Primal Android didn't show any muted users at all, but adding a muted user added the npub to my kind 10000, which suggests Primal simply doesn't support decrypting the other entries that were added from Amethyst. Also, muting an npub on Primal resulted in all the encrypted entries on my mute list from Amethyst being nuked.
#Nostur did not display any of the above. Not my kind 10000, encrypted entries or not, or the kind 30000 Primal had been using at some time in the past. Adding a "blocked" user in Nostur also did not add them to my kind 10000 and did not add any other list type that I could find on listr.lol either. I am guessing it is using a list kind that isn't recognized or is just storing blocked npubs locally. @npub1n0s…lahe, can you provide some insight into how Nostur is handling mutes/blocks, and why it doesn't seem to be using kind 10000?
#Damus appears to be using kind 10000, but only shows entries that have not been encrypted. However, when adding a new blocked user, it does not appear that Damus wipes out the encrypted entries in the list. If not supporting encrypted entries within your client, this is the best way to handle them, rather than erasing them when replacing the kind 10000 as Primal did.
#Nostrudel behaves much the same as Damus, using the kind 10000 and only showing entries that have not been encrypted, but also not wiping encrypted entries when adding a new entry.
#Pokey also seems to have trouble respecting mute lists for the sake of muting notifications. This appears to be because Pokey only looks for your mute list on your inbox(read) relays, while users publish their mute list to their outbox(write) relays, and those may not necessarily be the same. However, I wonder if it is also an issue of Pokey indeed being able to find a user's mute list, but not taking encrypted entries into consideration. @npub1v3t…yvjh, can you confirm whether Pokey is able to mute notifications from npubs that have been encrypted in a users mute list?
Is it possible to get these and other major clients on the same page about how to handle mute lists?
Yesterday, @nprofile…8jsn posted this about what interoperability means on Nostr:
#nevent1q…d6zu
I pointed out that in order for this to be the case, we also need to agree on the format and expected content that will be contained in a specific note kind. From what I can tell, there is little agreement on how mute lists should be handled.
Should they include encrypted entries? If they do, should clients respect the encrypted entries, since the user who created that kind 10000 certainly doesn't want to see notes from the npubs they added to their mute list, encrypted or not? Clients certainly should not nuke encrypted content from the mute list if it is present, right? Or should we drop support for encrypted entries on mute lists altogether, since some clients are relying on mute lists from npubs within a user's WoT to determine what content is likely to be spam?
Users just want to know that when they mute an npub or a word in one client, that it will also be muted in other clients, and that muting in one client won't nuke their mute list in another client.
My cousin, a financial advisor, every time I ask him how his diversified portfolio is going:
https://relay.utxo.one/fd45dd0bd7f54ba0272265e99372ff5f4b841ea3c8867be2601b8cbb545d044e.jpg
Ok but what do they bench???
https://m.primal.net/QyqN.mov
姪、爆誕！
https://image.nostr.build/676957c321020ce85198ccf05b1be14500f7a3583b222339995e8b23628ea242.jpg
It's one directional, as far as I can tell. You need to upload the media using https://blossom.band to get a blossom URL for sharing the media, and it will also show up in your nostr.build dashboard.
If you upload directly to your nostr.build dashboard, though, you can't get a blossom URL for sharing it. Only a standard nostr.build one.
Does nostr.build give me a blossom server URL that I can throw in things?
#asknostr
🚨 BlackRock just dumped $561M in Bitcoin… and bought Ethereum.
Good.
Let the suits run.
Let the cowards fold.
Let the paper pushers chase yield.
Because here’s the truth:
Bitcoin doesn’t need BlackRock. BlackRock needs Bitcoin.
They sold 5,362 BTC.
They grabbed 27,241 ETH.
Why?
To feel safe. To stay compliant. To chase their little ESG staking narratives.
This is what fiat minds do. they trade truth for comfort.
They abandon hard money for a programmable toy wrapped in Silicon Valley promises.
But Bitcoin?
Bitcoin doesn’t compromise.
It doesn’t bend to the SEC.
It doesn’t need hype, upgrades, or CEOs.
It just keeps going. Block by block.
Untouchable. Unstoppable. Unapologetic.
So no, I’m not impressed by their move.
I’m not worried.
I’m not selling.
I’m doubling down #Nostr
Because when this fiat clown show ends,
you’re either holding the hardest asset on Earth,
or you’re holding the bag.
Keep your #ETH.
Keep your ETFs.
Keep your permissioned games.
I’ll keep my keys.
I’ll keep my #Bitcoin.
I’ll keep my freedom.
This olive tree in Greece is 2,000 years old
https://blossom.primal.net/6420e2e223837139bd2a8539a26e004007e2641dfa35499bc719fc6f879a54ca.png
Also, muted words seem to be very client specific.
I have muted words on Amethyst, but they don't show as muted on Coracle. Instead, I guess I had added a different muted word there. Then Primal shows I have no muted words at all. Same with Damus.
Now I understand that there are plenty of folks out there who only ever use one client, so this isn't an issue for them. They can mute a word on their preferred client and it's all gravy until the next spam attack and they have to add a different word.
That's not the case for users like me, though, who use a wide variety of clients. Read relay selection is a solution that should work with most clients, and it should work against current and most future spam attacks without additional configuration needed.
That's fair.
Again, muted words is a great feature, and definitely one to have in the tool-belt for dealing with this kind of nonsense.
I have also been very happy with how well reading from WoT relays and paid relays has worked on most clients. I also wish more clients would support adding PoW to notes so that relay operators could realistically add minimum PoW requirements for anyone outside the WoT to also be able to write to the relay without flinging wide the gates to spammers.
Yeah... count me out. When I need to spend, I'll take the cap gains hit.
If you have a profitable job, then live within your means and save in Bitcoin.
If you are retired or between employment, this is what you saved for. Spend wisely and not frivolously.
If you are wanting to start a business and leverage your stack to do it, then maybe I can see this being an option for you, but I know there will be plenty of people who think they are making a sure bet, only to end up with Mallers owning their Bitcoin in the end.
I also can't understand the mindset of the person who is lending their fiat into such a scheme. Real inflation is upwards of 8%, and "risk free" rates can't come anywhere close to that on a 1 year horizon (remember that these loans are only 1 year terms), but these lenders are willing to put up capital at a return that maybe keeps pace with inflation, depending on what margin Strike is getting, when they could put the same money into Bitcoin, with a 5 year CAGR currently sitting at 60%.
The only explanation is that they think lending the fiat with fiat interest income will outperform Bitcoin over a 1 year time horizon, or else they would simply buy Bitcoin with that fiat they are lending.
Until that anchor is something shared with legitimate users.
Say they all start using a free Blossom server to host their profile pics (like Nostr.Build), and MiniBits or npub.cash for their lightning addresses. Then using muted words will block a large chunk of legitimate users along with the bots.
"As long as it's not Biden."
NPCs need #Bitcoin and fast.
https://blossom.primal.net/805de05fe6b351620ae017c611aa6014a70458f391893f4a48c8ca43404ca64a.jpg
The beauty of it is that in order for bots to sell their thing, they need some type of anchor. It's either the name, the url, ln address, some keywords in the post or their about me... Etc. There is always something. We just need to figure out what that is and block it.
The hidden words feature is really a superpower that more clients need to implement. I remember that we used it as a band-aid during the old reply-guy spam back in late summer of last year, too.
However, it is just that: a band-aid. It stopped working when the bots no longer used the words we were blocking, and this one will fail, too, if they stop using that user generation service to host their profile pictures.
Reading from relays that are better at spam mitigation is a more robust and long-term solution. And I say that as someone who does not run a paid relay I am trying to shill.
Exactly. When it comes to where they are more likely to find users who will make them money by using lightning every single day, it's a far higher concentration here.
@nprofile…aswu will this stop the yoda bots?
https://blossom.primal.net/c279d8db27fa36e6770a844257ae57a365136d43a4676cc11f3ae2a3bcb450f2.jpg
Alas, remember when @nprofile…w35w hung out here instead of Xitter?
Meanwhile on Xitter... 👀
https://cdn.hzrd149.com/f9ac31c9f9e05da3ea102a9034245d8cd38f7f9e82e3e728474d24a4d9019a79.png
👇
https://xcancel.com/walletofsatoshi/status/1929330378319503606?t=lA4YCvZRw9EDiO8R1E7YcA&s=19
GM
https://image.nostr.build/73e539034478f7b0fd24f04de214aef16e0dcd9055fc04a7425f5cdaf2cdf507.jpg
I’m having different problems with @npub12vk…pugg (iOS) where all my zap presets have disappeared and there’s no way to restore them. The restore defaults link doesn’t do anything.
Nothing I’ve tried has worked. https://m.primal.net/Qyjz.jpg
Yeah Primal having issue where I post multiples times and it does’t show, then go over to other clients and it shows them all. Then I try to delete all except one, but often end up deleting them all. Also multiple missed notifications on Primal. I'm guessing they tweaked something for the spam and now things are out of sync.
We're live right now! Come hang out!
#nevent1q…r9rs
#Minecraft #Minecraftstr #Gaming #Gamestr #Bitcoin #Lightning #ZapStream
It looks like hyperDHT requires UDP, so you would need a bridge anyway.
No, that would be more like how p2p stuff usually works. NAT traversal is apparently a huge pain, in this scenario all messages would be proxied by the brokers
I like that yours is using a Nostr relay to establish the connection. Once the connection is established, everything else is just straight from client to community relay, right?
Could work, I just don't know much about pear. In either case, it's a new transport protocol, so in theory they'd be functionally equivalent
This is definitely one of the biggest hurdles to running a relay for just about any purpose, not just communities.
What do you think about the possibility of using something like Pear runtime for connecting to a community relay?
I had an idea this weekend for how to make running community or personal relays easier for non-technical people by piggy-backing on commodity relays to avoid dealing with DNS/incoming connections. This would allow people to simply run a "relay" on a computer they own, but have it publicly accessible.
The way this works is via a DVM-like flow, where the user NIP 59 wraps a message to the relay's pubkey, sends it to a public relay where the target relay is listening, and waits for a similarly wrapped response back.
I call these "kelays", which is a terrible name, but the best I could come up with within 8 seconds. You can see my proof of concept implementation at https://github.com/coracle-social/kelay. The go program allows proxying any relay, and the `example.sh` uses `nak` to demonstrate the flow.
People could address these using something like `kelay://<pubkey>?relay=wss://relay.example.com&relay=wss://relay.example.com` This obviously routes traffic through hubs, but I think that's a reasonable trade-off, especially with the option to use multiple broker relays.
What do you think? This could obviously be abused in any number of ways, and I still have to figure out how I can make NIPs 42 and 98 work. And maybe some other p2p technology would be more suitable for hole punching. But this is the kind of left-of-bell curve solution that made nostr famous, so I'm reasonably optimistic about it.
#MinecraftMonday will be back today, starting at 4:00pm Pacific time (2300 UTC)!
https://relay.brightbolt.net/327c71e49a072b55a392d3c71c7338dce68bb901355ed18d2489434a5570d54a.jpg
I'll be checking in on my auction-house listings, getting a ton of sand, and mining for ancient debris. Maybe even hang out with some friends on the server.
If anyone wants to join in, you can use the latest version of Minecraft Java (recommended) or Bedrock. Go to https://sovereigncraft.com/
#Minecraft #Minecraftstr #Gaming #Gamestr #Bitcoin #Lightning #ZapStream
Got this reply 3 times. 😂
Interesting that Ditto renamed sats to zaps...
@nprofile…t7fy is this intentional to try and rename sats, or are we meant to understand that the zap total is 84 sats?
I think it would be the other way around in this case. Why not rename dollars to tips?
Yeah, but we're talking about people here, not just nodes on a network.
"Connect" has a relationship implication in the context of people connecting with one another that isn't implied when talking about nodes on a network.
More importantly, a personal connection is something stronger and more meaningful than what is happening when a user adds an npub to their kind 3. They may have no personal connection to that npub at all. It just means they want that npub's notes to show up in their home feed.
Just another spam attack that is probably intended to show Nostr's susceptibility to such things and encourage devs to build solutions.
Thing is, we already have some pretty good solutions!
Here's my canned suggestion for reducing or eliminating spam:
If you are seeing a lot of spam in your replies, it is because you are reading from relays that spammers can write to for free. Spam can only happen if two things are true: 1. It's free and easy to create new identities. 2. New identities can write notes to relays without a cost.
We're not able to, nor do we want to, make it difficult to create a new identity on Nostr, so reducing spam by making new users jump through hoops that can only be enforced by a centralized entity is not an option.
That means we need to prevent it via option 2, by restricting new identities from writing notes to relays without a cost. If you are reading from relays that don't impose some cost to write to them, either social, computational, or monetary, then you are bound to see spam on a regular basis.
Instead of reading from free and public relays, you should consider trading them out for the following types of relays:
- Web-of-Trust (WoT): This relay type imposes a social cost in order to write to it. Namely, you have to be followed by the relay owner or one of the npubs the relay owner follows before you can write notes to the relay. These types of relays may also automatically aggregate notes from those within the web-of-trust, even if they were written to other relays.
- Proof-of-Work (PoW): This relay type is less common, and it imposes a computational cost to write to it. Only those who have dedicated computational energy to generating the required PoW can write to the relay. This cost is trivial for the honest user, who only posts up to a couple times a minute, but imposes heavy costs on spammers, who are trying to post hundreds or thousands of times per minute. Unfortunately, most Nostr clients don't support adding PoW to notes, so most relays don't use it as a spam mitigation measure.
- Paid Relays: As the name implies, this relay type imposes a monetary cost to write to it. It may also impose a cost to read from it, but that is less common. Since this cost is per npub, and spammers don't ever use just one npub since that's too trivial to mute and move on, this makes paid relays affordable for honest users, but too expensive for spammers.
Since the only two relay types above that are currently in wide use are web-of-trust and paid relays, here are a few suggestions for each.
Web-of-Trust:
- wot.utxo.one
- nostrelites.org
- wot.nostr.net
Paid:
- nostr.wine
- nostr.land
- jellyfish.land
OS?
If Android: Amethyst
If iOS: Nostur
Shipyard is 1000% better. lol!
Hivetalk is a video meeting app and they have recently added more features, including scheduling posts.
Highly recommend checking it out!
Ah shit, you remember my projects better than I do; you are right, Shipyard was called nostr it but everybody hated that name 😂😂
I have an old one in my notes. Maybe it wasn't you who made it... "Nostr It" sound familiar?
Note, though, that the only reason adding that to your muted words works is because this spam attack happens to use that domain for their profile pictures. If they change what domain they are using, the spam will be back. It's a temporary band-aid at best.
Also note that while this works on Amethyst, your muted words may not carry over to other clients. Amethyst encrypts the muted users and muted words when it adds them to your mute list, and not all clients support decrypting them, or muted words in general.
As far as "pay once" relays go, there's nostr.wine.
Kick ass answer.
#note1h8q…4xwu
Whaaa ? I thought hive talk was a voice over app ?!?
When China banned mining last time, over 50% of the global hash rate was located in China, and most of it turned off and moved elsewhere. That massive drop in hash rate resulted in a "fire sale" for Bitcoin, which dropped to $30k. There were also other contributing factors, such as Elon announcing that Tesla would no longer accept Bitcoin that occurred at the same time.
I haven't heard about any new ban on mining from China, but even if they did, it would not have nearly the same effect on hash rate, since most of the miners are no longer located in China. If there's been a ban, it hasn't seemed to affect current hash rate at all, so I also wouldn't expect it to cause much of a dip in price.
If you don't have Alby extension set up, you can go to the Settings page in Nostrudel, then the section for Lightning, and there will be a "Connect Wallet" option that will have NWC as one of the connection options.
https://relay.brightbolt.net/41f2b4f320e09b1646ea0d0da948270b4cc195120857f6d2c6b1bbefa6d88b2a.jpg
If you have Alby extension, Nostrudel will default to using that instead, and you can connect your wallet to your Alby extension via NWC.
no, it was always Shipyard :D
It has recently been added to @npub1z0l…8ldk Honey.
There was another one that I think @npub1l2v…ajft made before Shipyard, where you could schedule a post based on a block height, date and time, or other factors. Don't know if it is still up and running, though.
Haven is khatru under the hood, by the way.
Best approximations are available on https://stats.nostr.band/
Didn't see a breakdown for monthly active users specifically. Just daily and weekly, and at the top of the page you can choose to see numbers for either the last 2 months, or the last 6 months.
Primal premium expired so i’m on to the next client
what’s your favorite client?
Besides @nprofile…zg2n do we have any Nostr post scheduling tool?
#asknostr #nostrdevs
Yes, and the format and expected content within a given kind.
How can it be a "connection" if it is only one way?
Adding an npub to my kind 3 just means I'll see that npub's posts in my feed. We've not necessarily made any kind of mutual connection and may have no relationship to one another at all.
All that it means is that I am interested in seeing what that npub has to say.
If it worked by sending some kind of request to connect that had to be approved by the npub I was trying to connect with, then you might be on to something.
Interoperability is the #nostr context just means agreeing on the kinds you want to use.
Feel like rebranding "followers" to "connections" or something like that would be a healthy thing for the internet. "Followers" implied a kind of awkward hierarchical relationship, mostly meant for advertisers and personal brands.
bedtime for all the kids, I mean
like herding cats 😅
Exhausted. Bedtime.
This is my circus.
These are my monkeys.
Let's do this.
Regular payouts via Lightning? @nprofile…ckyu + DATUM.
Lottery chance at hitting a block on your own for whole block reward to yourself? DATUM on its own. No need for a pool to solo lottery mine.
Where is the best place to point a Bitaxe? No wrong answers.
#btcmining #asknostr
What is a good node that is easy to set up? I am a newbie #asknostr
Wow... Thanks for the info!
Here's hoping! Centralized platforms are enemies of freedom once again.
Shopify paused any 'new' payment gateway applications about 2 years ago and haven't yet opened up that process again. We're hoping they will soon.
Existing services like OpenNode and IBEX etc. are grandfathered in.
Phoenix is pretty nice. Been using it on the side for a couple years now. They also recently added a new kind of lightning address powered by bolt-12 invoices, but they warn that it might not work with all wallets to be able to send to it.
The major reasons I can't recommend it as a daily driver for newbies at present are 1. No way to connect it to Nostr apps for one-tap-zapping, 2. No way to reliably receive zaps to their new lightning address spec, 3. Even though they lanage your lightning channel for you, you have to know a thing or two about how liquidity works to avoid surprise on-chain fees when you run out of inbound.
And fees lower than muun I believe. Need to explore phoenix wallet more. Thanks for sharing!
Are you using one of the existing market/classifieds NIPs (NIP-15 & NIP-99) or doing something different entirely?
I’m adding store to spacestr https://www.spacestr.com/npub16sg6pkyux5kvyr5pckhkqymk2lnrsplu6zu4r54ans8h9df4s0msmkgy58
https://blossom.raybuni.com/00916040c2299cebbd310f989983fb6fb48456ff7485e7f5566476528b86f828.jpeg
I want to build Shopify for Bitcoin, build premium Bitcoin online stores.
This will give you a bit of context, I think:
#nevent1q…aulh
Wha?
Was there some attempt by Amethyst to get apptoved on Apple's iOS app store that I'm not aware of, and they were rejected for not meeting their security requirements?
As far as I am aware of, Amethyst was only ever made for Android. No iOS version was ever developed.
The reason probably had nothing to do with Apple's security requirements and everything to do with the fact that it's an entirely different OS architecture that requires a complete rebuild of the app, and not worth it when Apple's draconian rules didn't allow zapping to be available by default.
Heck, we still don't have an Android version of Damus, and that has nothing to do with Google's "security requirements" either. It's just a completely different OS to try and build for.
I don’t trust Amethyst. I have only used @nprofile…u4zk @nprofile…9jls and @nprofile…xss0
I don’t trust any “only android” services that can’t meet apple security requirements.
Hopefully with time clients get better, I don’t mind monthly fees if the app is good.
#asknostr #nostr #clients
What's the best place that can catch me up on the whole bitcoins, bits, sats sitch that's up right now?! I did an oracle reading the other day and got interesting insights. I wanna get more informed before I share.
#asknostr #grownostr
Yes, Primal's caching server aggregates my notes from the relays I have set up to write to. However, it does not allow me to read directly from the relays I want to read from. I can only read from Primal's caching server, which pulls in notes of other users from the relays they wrote to.
Therefore, any web-of-trust filtering on my read relays, or payment requirements for someone to post to them, are to no avail. Their note will be aggregated by Primal's caching server from whatever relay they post to, regardless of the ones I want to read from, and displayed to me.
Indeed, you can't even set which relays are read vs write in Primal, because they don't let you read from relays. They only let you write to them and read from the caching server which aggregates notes from all known relays.
For something like that to work, you would need to be able to select a relay to read from that won't accept posts mentioning you without the user paying first.
You don't have that option with Primal, because you can't configure which relays Primal reads from. It only reads from their caching server.
Mileage seems to vary. I don't have any bot spam on Primal at all, meanwhile others in the AskNostr feed clearly have a ton on Primal. I don't really use Damus, so I can't speak to that, but others are saying they have no spam at all on Damus:
#nevent1q…5jul
For most clients, it's going to depend heavily on what relays you are reading from, not what client you are using.
Indeed. There is one major downside to it, though.
One of my favorite clients is Coracle, and the reason is because it has built in WoT filtering. However, the scoring for this feature is based on how many people you follow who also have followed a particular npub (adds to that npub's score), vs the number of people you follow who have muted that npub (subtracts from their score). If your mute list is encrypted, Coracle cannot use it for this purpose.
A middle ground that might be workable would be to not encrypt mute lists, but relays won't display other users' mute lists to just anyone. Only those within the author's web-of-trust can access them, enforced by AUTH.
Just an idea, and probably too complicated to actually implement. 😂
Yep. Again, it's a nice feature to have them encrypted, since you don't necessarily want to advertise what words you are muting to anyone who reads your mute list.
If you ask me, mute lists should be encrypted by default.
People spending all their time and energy to earn something others created for free.
I'd like to see a hybrid relay. WoT can post without PoW, and anyone else needs to either pay to post or include PoW.
If aliens visited tomorrow and started observing us, what's the weirdest thing they'd see?
#asknostr
So, Amethyst appears to be putting this information into the user's standard mute list (kind 10000). However, it is also encrypting the words you are muting, so this will only carry over to other clients if 1. they support muting words, AND 2. they support decrypting your mute list.
I have noticed this being an issue when muting npubs, too. Amethyst encrypts the npubs you mute in that client. Very nice feature, since you don't necessarily want someone to know that you have muted them. However, not all clients support this, so the npub won't be muted on those clients unless you re-add them to the list without encryption.
Indeed. Plastic is on the way out, and good riddance.
All teens I see here in Brazil pay with mobile.
Instead of WoT relays, can't we just make PoW notes a thing again? This would slow down bots a lot and cost them way more to spam... #askNostr
So you're saying that if Lightning is going to work, the receiver needs to be the one who pays the fee, everyone has to be locked into KYC custodians so they can get cheap credit, and we need plastic cards filling our wallets, instead of just using an app on our phone?
Sorry. Hard pass.
Lightning is a protocol, not a company. Lightning can't "offer" anything.
There is nothing stopping a custodial lightning wallet provider from offering 30 days of credit, but then I guarantee they would have KYC so they can collect if you don't pay it back.
There's also a reason credit card companies are able to offer 2% cash back. It's because they are charging each merchant who accepts your card 4%+ in transaction fees, and just passing a portion of that on to you. Lightning doesn't have anywhere near that kind of ridiculous fee rate, and what little fee is charged is paid by the sender, not the receiver, as it should be.
Just someone spinning up reply bots, similar to replyguy from last year, but this time they parrot your note with the words scrambled.
Annoying, but harmless and easy to filter by using decent relays.
How very odd... Why such a disparity of experience when everyone on Primal is reading from the same caching server? 🤔
I’m on Primal. Haven’t seen any spam for months.
Yeah, problem is, you don't get to choose which relays you read from in Primal. That's why I don't usually use it, and rather use a client like Amethyst, Coracle, Nostur, or Damus, where I CAN choose the relays I read from.
I am just perplexed because I expected to see a torrent of reply spam when I decided to check out the situation on Primal, and I am seeing none. I know plenty of other users on Primal ARE seeing it, so I have no idea why I am not, since all Primal users effectively read from the same relay; namely Primal's caching server.
Well, Damus is a client that lets you pick which relays you read from. Major benefit of using a full fledged Nostr client during spam attacks.
It's a mystery to me why I am not seeing spam on Primal, though, since it doesn't have that benefit.
Now you have me intrigued. How is the web-of-trust built such that it excludes bots people are following automatically? It's obviously not a simple "all follows + their follows" like a standard web-of-trust.
Interesting... I popped over to #Primal to see how bad the spam reply nonsense is here and I have ZERO reply spam in my notifications.
I am seeing questions from Primal users about how to get rid of it, so I know it must be an issue over here, and I know that I am getting reply spam on my notes, because I am seeing it on Jumble or on Coracle when I have my WoT filter set to 0.
So what gives? Primal users are all reading from the same caching server, rather than directly from their selected relays, so why are other users seeing reply spam on Primal but I'm not?
Have you tried out Nostur yet? I think it has one of the best looking UIs of all Nostr clients, while also giving the user a ton of features, including the ability to set which relays you read from.
While this works for the current attack, just bear in mind that it's not really a solution to the issue. They could just start hosting their profile pictures somewhere else.
I feel like PoW is an underutilized spam prevention technique, since most clients don't support it, and most relays don't require it.
Now that pagerank is a thing, I think public relays could do a lot to minimize spam by simply requiring PoW for anyone below a pagerank threshold, but only if more clients supported adding PoW to notes.
Maybe it's a chicken and egg thing... Relay operators are reticent to add PoW requirements since so few clients support it, and client devs are reticent to add the option to include PoW since no relays are requiring it.
Really would not be surprised if that was accurate.
It's gotta be above half for newer users, I'm thinking maybe 60%.
You can still have Damus as a write relay, just 86 it from your read relays.
Write to whatever you want, but definitely purge public relays from your read/public inbox list.
Removed Primal don't really want to remove Damus but might have to do that as well.
Yeah, I gotta do a relay cull.
No idea. It's probably substantial, though.
The apps are gorgeous. It's easy to get started. Built in wallet. You barely have to touch the settings if you don't want to or don't understand what they do.
I definitely see the attraction.
The majority of those in my local meetup group who are on Nostr had only used Primal before I started showingbthem other options and why they might be interested in checking them out.
Disconnected from the two non-WoT or Haven relays I was using for discovery. Spam gone.
Ergo, web of trust is the way.
What % of nostr usage is via Primal these days do you think?
The AskNostr feed barely has any questions today ouside of, "What's with this reply bot spam?" and "How do I get rid of these reply bots?"
Read only from WoT relays and paid relays, my friends, and they'll all be gone.
Unless you use Primal, where you don't have a choice where to read from...
Probably just meant to annoy us into making improvements to our spam prevention measures.
There are probably a lot of solutions that can work for squashing this particular wave of reply spam. However, they won't necessarily work for the next one, and there will always be another new wave of spam.
The best option is to level up your relays. If you are only reading from relays that keep spam out, you'll never see spam.
Web-of-trust and paid relays are the best ones for reading from. Best of all, you usually don't need to pay to just read from a paid relay.
A couple good paid relays are nostr.wine and nostr.land.
There's a lot of good web-of-trust relays out there. This GitHub page has several listed at the top, and instructions on how to set up your own, if you're adventurous:
https://github.com/bitvora/wot-relay
Just remember to also get rid of all public relays from your list of read relays. You can still write to them if you like, but don't read from them. That's where all the spam is.
Dynamically based on which relays are most popular at the time, right? Pretty nice feature! 🫡
nostr.land will broadcast to other relays so you’re fine
Scramble bot is really being annoying.
I ristricted my read/write to paid relays. I wonder if anyone can read my notes now lol
No, Phoenix maintains the channel for users as an LSP. Splicing in and out from that channel also allows for on-chain activity without users needing to think about what sats they have in L1 or L2. The downside is that they charge some small fees for the convenience they offer, but I think they're reasonable.
Oh! Bed time now.
GM and GN @npub1der…xzpc
This is great! Now I want to go put some caches of my own out in the wild!
So, this is definitely something Nostr devs have considered at length. For one such discussion, refer here: https://github.com/nostr-protocol/nips/issues/103
There's NIP-26 for key delegation, which was merged, but is unrecommended: https://github.com/nostr-protocol/nips/blob/master/26.md
And here's another proposal with a discussion: https://github.com/nostr-protocol/nips/issues/116
There are significant challenges to implementing key derivation and rotation, but if you think you can add to the discussion and even suggest a possible solution, by all means head on over to GitHub and chime in!
Aaaand there's the ad hominem... Well done.
I am sorry, I thought I had. Did my response not acknowledge that buying a Start9 is not needed, and that there are other options, it's just that each of those options come with their own tradeoffs as well?
Well, it's either that or you have to get some other general piece of hardware that requires even more know-how to get up and running, or you have to use one of the node-on-a-phone options, like Zeus or Phoenix, which have their own tradeoffs.
"Hi! I'm new to Nostr and want to try out zapping, what wallet should I use?"
"Whatever you do, stay away from custodians because they can rug you. Go get yourself a Start9 for $900, install Bitcoin Core, LND, and Alby Hub. Then you'll need to get about 1m sats for your first channel. You might be able to get away with 100k+, but it's really best if you go with at least 1m. Oh, yeah, that's over $1k right now. Don't worry though, you still own that money so it's not costing you anything more than the on-chain fee to open the channel. Now you have to decide who you're going to open it with. Go research well connected nodes that allow people to open channels with them. What do you mean you can't receive? Oh! You need to have inbound liquidity. You'll have to zap some people so that there is liquidity on the other side of your channel before you can receive any zaps. "
Yeah... Not feasible. Custodians are a great first-touch, and people can upgrade their sovereignty as they go and as they learn and get interested in doing so.
Hmmm, that's less likely. Maybe you have a relay they have write access to in your public inbox or general relays?
I run my own. Someone among my follows is following them.
What tardbots? I don't see any tardbots. 😉
WoT relays are your friend when Nostr has an influx of reply spam.
Alternatively, use whatever relays you like and use Coracle with your WoT filter set to a minimum of 1.
No more tardbots.
Right? Who would condone him for that? Condemning him for that alone would also be dumb, but condoning him for it makes no sense at all.
While I would have preferred he stuck to Bitcoin only, I can understand having fascination and curiosity when you've never had the chance to touch the stove and learn better.
So, there’s a swarm of tardbots that reply with dyslexic versions of the original note. Cool, cool.
I've seen some people on nostr condone him for saying that, which is completely fucking retarded, but whatever.
Will Bitcoin Puritans cancel Ross for daring to say that altcoins are fascinating experiments and a broader aspect of decentralization? 🤔
#nevent1q…srdx
Thank you, sir! I'll let you know if I come across any more in my travels on asknostr.site.
Ok frens, for the sake of those of us who run Web-of-Trust(WoT) relays, can we establish this as a best practice?
Follows (kind 3) should be for npubs you believe to be real people whose posts you enjoy seeing in your feed.
Other follow lists (kind 30000) can be used for any other reason you like, including following bots.
Following bots in your kind 3 requires WoT relay operators to choose one of the following paths:
1. Unfollow you so you are no longer part of their WoT and the bots you follow will no longer be included on their relay. However, that also excludes all the other npubs you follow, too.
2. Manually blacklist the bots from the relay (available on some WoT implementations and not others).
3. Manually exclude you from the WoT while keeping you as a follower (available on some WoT implementations and not others). However, this has the same side-effect as option 1.
4. Live with the bots' posts showing up in the feed all the time.
Excuse me while I go investigate who is following all the bots...
Yes, for newcomers (or others who have been around a while and always wondered but never spoke up) to find the answer to a common question, and for those who spend time helping answer questions to easily be able to copy/paste or provide a link to the answer each time it comes up again, instead of typing it out all over again.
See! An FAQ would definitely be helpful!
In any case, follower counts are impossible to get accurate, because of the way they are tracked.
Presenting a count of how many people YOU follow is easy. It's all saved in your follow list, which is updated and signed by your private key every time you follow or unfollow an npub. So long as that new version is spread around well enough, clients will consistently present the same number.
It's quite a different story when trying to count how many people follow you, though. Think about how a Nostr client would be able to get that information. For centralized social media, it's easy. It's all stored in one server. But on Nostr, different users could be storing their follow lists on any one or more of thousands of relays. Your client, therefore, has to try and reach out to ALL of the relays it can, ask for any follow lists that have your npub listed, weed out the duplicates, and tally them up. What if it doesn't reach out to every relay that has a follow list on it with your npub included? That's highly likely. What if not all of the relays respond? That's highly likely. What if a portion of the relays are offline? That's almost a certainty. What if the request from the client times out before all of the relays have responded? Yep, that is also frequently the case.
So, why does Primal's follower count seem to show so many more followers, and also seems to stay a more consistent number (other than the follow/unfollow bots causing fluctuations)? Because Primal apps don't read from all the relays to calculate your follower count. Instead, their caching server pulls in follower lists (and most other notes, too) from as many relays as they are aware of, so that they all live in one place and can be counted easily. Most Nostr clients read from relays directly, but Primal apps do not, and that comes with some tradeoffs. You get a more consistent and probably more accurate follower count, but Primal's caching server becomes a central point of failure and a central point of censorship for anyone using their apps.
@npub132n…8cn4 here's an idea for asknostr.site: There should be a FAQ page with common Nostr questions that are asked over and over again and their answers. Things like, "Why do different clients show a different follower count?" or "How come I lost all my follows?"
It would be a place users of the site could go first to see if their question has already been answered, and it would be a convenient resource for providing answers to users asking questions from other clients.
It's something I have been thinking about compiling for a while now. If you want to add it, I would be happy to work on it.
Can confirm. As long as their relay is up, it just works.
#Albyhub has been the most reliable nwc setup so far. I've tried coinos and primal but kept having issues with payment after some time. But with albyhub it just works all the time. Impressive for a self custodial solution.
Exactly this! Nostr is ridiculously easy to onboard to and start participating. Everything that hasn't been made incredibly user-friendly already is entirely optional.
The GitHub page for the relay implementation has several listed you can try out:
https://github.com/bitvora/wot-relay
Ifbyou're adventurous, you can also get instructions there to run your own.
To be fair, the @nprofile…tdq0 has much more than just Nostr and Bircoin apps.
F-Droid
(FOSS apps)
Aurora Store
(anonymous mirror of Google Play Store)
Zap.Store
(Nostr and bitcoin apps)
#note1yzw…v0x9
So give us some names. We need more trusted relays.
You won't see reply spam if you use WoT relays (only)
I was trying to explain the difference between Nostr and “decentralized” crypto social networks to someone the other day and I boiled it down to this:
Everything else assumes you already have a wallet like MetaMask and it forces you to connect it before you can even sign up, or you have to use an email address or even attach a centralized profile from another service to verify your identity.
On Nostr, by comparison, you just create a keypair. That’s it.
Sure, you’ll probably get pestered by everyone to add a Lightning address to your profile, but it’s entirely up to you if you want to be paid in the world’s best money for your stupid shitposts. 😆
Your ignorance far outweighs your knowledge.
Seems we have a new spam attack going on. Similar to replyguy, but mixing up the words of the post they are replying to.
Any clients with web-of-trust or pagerank filtering shouldn't be affected much, if at all.
@npub132n…8cn4, I thought asknostr.site was using pagerank-based filtering. Maybe that's only for the original question itself, not for the replies? The bots are in full force on your client, unfortunately.
No lost funds, just no access to any funds received during that 24 period until Coinos could verify the deposits. Funds received prior to or after that period were available for use.
Your options are pretty well Damus, Nostur, and Primal. Of those, I only ever tried Damus back when I had an iPad, and it was decent. Nostur didn't exist back then, though. I would give Nostur a shot, as it is probably the best blend of an attractive UI and a ton of functionality. Let me know how it looks on iPad, as I have only ever used it on a phone.
More details, please.
Are you wanting notes that are stored on relays encrypted so only you can see them, like a relay-hosted version of Obsidian or Joplin?
Or are you wanting encrypted direct messaging, like Signal or SimpleX?
We have encrypted direct messaging in 0xChat and Keychat, and many flagship clients, too. It's a mess right now, because they aren't using the same DM spec, though. You'll receive some messages in one app, but not others. 0xChat seems to be the best about showing all of them.
We don't yet have the relay-hosted version of Obsidian or Joplin with encrypted notes only you can read.
Depends on the use-case.
Do they need to be able to use the wallet with Nostr, or at least have the option to do so without switching wallets? You'll want to point them toward something with Nostr Wallet Connect as an option.
Custodial: Coinos or Minibits
Self-Custody: Alby Hub
Honestly, though. Self-custody lightning is NOT for the beginner. It's for someone who understands the fundamentals of how lightning works, and who is willing to take responsibility for managing their liquidity, understanding that it will be costly and frustrating when they mess it up.
Sure, but a limited usefulness. From that screenshot I can tell that is likely the legit @npub1jlr…ynqn due to the WoT ring next to his handle. Impostors don't build up WoT scores like that. And I can tell that without having to look up his profile, check his NIP-05 or follower count, or anything. It's just immediately apparent at a glance.
Here's a post on Nostrudel by contrast:
https://relay.brightbolt.net/5d7c317cee97840724568f93d69c0808a6c3598c558adfbce2b5152860dfe116.jpg
Can you tell, without going to his profile, whether this post is the legit @npub1jlr…ynqn or a fake?
This colored border around his profile picture means exactly nothing to me unless I happen to already know what color it SHOULD be.
The above screenshot is from the impostor, by the way. @npub1jlr…ynqn's correct color is lime green on Nostrudel. But the point is, I didn't just happen to know that. I had to look him up by his npub that I already knew (from Coracle) to learn that lime green is the color I should be looking for.
Yes, I have seen that Nostrudel has it. And yes, it can help to quickly identify that you are dealing with a different npub, but only if you already know the correct one and remember what color they should have. Which means, not very useful at all...
Had no idea what Skool was. Sounds like it is attracting people who want to make money by selling their own courses on the platform, but it's mostly just courses on how to make money selling courses on Skool.
This naturally incentivizes every user to promote it to all their friends and family, in the hope of boosting their earnings. However, I don't think it will have staying power.
Trying to understand how this would help.
So, it converts an npub into a series of colors instead, because npubs are too long. Great. How does that help someone know whether color series A or color series B is the impostor? They would need to already know the correct color series ahead of time.
I think Coracle has the right approach. Just need more clients to have similar indicators, marticularly on their search results.
It's to the point that I won't search for users on any other client but Coracle. It's the only one I know I can trust to have the legit profile as the top result, with a clear indication of why I should trust that they are not an impostor.
I find it quite ironic that it would have been obvious he was an impostor if they had been using Coracle.
PSA @npub17yz…a6q6 @npub1824…tzv8 @npub1ehh…zjqv @npub1mt8…m7cz @npub1vxl…gnvx @npub17vc…6mq9 @npub1nn5…zmh4 @npub1pc5…dmza:
Please unfollow and mute the impersonator account @nprofile…xfp4
I generally use Habla.news for publishing my long form.
Your end result should be mostly the same regardless of which one you use.
Long-form notes use markdown for formatting, so you should brush up on proper markdown syntax for common elements like images, headings, bulleted lists, hyperlinks, etc.
The compoaition tools for each long-form client may have different elements available for you as shortcuts, but if you know how to write markdown without those helps, then it really makes no difference which one you use.
How your article will look to the reader will depend on where they are reading it from. Even if you wrote it on Habla, they might read it on YakiHonne, or even Amethyst, and things might render a bit differently. Since Nostr is an open protocol, writing the note on one client doesn't mean the note is locked to that client. It will be visible on any client that can display that kind of note.
What Nostr platform does the best long form content? I want to polish up some essays to present here, but a bit separate from my standard notes so that my notes are more short commentary like tweets, the long form essays are separate from my notes feed. Let me know what you think! Yakihonne? Habla? Flycat? Does it matter? I don't fully understand the pros and cons of using one vs the other
#asknostr
I am onboarding new user to #Bitcoin.
What wallet would you recommend for a newbie? I need frictionless experience with LN.
I was thinking of WoS, but it's a custodial solution and I am really hesitating to offer it.
I don't want to move him on KYC right away, like Strike.
Any ideas?
#asknostr
I can see this being useful for NIP-05s that are actually associated with a particular community. I could also see this being useful if an npub could be associated with multiple communities by having more than one NIP-05.
Less useful for more generic NIP-05s that are just "pay here to get verified," though, IMO.
Still, looking forward to checking it out!
Now that I’ve announced this feature to #NosVegas attendees, I’m excited to announce it more publicly on Nostr!
I’ve recently opened a PR to add NIP-05 domain feeds to Damus iOS. You’ll be able to tap on anyone’s Nostr NIP-05 address on their profile to bring up a feed of all profiles within your trusted network (your follows and their follows) that have an address associated with that domain. The purpose is to help you build trust and discover communities by domain.
What does that really mean?
For organizations that provide Nostr NIP-05 addresses on their domain (such as damus.io and block.xyz) to only employees and self-owned accounts, you’ll be able to see a refined feed of profiles and content from your trusted network that belong to those organizations.
For organizations that provide Nostr NIP-05 addresses to customers on their domain (such as nostrplebs.com and primal.net), you’ll be able to see a refined feed of profiles and content from your trusted network for customers of those organizations.
I’m excited for you all to try it once it becomes available. In the meantime, I’ve included a screen recording of it in action below. Let me know if you have any feedback! As always, thanks for your support. ✌🏼
https://v.nostr.build/YiXDKASFwv202mnP.mp4
Yeah... Carrying in a proper holster is important.
That's a fair point. Some folks are more on top of notes when they are mentioned than others, though. 😂
I generally lean the same way when it comes to my feed, though. I make heavy use of my web-of-trust relay.
Interesting idea. Might be a bear to implement, though, and it would have to be implemented by the majority of clients in order to be useful. Otherwise, users might pay to have their note put into @npub1qny…95gx's feed, is a feature that a few clients support, but he doesn't use those clients, so he never sees it and they wasted their sats.
It does kind of remind me of what @npub1pmh…uksr and @npub1yz8…pxp7 are working on with @npub17vs…66ne, though. Haven't heard any developments on that front in a little while, though.
You absolutely can. In fact, you can set @npub1h2q…w8ch to automatically send sats to any lightning address when your balance hits a threshold you decide.
Yep. 100% agree!
I personally receive my @npub1qtv…7dze payouts to my own CLN node. But then, that’s also not where I hodl my sats, either. I build up enough for a decent UTXO and then swap it out to on-chain and into cold storage.
In any client that supports Blossom, put https://blossom.band/ as the media server. In any client that still only supports NIP-96, put https://nostr.build/
In the ones you mentioned, Nostur and Primal both support Blossom. Couldn't find any way to change what media server is used in Damus, but it uploads to nostr.buld, and probably using NIP-96.
Everything you upload to blossom.band will show up in your nostr.build regardless of which client you use to do it. They are the same thing.
I meant to tag @npub15yp…mpcx on that second one, but I guess I still had Coinos' npub in my clipboard...
Alas, the folks at Phoenix Wallet have not deigned to grace us with their presence on Nostr.
And you are correct, Phoenix does not work for receiving lightning payouts from OCEAN, because they don't support the description field properly.
Your option for self-custody payouts is running your own CLN node, and your custodial option is @npub1h2q…w8ch.
Our fellow nostrich @npub1h2q…w8ch has a guide for the latter:
#naddr1qv…z5ck
I don't use it, but definitely don't hodl with custodianfn?mmmm-
My friend, what do you think their auto-withdrawal feature is for?
No, that's totally fair. He was locked up for over a decade. He never had the chance to learn what scams they all are by touching the stove like most of us have. I'm happy to not give him too hard a time about it.
Still would have preferred he wasn't promoting shitcoining in the last speech to end the so-called Bitcoin conference, though.
You abbreviated for some reason. I believe he said "build shitcoins." As many of them as possible, so we can see what works and what doesn't.
The bulk of @npub1pzz…dsr8 's speech was fantastic!
Really could have done without all the shitcoining in it, though.
I guess he knew his audience?
The short answer? People do. As soon as one person proposes a change, 10 other people will have proposals that are variations on it.
I think they handled the situation about as well as can be expected. They were transparent about their progress in restoring wallets as fast as they could with the data they had available to them. Sounded like it was a pretty manual process.
That said, they're a custodian. Keep as small a balance there as you can get away with.
If you have what it takes to switch to self-custody Lightning, then do so. If you don't, then consider taking a bit of time to learn.
As far as custodians go, I wouldn't consider them more or less trustworthy than any other. They're probably the most ideal custodian for using with Nostr due to their feature set and ease of setup, but that doesn't make them any less likely to rug you, intentionally or not.
Fixed money and more productive work.
Is this just a LNURLw, or is it something proprietary so that it can only be claimed using Primal wallet?
Well, there's always incentive to vote yourself free money. Problem is that you can't get everyone else to also go along with you.
Say you propose a change to the code that gives every node 1 Bitcoin, irrespective of whether they mine. Well, you as a node runner might be incentivized to run that new code, but that doesn't matter much if you're the only one running it. You still need to 1. Make everyone else who runs a node is aware of it, and 2. Convince them that it is in their best interest to also run it.
Might think that's easy, right? Won't all those node runners also want to receive a free Bitcoin without doing any work? Sure, they likely would, if they don't know any better. However, there's plenty of node runners who are fully aware of what would happen if they did so, because even though they would have a free "Bitcoin," it wouldn't really be Bitcoin anymore. It undermines the whole reason why Bitcoin is valuable in the first place. They also know that it would just create a fork that people would sell, expecting that it will lose value over time.
Even those who like the idea will want to put their own spin on it. Some will wonder why stop at 1 Bitcoin per node and will want to receive 2 or 3 instead. Others will rightly note that it's too easy to spin up a bunch of nodes and get more Bitcoin for free, and they will want to limit it to one node per person by requiring KYC to ensure no one can get more than 1 free Bitcoin. Others will be adamantly against KYC, and they will want to regulate who gets the free Bitcoin by some other means that better preserves privacy, like requiring a certain amount of proof of work that can be done by an average PC's CPU, but which would be prohibitive to spin up a lot of them. Someone else will note that if each node is getting a full Bitcoin, it will be more than worth the money to buy as many PCs as you can, each able to generate the required proof of work for the free Bitcoin, so they will suggest limiting it to 1 Bitcoin per node and per IP address... So on and so forth, with each camp gaining supporters and eventually getting fed up with one another and spinning up their own idea that has a small minority support.
Meanwhile, the actual Bitcoin keeps chugging along. Tick tock, next block.
It's exceptionally difficult to get people to agree on anything that is a change to the way Bitcoin works. Even in the least controversial of circumstances, there are competing ideas about how to do things. As such, making no change at all always has the advantage over any proposed change. It is the default position of what will occur if not everyone agrees about exactly what the change should be, including every minute detail about how it will work.
"If you get a loan against your Bitcoin, you don't have to sell it, and you avoid capital gains."
Yeah... Until I'm forced to sell it due to margin-call. No thanks.
Have a link for the Discord? The one @npub18pu…a699 posted on ChaChi has expired and the one on the HiveTalk site doesn't seem to work. This is what I get when following the link on https://honey.hivetalk.org/dashboard/help :
https://relay.brightbolt.net/b9cc8a75e8e483bf48d5e535abec8189679a158c0953217bb4717177ba87b2fa.jpg
Give us time, I'm sure @npub18pu…a699 will have a solution :P
Can do. I'll pop over to the Discord.
Our of curiosity, though. Why use Discord instead of something built on Nostr?
There is a massive difference between wanting the price to go down so you can buy more vs wanting the entire basis of the value to be undermined so you can get some.
Your node also isn't meaningful on the network if you don't own Bitcoin and use your node for transacting. Only nodes that are actually being used to conduct transactions and verify the validity of the Bitcoin received by those relying on that node matter. A node that is just sitting there keeping a copy of the chain, but not being used by anyone, effectively has no vote. Whether it wants to increase the supply doesn't matter.
Let's entertain the idea that a number of nodes and miners want to increase the supply of Bitcoin, so they start running an alternative version of the code that allows more coins to be mined and distributed to the miners and node runners. What happens then?
Well, you end up with a chain split. All the nodes that want to inflate the supply will accept a block mined with the increased reward, while all of the nodes that don't want the supply increased will reject it. So there will be two versions of Bitcoin at that point, and anyone who owns Bitcoin on the original version will own an equal amount on the new version (we'll call it Inflato-coin), where the supply is able to inflate beyond 21 million coins.
Anyone who knows how scarcity works to ensure a money retains its value will do what any sane person person would. They will sell the version they expect to go down in value, namely Inflato-coin, and buy more of the version they expect will retain its value. As you might expect, this will cause Inflato-coin to rapidly fall in price compared to Bitcoin, which will have a cascading effect of more and more holders selling it, driving the price down even more. There will, of course, be some idiots who think this is the buying opportunity of a lifetime, and that they will make crazy gainz when the market rebounds and Inflato-coin just gets back up to its previous ATH, but they will just be the exit liquidity for those who know better. They'll just end up as the bag-holders.
There is no way around this, because consensus is messy. You never have a situation where literally everyone agrees what should be done, and that is doubly the case when it comes to mucking around with the Bitcoin's supply cap. Yes, there might be a sizeable amount of node runners who want to "vote" themselves more coins by destroying the entire value-proposition of what they hold, but there will also be plenty of node runners who would never do so. That being the case, a chain split would be inevitable and it would become clear very quickly which version is able to retain its value, and people will choose to keep that version and sell the other.
Depends on who it is, right?
Let's say it's some random npub that hardly anyone knows about and who hasn't built up a reputation. A zap is probably going to be considered more valuable than a repost in that case.
On the other hand, if it's someone who has built up a following and a reputation that is well respected, then their repost will likely be more valuable than their zap. It could also cost them more than their zap would, if the person whose content they are reposting damages their reputation.
No, I agree that there can be reputational cost. But how much it costs your reputation is even more subjective, as it depends on what the content is that you are reposting, and whether it is in alignment with the reputation you have built up, therefore reinforcing it, or at odds with and therefore hurting it, or somewhere in-between. None of which can be easily quantified.
Someone of character may not be willing to repost content that could damage their reputation, regardless of how much they are offered to do so, while they will gladly repost content that reinforces their reputation for free.
There is no incentive to undermine the very feature that gives Bitcoin its value. The only way it will reach million dollar heights is if the fixed supply remains reliably enforced, and the only way it will retain that value or higher will be if it retains its fixed supply.
Every increase in USD denominated price is a challenge to the market, daring it to prove that more supply can't be made available to meet the current demand. If the supply is no longer immutably fixed, then the price will likewise plummet. So there is no incentive for either mining pools or node runners (who are relying on Bitcoin maintaining its value) to inflate the supply.
Not really. Most block formation and coinbase is not controlled by the miners at all, but by the mining pools.
At any rate. When a block is mined, it is broadcast out to the nodes on the network for them to validate in retain in their copy of the chain. If the mining pools included a transaction that is outside of the consensus rules the nodes are enforcing, then the nodes will reject that block. They simply will refuse to add it to their copy of the chain. One of the consensus rules they enforce is the amount of new Bitcoin included in the coinbase. If miners, via their mining pools, try to award themselves more than what the nodes are enforcing, the nodes simply won't accept that block.
So long as the nodes won't accept blocks with an inflated supply, then mining pools won't run code that tries to award miners more Bitcoin, because they don't get paid at all if the nodes reject their blocks. They only get paid for blocks the nodes are willing to accept as valid.
Can't go wrong with this list of articles compiled by Anilsaidso, which @npub1h8n…rpev has read the vast majority of on Bitcoin Audible. I reposted Anil's list as a Nostr long-form, with all of the available audio linked, here:
#naddr1qq…uwmu
If your client can't display the above Nostr URI, here's a regular URL: https://dikaios1517.npub.pro/post/1733001418581/
Anyone can change the code at any time. The problem is convincing anyone else to run it. Miners don't control Bitcoin. If they want to inflate the supply, the nodes will reject their blocks.
Preferred place to send such requests? DM? ChaChi? Discord? GitHub? Just tag you in a Kind 1, "Hey Karrot! Pls add ___ to HiveTalk"?
All value is subjective. The answer is, whatever someone is willing to pay.
And since when are reposts costly? There is no scarcity for reposts. They may be costly reputationally, if you are reposting content others wouldn't want to see. Outside of that, though, it costs nothing to repost except a couple seconds of your time.
Since Bitcoin is perfectly scarce, and reposts are not, it follows that the value of reposts would trend toward 0.
Think about how a Nostr client would even begin to calculate that number.
Calculating how many people you follow is easy. It lives in a single note (kind 3, specifically) that gets replaced each time you follow or unfollow an npub. All a Nostr client has to do is find that note from your write relays and tally up the number of npubs you have listed on it. Done.
Where would the Nostr client look to find out how many people are following you? There's no single note holding that information, and there can't be, since notes require the signature of the author on Nostr. You can't be made to sign to update a note when some other user follows or unfollows you, nor can there be a note that just anyone can sign when they follow you so it's all tracked in one place. Instead, they do the same thing you do when you follow someone: They add your npub to their kind 3 follow list.
In order to display a follower count to you, your Nostr client has to try to find the follow lists created by any Nostr user who may have followed you. It has to do this by checking every single relay that any individual Nostr user may have written their kind 3 to. What if your client doesn't check all of the relays? Highly likely to happen. What if some relays don't respond or are offline? Also highly likely to happen. Your Nostr client will only receive a partial count of how many people are following you. In fact, it's pretty well guaranteed that it will only ever get a partial count, and that the count will be different every time.
The only way to have a consistent number every time would be if there was a server where all follow lists of all Nostr users was stored, and your client only had to reach out to that single server to find them. But then, that would be a centralized point of failure, wouldn't it? If Nostr is to remain decentralized, then follower counts will always be inaccurate approximations based on which relays your client reaches out to, and how many of them respond.
Wow! That's quite the upgrade!
Could this replace Riverside for podcasters?
I like the calendar and note scheduling integration.
Lists would be used for having a set group of people you invite to a room, right? Would it be possible to support encrypted lists? Wouldn't necessarily want to dox who is being invited, especially for private rooms.
The world is not ready for that content
Love to see HiveTalk keep improving!
What's the short-n-sweet of the differences between vanilla and honey?
My lightning address is dikaios1517@getalby.com, and nope, that does not work for getting an invoice, either after updating it to "https://getalby.com/lnurlp/dikaios1517/callback?amount=1000"
A lot of these things I'm not fixing on purpose. With the work I'm doing right now, the foundation will be much more solid and lots of these annoying issues will go away (or be more clear/actionable)
Yeah, I have received that pair of errors before, as well.
Thanks for the response!
I was unaware that Shopify was blocking alternative payment apps. How did OpenNode and Ibex Pay get around that, I wonder?
Or did you mean the Apple app store? Because I was not asking about that.
Should have added a sensitive content warning, huh? 🤣
Was a meme that started last cycle. Not sure who started it, but #LaserRaysTill100k caught on.
Of courrse, we didn't see $100k last cycle, so most kept their laser eyes through the bear of 2022 all the way till $100k last December.
A fair amount removed them after that, but some of us have grown attached. Now it's #LaserEyesTillFiatDies
At the recommendation of @nprofile…u0w6, I tried out shaving with @nprofile…75w5 soap. Specifically the pine tar scent.
No, not my face. My head.
https://relay.brightbolt.net/97a212e114a5fe542d3a73d436dfcf26e81991915495b25904eaf2da34cba39e.jpg https://relay.brightbolt.net/c8171caa642d49cd7720f9d7bb1822bed528cf233213d5e0f193901684e5f886.jpg
Lathers up really nice and was a great shaving experience! Highly recommend!
Good question. The only part of the notification that may not be easily understood is the "Hash Mismatch" portion. The rest is plain.
I don't think the problem is primarily a lack of understanding the meaning of the warning. I think the issue is that users are assuming the Zapstore is wrong in presenting the warning at all. That the file certainly isn't malicious, and there must be a bug in the Zapstore.
It's a sort of normalcy bias. Apps generally install fine. They've never experienced installing an app that was actually not what the dev released, but was a malicious app put in its place. So they assume it couldn't actually be what has occurred.
What's more, they're probably correct that it isn't a malicious app. It's probably just that the dev made a change after signing and didn't update the signature on the Zapstore. However, the correct course of action is not to assume that's the case and install the app anyway directly from GitHub... The correct thing to do is reach out to the dev and alert them to the fact that there is a hash mismatch, so the dev can diagnose why.
Perhaps the alert should suggest this course of action.
Can someone please explain to me why laser eyes? #asknostr
How might @npub10r8…t2p8 Zapstore re-word the warning / unhappy path notification phrase below to make it more normie friendly?
#asknostr
#note190t…cm9c
We usually just want things to work, but sometimes when they don't, they are actually working perfectly fine, just not in the way we expected.
#nevent1q…tpy3
PSA:
If you get an error: "Possibly a malicious file. Aborting installation" it's because it's true. The hash of the file in the nostr event does not match the hash of the downloaded asset.
Two possible reasons:
- The developer modified the release after publishing the nostr event to the Zapstore relay
- There is a server compromise or a man-in-the-middle attack
This is Zapstore protecting you, not trying to annoy you.
In the case of APKs indexed by Zapstore (from Github, for example) this will be mitigated with the new zapstore-cli indexer going live in a few weeks.
If the app was signed by a developer, you need to contact the developer.
I am going to improve the messaging, and add a "reckless mode" for those who want to install or upgrade despite the mismatch.
Came here to say the same thing.
Get enough people in one place and there will always be clowns willing to act foolish for attention.
Without web-of-trust or pagerank filtering, hashtags can be as bad as Global.
I was going to suggest hastags but I regret following them.
I need to follow more people, especially those who are actively posting good stuff. Suggestions?
Running a routing node requires a skillset and a substantial amount of capital. I doubt many pleb-nodes are getting anywhere near that kind of rate.
"France is gay." - @nprofile…zk3a
#nevent1q…cuh4
What the literal fuck is this?? This is what makes conferences not be taken seriously. We are trying to replace the existing monetary system with one built on truth. This is a deadly serious mission we are on. This shit makes us look stupid and unserious. Do better @nprofile…ksf4 #Bitcoin
https://blossom.primal.net/862b58c3a4ca3d5938c94ddef4ff7a1ec488a0743668bf65952eb93eb3369684.mp4
https://blossom.primal.net/121c27c68ba1e0363fc6fec4619f434d2566ea4fe9f46a2200fa53b7154d9e0e.mov
Wow, so far I’ve only seen peanuts.
Holy Shit!!!
9.7% REAL yield on a payment network while holding the keys to their BTC the entire time!!
Holy shitballs that is absolutely insane! This has to be the craziest thing to come out of the conference this year. I don’t think people will get how big of a deal this is.
Things are about to change big time. This is fucking nuts.
https://blossom.primal.net/90b974584bcb0cd99cce852ffb7bf63442b6d704dfde6765467c8c2d119c92d9.png
Lists can work for this purpose. Keep a very short list of your favorite npubs and some clients, such as Amethyst and Coracle, will let you view that list as a feed.
Other than that, Nostur is the only client I know of that will notify you when there are posts from an npub you have "subscribed" to.
Have any clients implemented favorites yet? There are like 10 or so people who's notes I really don't want to miss and there's no way I see to do that yet
#asknostr
There are a ton of ways to follow an npub without it ever being seen in a follow list, anyway. Follow count is a useless metric. I would love to see clients get rid of it altogether.
Primal Android wallet settings:
https://relay.brightbolt.net/bd292ec0cd2d3e6a53e5c44c8cdcb067ab4bfa86341d7583632a98acff7aa3d8.jpg
Primal iOS wallet settings:
https://relay.brightbolt.net/cc00756d5f5234f3b3f3cb1481ad3a1d57ed8b7605d43ed4c93e78c811e7bd6f.jpg
These are both logged into the same npub. So iOS still doesn't have the option to connect a different wallet. Only Android.
This did not disappoint. Great discussion @nprofile…mctc and @nprofile…ucf3!
#nevent1q…r7fa
https://fountain.fm/episode/rrhOoP3LoVLMCitU58uw
One of my favorite things about The NOSTR is that the "followers" count is _never_ right. Makes me smile every time I first flip to my Amethyst profile and it reads like "12"
"Good. I don't want to know."
Stay humble, etc.
I see it in Primal IOS though, but it doesn't work i believe
Which part of this is plug and play?
https://docs.btcpayserver.org/assets/img/DecisionDiagInstallBTCPayServer.381f8b42.png
That I did not know, and that's a really good option, too! Thank you sir! 🫡
That would be fine for me, who likes to tinker and self-host and do full self-custody, but that's not my buddy's cup of tea. He just wants something he can plug into his web store, connect a wallet like @npub1h2q…w8ch , and it just works.
@npub1cwn…raju any plans to add Shopify integration? I have a good friend who runs an online store built on Shopify and I know he would love to have a simple way to accept Bitcoin.
Primal's advanced search FTW!
About the only thing I use Primal for consistently.
Check the timestamps 😉
Mine: 1748464026 (20:27:06 UTC)
@npub1q22…zq27 : 1748464055 (20:27:35 UTC) REALLY CLOSE!
@npub1lrn…qnw5 : 1748464128 (20:28:48 UTC) Over a minute later, and a different note with only 12 responses instead of the one with 124 responses.
Oh, I agree 100% that Nostr should be as easy to participate in as centralized platforms.
When you can tell me how much easier it is to set up zapping on Facebook, you might have a point. We're doing things here that are not possible on those platforms. Can you imagine what the process would be for connecting your bank account to Facebook so you could tip your friends' for their posts? Connecting a lightning wallet to a Nostr client is FAR easier, I assure you.
To participate in Nostr is dead simple. Download a client, generate your keys, put some info in your bio (or not) and start posting, commenting, following, reacting, etc. You can just stick with the default relays and media servers your client has prefilled. It takes WAY less time or effort to just "participate" on Nostr than it does to participate on a centralized platform. Have you tried setting up an account on X lately and the hoops they make new users jump through? It's ridiculous!
But there is a world of difference between simply getting started participating on Nostr, and being able to make the most of all that Nostr has to offer, such as being able to send and receive zaps, choosing the right client for the content you are interested in, properly protecting your private key, and all the other stuff that Nostr enables beyond just writing and interacting with kind 1 notes.
Zaps are something we take for granted now, since they have been integrated into the vast majority of clients, but that was not always the case. Nostr has been around since 2020, and zaps weren't even a thing until 2023. Before that, we were just pasting lightning invoices into our notes and hoping someone would be generous enough to pay them. There are plenty of folks on Nostr who do plenty of participating, but have no interest in sending or receiving of zaps.
You only need to provide that to use Primal's built-in wallet, which is provided by Strike.
If you have a Nostr Wallet Connect compatible wallet already, you can link it to Primal in their Android app or on Primal web. This feature is not available on Primal iOS, yet.
You'll have to be more specific. What client are you using?
You can't. Assume everything is fake that you didn't see happen in person, unless signed by a private key you trust who has first-hand knowledge about what they are stating.
You guys accepting Bitcoin via Zeus now?
@npub1c87…8avm @npub1get…0nfm , any ideas what the issue is, and why my Alby Lightning address can't fetch a workable invoice via the LNBits NWC string? Creating an invoice via the extension or Alby Go, or Zeus wallet works just fine using the same NWC string. It's just the Alby Lightning address that's not working.
There is no need to become a "Lightning jockey" to use Coinos or Minibits. Both are dead simple. And to connect them to Alby, you just need to snag a Nostr Wallet Connect string from the settings and paste it into your Alby account settings. Specifically, go to Settings > Wallet Configuration and choose to link a wallet. One of the options will be to do so using Nostr Wallet Connect. Choose that option and paste in the connection string you got from Coinos or Minibits. Then you're done.
No need to set up channels. No need to manage liquidity. Just free, custodial Lightning.
I do like the idea of Alby partnering with a custodial wallet provider, but I doubt they would go that direction. They are wanting to promote self-custody Lightning. That would be a step in the opposite direction, and a tacit admission that self-custody isn't for everyone.
Popped into Damus on my iPhone and the feed only shows people I follow. The only way to see non-followers is to go to the search tab, which shows all notes on the relays I have set up. If that's where you are going and seeing stuff you don't want to see, I don't know what to tell you...
The other possibility is that you have followed some hashtags. Doing so adds any post that includes that hashtag into your main feed. That will end up putting posts from people you don't follow into your home feed. Also, do you suppose malicious actors might add popular hashtags into their posts in order to get their content in front of people who don't want to see it?
Yep. They absolutely do. Unfortunately, this has made hashtags close to useless, unless you have a heavy web-of-trust or pagerank filter applied to them, which Damus does not... Imagine that, a censorship resistant protocol where it is actually difficult, to the point of being close to impossible, to censor.
I would recommend trying out Nostur instead. It has built-in web-of-trust filtering. Another good one is Coracle. No iOS app for it, as it is a web app, but you can use it pretty easily by first downloading @npub1h0u…rwx8, then log in with your nsec and go to the built-in web browser and navigate to https://coracle.social/
I use Alby Hub all the time. I have never paid a sat for it. It is 100% free to host yourself. You only pay Alby if you want them to host it for you.
Your only cost is setting up channels, but that's not Alby. That's just how Lightning works. You have to pay an on-chain fee to set up a Lightning channel, because a channel is just an on-chain UTXO shared by two parties. You also may need to pay your channel partner to keep the channel open, since it locks up their liquidity.
And there are good free options for Lightning wallets. I mentioned @npub1h2q…w8ch already. There's also @npub1kva…tkzv. Both of them can be connected to your Alby extension for free. You don't need to use an Alby wallet with your Alby extension.
Yeah, there isn't another one. Alby is it. The other extensions are Nostr signers only and have no Lightning wallet integration.
Alby got rid of their custodial wallet. In its place they gave us an incredibly user friendly, self-custody, Lightning node in Alby Hub. Good on them, IMO.
That said, if you still prefer free custodial wallets, you can use @nprofile…0pev. You can even connect it to your Alby extension, if you want.
What is a good browser extension that allows both nostr login and recieve/send sats? I am looking to replace @npub1get…0nfm since they effectively destroyed their free wallet.
#asknostr
Yeah, I looked at their official announcement page (https://squ.re/btc) and it's not expected to be available for most merchants until second half of 2025 and possibly into 2026.
Way to get us hyped, tho, right?
Square Soon ™️ 😂
https://image.nostr.build/e798555c64b65d6758593c89a62e9f306b41f606c94fa3d878fec15fdc9db712.jpg
I was not able to activate or link my LN wallet in primal. Do you really have to fill in an email address and personal information to zap with primal? #asknostr #primal
What client are you using that your feed is filled with people you aren't even following?
Part 3 of the #AndroidElite setup, covering #Amber Signer is out now!
Part 4 covering #Amethyst will take a bit more time. There is much more to cover for a tutorial on a full #Nostr client, especially one that packs in as many features as Amethyst, and it will be the longest tutorial of the series, I am sure.
#naddr1qq…xwma
Eh, I would still reserve that for merchants that are keeping at least a portion of the sale as sats.
BTCmap has a lot of work ahead of them
Need me a map of merchants that use Square, now...
This is what I wanted to hear! Awesome! This is gonna be a huge factor in adoption I think.
#note19qq…3ez2
It's actually far more simple.
Without the outbox model, you have to keep adding more and more relays that you read from so you will see the posts from all your followers, and more and more relays that you write to so that everyone who follows you will see your posts.
With outbox, you can have a handful of read relays, a handful of write relays, and other users' Nostr clients just read from whichever ones you wrote to and write to whichever ones you read from. You as the user don't have to do anything to make sure that you can see the posts those you follow are making. Your Nostr client just looks up what relays they are writing to and shows you their notes, even if you don't have them in your relay list.
It's delightfully simple when properly implemented.
Pools will always be profitable. They just charge a fee to miners for their services.
Miners themselves operate on thin margins. Sometimes they are profitable, sometimes they aren't. Miners come and go in Bitcoin based on who can stick it out, whether they can find stranded energy, and how well they run their operations. Plenty of mining companies have gone under in the past and plenty more will go under in the future, yet overall network hashrate keeps climbing.
Thanks for the tip! I will check it out, as I have a chunk of writing to get done over the coming weeks.
@nprofile…mctc has yet to drop an uninteresting episode.
This should be an interesting episode.
#nevent1q…q3ch
Being able to pay any merchant who uses square from my Lightning wallet is pretty cool, for sure.
Every merchant being able to auto-covert a portion of their sales to Bitcoin is even better. Though that will receive less fanfare, I'm sure.
#nevent1q…wlpx
OnlyOffice is now my go-to editor on the #linux laptop. And I find that the open document formats (docx, xlsx) are handled far mor reliably than the LibreOffice formats (odt, ods).
YMMV.
it will be on by default for all sellers, allowing people to pay however they want, and sellers will never miss a sale.
by default it will auto-convert to fiat, and sellers can switch that to holding the bitcoin instead. i hope most do that. but they can also use our reserves feature to convert a percentage of incoming sales to bitcoin.
#nevent1q…w6tj
If you get a lot of spam replies, I recommend using a popular paid relay like nostr.wine. You don't have to pay to use it as a public inbox relay, since you'll only be reading from it, but only those who have paid will be able to write to it. Another option is a web-of-trust relay or two, and the reply spammers likely won't be on the relay's white-list. A more extreme option would be to run your own zapbox relay, which means you won't get replies from anyone except those who have zapped you above the threshold. It's sort of a dynamic paid relay that resets its whitelist on a recurring basis.
If you don't have a lot of reply spam, public relays work just fine, and broaden who is able to reach you when they reply.
Nostur doesn't use the "outbox/inbox" terminology. Instead, you just configure which relays you are using to read from, write to, and search from. Then you "announce" which relays you want others to see that you are reading from and writing to. Announcing just creates a new kind 10002 (replacing your old one) that others can find, listing your read and write relays. Read = inbox, write = outbox.
Why purplepag.es? That's an indexer that only stores kind 10002 notes. No one will be able to write notes for you to see there. Stick purplepag.es in your General Relays.
Public relays can make decent inbox relays, so long as you aren't getting a bunch of spam. However, this is where paid and web-of-trust relays shine, really cutting down on the amount of reply spam you get, if you have them set as inbox relays.
For most clients, they just list your relays as read (inbox), write (outbox) or read/write (inbox and outbox).
Now, we've always had the ability to set which relays we read from and which we write to in our Nostr clients. But the outbox model adds a bit of functionality to these choices. Without the outbox model, you have to set read relays that your follows are writing to, or else you won't see their notes and replies, and you have to write to relays they are reading from, or you won't see theirs. That has a centralizing effect over time, and discourages the use of smaller relays.
On Nostr clients that support the outbox model, your inbox relays aren't the only ones you read from. Rather, they are where other users should expect that you will see a reply, reaction, or zap, and clients should write notes that mention you to those relays. Meanwhile, outbox relays are where you are writing to, and Nostr clients trying to find and display your notes should be fetching them from those relays. That way a user who follows you might have a completely different set of relays that they are reading from by default, but they will still see your notes, because their client is fetching them from your outbox relays.
Will be covering logging into the Zapstore in part 3, after installing and setting up Amber, and also connecting a wallet and zapping app releases in part 5, after setting up Coinos. So, not done with Zapstore info entirely, yet. Just didn't make sense to cover those bits until then.
Part 2 is out now!
#naddr1qq…jr6u
Thank you! This is awesome
Yes. The Primal app IS writing your notes to Nostr relays, even though it doesn't read from them. If you go to any Nostr client, your notes, comments, follows and followers will all be there waiting for you.
I encourage you to try out various Nostr clients. Each one does things a bit differently and has certain strengths and weaknesses.
For instance, even though I rag on Primal a fair bit, I still use their advanced search feature quite a bit, because it helps me find a particular note I am looking for really easily. Yet, when it comes to searching for a particular user, I always use Coracle, because I know that it will give me the legit user, based on web-of-trust, as the first result, whereas other clients may surface an impostor as the top suggestion. If I want to browse a specific relay's feed, I can definitely do that in Coracle, but Jumble is a better experience for that. Then for direct messages I stick with 0xChat, as Primal only does NIP-04 messages and while Amethyst does NIP-04 and NIP-17, it still seems to miss some NIP-17 messages.
I believe this is called a "Darwin Award," when an idiot does us all a favor by taking himself out of the gene-pool.
Stupid fag
#gun #gunstr https://video.nostr.build/18f6eeb60d6717d4a9cbcc8c96abe189ea1bfd302752ad33c35f198668d01b27.mp4
If you are set on using Primal as your wallet provider, then the only way to have a custom address is to subscribe to Primal Premium.
If you are open to looking into other wallet providers, there are a few options that allow you to set up a custom lightning address.
- Coinos.io allows you to set a custom lightning address for free.
- Minibits has a one-time-fee to customize your lightning address.
- Alby allows free customization of your lightning address, but requires you to connect a separate wallet via Nostr Wallet Connect, or run a self-custody node via Alby Hub.
- Misty Breez allows you to customize your lightning address for free, but it has a minimum receive amount of 100 sats, so it's not ideal for a zapping wallet, since most folks zap smaller amounts than that.
- Zeus lets you set up a custom lightning address for free, but you have to run their node on your phone, with all the liquidity management that comes with it. This will be changing in their next release (currently in beta) that allows users to receive via eCash until they have built up enough to create their first lightning channel.
LND Rest is a pretty standard way for you to connect your LND node to a wallet app, such as Zeus. However, for node implementations like Start9 and Umbrel, this has to be done over Tor, so it can be quite slow and unreliable to connect.
LND Connect is a way to connect Lightning Terminal running on your node to to Zeus, if I remember right. Lightning Terminal can allow you to set up separate wallets that all use your node's liquidity. It is also much faster and more reliable than LND Rest, because you don't have to connect via Tor.
Embedded LND is just Zeus' node-on-your-phone implementation. It doesn't connect to a separate Lightning node, but rather requires you to manage liquidity in Lightning channels within Zeus. To account for the fact that your phone will often be offline, Zeus uses hodl invoices to hold your received funds for you until you reconnect. I believe they have also implemented a way to use eCash until you build up enough of a balance to justify opening a channel, too, but I haven't had a chance to play with that yet.
Nostr Wallet Connect is a way to connect any compatible wallet to Zeus, whether running on your own node at home, held by a custodian, or even a Nostr wallet that uses eCash stored on relays. Nostr Wallet Connect uses a Nostr relay between the host wallet and Zeus to send encrypted transaction and balance information back and forth. It works quite well, so long as the relay is online. As for where you get the connection string, that is going to differ based on the wallet you are wanting to connect to Zeus.
I believe PDF upload is only for paid accounts.
The concept is sound, though. As long as you have a place to host the PDF, upload it there and copy/paste the url into a Nostr note.
Part 2 - The @nprofile…tdq0 is out!
Part 3 - Amber Signer coming soon.
#naddr1qq…gc0x
#nevent1q…s60e
#Android #Nostr #AndroidElite
Upload to nostr.build then copy and paste the link on your post
@npub1nxy…avr7
Anyone know how to post a PDF to NOSTR?
Thanks.
#asknostr
"Reads" on Primal are just long-form notes, and they can be created from a number of different clients, including habla.news, highlighter.com, untype.app, and yakihonne.com.
Primal also recently added their own long-form composition tool available at https://primal.net/myarticles
So sue me for my proper punctuation. lol
Yep. Can't understant the solution without first understanding the problem.
Bitcoin: A peer to peer electronic cash system.
⚡️Stack Sats with ASL⚡️:
This message is easier than it looks-
1st person to decode the cipher gets zapped 221 sats
#asl #signlanguage #homeschool #grownostr #Interpreter #microlearn
https://image.nostr.build/b5b63dc5838bc41cd52d8b9dd5f2d252753596130bcbec6867fa7cb029813537.jpg
By first establishing with them the problem of inflation.
#nevent1q…ecn2
Exactly. I feel like note aggregators are a centralizing force. Why do the hard method of looking for notes from a user's outbox relays if it is almost certainly also saved to a note aggregator? Heck, that's Primal's entire architecture, right?
Indexes, by contrast, can be helpful for encouraging decentralized relay usage, since the indexer doesn't store the content itself, only points to where it can be found, and there can be multiple indexes, since it takes up a comparatively small amount of space.
I know that an index of all kind 10002s is currently around 50MB, which means Nostr could 20x before the index even grew to 1GB. I'd be interested in finding out how big an index of all note's hex IDs, paired with the author's hex pubkey would be. A lot bigger, I imagine, but likely still more than realistic for a standard PC to store several times over.
There is always some amount of trust.
Even if you are using open-source wallet software, if you can't verify the code yourself, you are trusting someone else to have verified it.
Could wallet software show you a false receive address and just display what you assume to be the correct balance? Yup. It could, and it could do so regardless of whether the wallet is connecting to your own node or someone else's.
Only use wallet software that is tried and tested, like Sparrow, Nunchuk, or Spectre. You can also use multiple of these in conjunction. For instance, use a hardware wallet to store your actual private key, and then use Nunchuk on mobile and Sparrow on desktop, both only having access to your XPUB for generating receive addresses. Then you can confirm between the two that the addresses generated are indeed associated with your XPUB, and not being swapped out by the wallet software. As long as any receive transaction originating from Sparrow shows up in Nunchuk, and vice versa, you know that the address wasn't swapped out, because the chances that the developers of both Sparrow and Nunchuk are colluding against you are small.
Using your own node with the wallet software you use for transacting is still important, but not for the sake of false addresses being swapped in place of real ones. Rather, you should use your own node for the protection of your privacy. Using someone else's node with your wallet software means the node operator can potentially associate your UTXOs with your IP address, and with one another, so that they will know your full balance.
Got it. That makes sense. Thank you, sir!
I don't know if there are other aggregators out there, other than maybe Primal. But aggregating all notes is only going to be realistic for so long, and nostr.band has been known to go down from time to time. 😂
Most users still post to one or more of the big, public relays, too. That would be relay.damus.io, relay.primal.net, and nos.lol. Having them on the fallback list would always be a good idea, but this is also just a stop-gap rather than a solution.
If @npub1gxw…k8jl's client is going to be generating the nevents pointing to these notes, though, he should be able to include relay hints in them based on the author's outbox relays. Then there is only an issue finding those notes if the author changes their outbox relays, or there is another client that starts using the same note kind and doesn't include relay hints.
The outbox model is great, if you know the note author, since you can just look up their relay list... Maybe note aggregators like nostr.band will one day be unrealistic and they will just aggregate the note ID and author's pubkey, then the client can look up the author's outbox relays based on that.
I zapped 2k sats to the @nprofile…f7xn npub, but I am still getting this error:
https://relay.brightbolt.net/01e846d727e43317b428c44ca3b52e86d9c0d2600369779add615cdfaed4f42f.jpg
Never received a DM.
Amethyst and Coracle will likely be a bit slower than Primal, just by the nature of the fact that they are actually reading from Nostr relays in real time, and some of those relays will be slower to respond than others. Additionally, if you have any of Amethyst's Tor privacy settings turned on, it will be a bit slower.
Primal apps, by contrast, don't read from relays at all. They only read from Primal's centralized caching server that aggregates notes from the relays, which is why it generally works a bit faster than other clients.
On Primal, therefore, you only see what they have configured their caching server to show you. They can censor anyone at any time simply by not aggregating their notes onto the caching server, so that no one who uses Primal will ever see them.
You give up nearly all of the censorship resistant properties of Nostr by using Primal, other than the fact that they DO write your notes to the relays listed in your Network settings.
And that is the distinction between being just an app with good UX vs being an actual Nostr client.
Nostr clients do the following things:
1. Fetch notes from Nostr relays.
2. Verify the signatures of those notes locally, to ensure that the content hasn't been manipulated.
3. Display the verified notes to the user.
4. Provide means for the user to write their own notes to Nostr relays after they have signed them with their own private key.
Primal only does 3 and 4 above, offloading 1 and 2 to their caching server. So it's a half-client.
Additionally, and possibly more egregiously, if a new user sticks with Primal's defaults, Primal will be in control of their entire Nostr experience. Primal will control what they see via their caching server, Primal will also be one of their handful of write relays, Primal will be their media server, and Primal will be their Lightning wallet.
The entire point of Nostr is to separate control of all of those things, so they are not controlled by a single company, like legacy social media. Any Nostr client worth their salt should separate the ownership and control of each of these elements by default. And while it is true that the user CAN change all of these defaults in Primal, most users will simply stick with the defaults. Technically someone can even select a different caching server than the one Primal runs... Except that no other options exist.
Maybe check an aggregator like relay.nostr.band? That's a temporary band-aid for the issue, though... What client is generating nevent URIs without any relay hints?
Folks on iOS have things I am jealous of, as well. Nostur is probably my favorite mobile client now, but only available on iOS, and Android is my daily driver.
To each their own, I suppose. UX is definitely great, but hard to call it a “client,” strictly speaking.
It’s a solid Nostr app, but the best actual client on Android has to go to Amethyst, IMO. Coracle is pretty solid, too.
You should have gotten DM. Zap2relay zaps are not published
Also yes
I zapped you and I see the outgoing in my wallet but the note didn’t update. Did you get it? @npub1226…grkj
Yes! I would love to have a relay, for instance, that automatically aggregated the notes from everyone I follow, allowed anyone within my web-of-trust to post for free, and allowed anyone who had zapped the relay above a threshold to be whitelisted for a month.
Welcome to Nostr! If you have any questions just use #asknostr and some great folks will help ypu out.
Think this can be a useful pattern for publications conditions beyond a personal mailbox btw.
Probably the most convenient and Nostr native way to pay for a relay.
#nevent1q…pvv3
⚡ Announcing: Zap2Relay
You can now fully pay for a relay without ever leaving nostr 👀
Simply zap this note/npub with 1000 sats or more, and you will get the proportional amount of time added to your account. (see https://nostr.land for info)
For a short time, there is a 35% discount on Zap2Relay payments. 👀
(Anon/private zaps do not work since they cannot be attributed to you. Your zap is never published.)
I get so many going on #AlbyHub for testing stuff that I lose track of them and just nuke them and start over sometimes.
Yup, that would definitely keep it from working. 😂
Thanks. I set it up but I guess I deleted the NWC wallet in AlbyHub for it so it failed. :(
You can zap notes too, but you have to go into your settings and add ⚡ to your options for note interaction.
Nostur works great for zaps. Haven't tried it with Coinos specifically, but shouldn't be too difficult.
Nostur has a place in the settings (scroll down for a bit, because it's not near the top) to add a zapping wallet. There are several options including adding via Nostr Wallet Connect, which is the one to choose.
In Coinos, you just need to go to the settings, Nostr tab, and add a new connection, name it and give it a budget, then copy/paste the connection string to Nostur's zapping wallet settings and you're good to go.
Can even install Coinos as a PWA.
It's in the settings but you can only zap profiles I think.
https://image.nostr.build/d0ca5d67b809d6129eeada63590772a949f189d44f6c48b1db5fc88d9c75e4f0.jpg
https://image.nostr.build/3dc8f2e0b3ce61d273375a981b6cc549aefdb75d4cd282ed258f4103e5448088.jpg
Damus has zaps again and works well with coinos
Any docs for how my brother can get a (custodial) wallet setup for zaps on nostur? I am not sure how to guode iPhone people in onboarding
#asknostr
It's by far the best client for android.
Is there some NIP defining how to link to a Nostr event given a specific relay? NIP-21 does not define a relay unfortunately... #asknostr #devstr
MiniBits is a pretty good option, as well. It's a bit slow for zaps going through, last I tried it, though.
So, what if the relay bases its policy on the tags I mentioned could be added to user A's kind 10050, and if the AUTH challenge reveals that user B attempting to write a DM to the relay doesn't fit within those criteria, the relay returns a denial. User B's client then refers to user A's 10050 to see what can be done and suggests user B can add postage or PoW, since user A's 10050 states they will accept messages with those attached?
As with most things on Nostr, there's more than one way to get it done.
Primal has their new long-form composition tool that @npub18am…p424 and @npub1spd…q6j7 mentioned.
I am a big fan of https://habla.news/ for publishing my articles.
From there you have:
- https://highlighter.com/
- https://notestack.com/
- https://yakihonne.com/
- https://untype.app/
Heck, there's even a note taking app you can download to your desktop that can publish long-form articles to your specified relays: https://comet.md/
Or, if you are a user of Obsidian notes, there is a plugin for publishing them to Nostr as long-form articles.
Yeah, Facebook groups are big for the towns around me.
That I am not sure on. So the idea would be that before writing a message to user A's inbox relay, user B would need to use AUTH to sign a challenge, and as long as the signature matched someone within user A's web-of-trust (or other filter criteria) the relay would accept any message sent to it through the same connection, even though the message itself has no indication of the identity of the sender?
That could work, I think... Admittedly, I don't know a lot about how exactly AUTH works.
There's a few.
Olas was already mentioned.
https://slidestr.net is another and also https://lumina.rocks/
Kristen! If you're reading this, you're about to see why Steak 'N Shake should join us here on Nostr! Nostrafarians, please zap, share, and leave a comment for the Steak 'N Shake Global Brand Development folks.
All zaps on this post will be used to purchase shakes at the Fremont Street Steak 'N Shake next Thursday evening during the Bitcoin For Corporations Meetup (RSVP at link below) to not only show the power of Bitcoin, but the compounding effect of Nostr as a protocol, social media network, and circular economy.
You'll see how you can use Nostr to build and foster the Steak 'N Shake brand identity, value, and community within the decentralized ecosystem. Like Bitcoiners, Nostr users are extremely generous and fiercely loyal towards those that share interests.
Steak 'N Shake is a pioneer in Bitcoin payments so why not follow suit within the decentralized social media space, too?
@nprofile…8m4j @nprofile…0xaw @nprofile…zx3h @nprofile…hs8c @nprofile…vvhl @nprofile…xh4c @nprofile…6dtc @nprofile…rjkj @nprofile…38q9 @nprofile…6un7 @nprofile…yces @nprofile…l2yj @nprofile…6z38 @nprofile…a0xg @nprofile…2wva @nprofile…wvc3
https://www.meetup.com/bitcoin-for-corporations/events/307959213
#asknostr #grownostr #bitcoin #btc #bitcoin2025
I also have this version available. Someone wanted the larger print on the back.
https://relay.brightbolt.net/dbdda1936fb27e1b21664600e68e277456f05f133d226be33df79f1541720a9c.jpg
Yeah, technically Liquid is NOT self-custody. You can be rugged if the members of the federation collude. It's a different trust arrangement than a single custodian, to be sure, but it's still a trust arrangement nonetheless.
The Lightning side of things is just a pass-through on the way to your Liquid wallet, and runs in the cloud, not on your phone. They are using an LSP for Lightning liquidity and they just forward the sats to your wallet on Liquid, which does not require your phone to be online whatsoever.
What extension are you using? I am using Alby and not being asked to login repeatedly as I browse.
Of all of them, Pokey is the biggest power draw, but still only 3% of total battery usage. Your mileage may vary, though.
It's written. I just need to drop in screenshots and a title image. Hopefully tonight or Monday.
Lol My Pixel 7a got through a whole day (minus Pokey) until I put Zeus on it. Now I have to do the heinous act of charging my phone for an hour toward the end of the day. It's so horrible.
Now tell us about the backpack-scale fusion reactor you use to power those monsters!
New tutorial series dropping for my friends on #Android!
Here's the introduction with what it will be covering:
#naddr1qq…z7n7
That’s theoretically possible using bunker connections with limited permissions, but adds a whole mountain of complexity to it all.
Relays could enforce PoW requirements or payment requirements, but it would be an all or nothing sort of thing, since the relay would be unable to identify the sender to apply different policies to different classifications of senders.
@npub1jlr…ynqn made a good point here regarding NIP-17 DMs:
#nevent1q…arjc
Given that, I don’t think the filtering could be done by a user’s inbox relays. It would have to be done by the client after it has identified the sender by decrypting the giftwrap.
Can't really enforce it on the relay level without sharing the ability to decrypt the events, since sender metadata is obscured on nip 17.
I suppose I was operating under the assumption it would work like your email inbox. You technically still receive the spam, it's just shuffled away to a corner of the UI that you don't have to look at unless you are looking for a particular email that may have been sent to your spam folder. In the same way, your inbox relays would still store DMs from potential spammers (with maybe an auto-delete after a certain amount of time?) but you just wouldn't see them in your client's UI unless you specifically went looking for them.
That said, you are right that making it a policy that the user's inbox relays enforced entirely would mean that the inbox would look much the same in all clients, NIP-04 vs NIP-17 notwithstanding. The user just wouldn't have an option to browse the potential spam received for possible legitimate communications, since the relay would presumably be rejecting those messages.
If your inbox relay(s) respect your conditions it's easy to make it look the same in your apps.
For the sender to get this info up front, it would probably need to be in some sort of "DM Policy" event kind that can be looked up by the sender's client from the receiver's relays.
Maybe this "DM Policy" event kind would include a tag for types of senders that are always accepted that could be set to follows only, web-of-trust, or allow all (not recommended unless you just like spam); and another tag for other optional conditions upon which a DM will be accepted from those who fall outside the filters, such as exceeding a pagerank threshold, including a certain amount of PoW, or paid postage using an eCash token from a reputable mint,
Of course, your DM inbox would then look very different, based on which clients respect your DM policy and which ones don't, but my inbox looks very different from client to client already, based on which DM NIPs they support. 😂
Maybe these policy tags could be included in the user's kind 10050, since clients SHOULD already be looking that up to determine where to send the DM anyway.
None that I am aware of. It would definitely be handy to have requests split between those I probably want to see and those that are likely spam, and I think Vertex's pagerank would be a good basis for it.
I just tried doing the same. Doesn't seem to work for receiving via my Alby Lightning address, though.
Tried sending from Phoenix to my LNBits wallet connected to my Alby account using my Alby Lightning address and it says "The invoice returned by getalby.com is malformed."
When trying to send to my Lightning address from @npub1kva…tkzv, I also get an Internal Server Error that has the following details:
caller: "fetchApi"
status: 500
url: "https://getalby.com/lnurlp/dikaios1517/callback?amount=21000"
I can pay standard invoices created from my Alby extension connected to LNBits with both Phoenix and Minibits, though, so it's just the Lightning address that isn't working for some reason.
Any ideas? @npub1c87…8avm or @npub1get…0nfm?
Follower count is a notoriously difficult metric to track and impossible to track with 100% accuracy. I recommend only using it to get a general idea of how many followers you have at minimum. The actual number will be higher, but impossible to determine.
Regarding Primal in particular, the fluctuation +/- 40 or so all the time may be due to some follower bots that have been repeatedly following and unfollowing Nostr profiles.
In general, though, the difficulty of counting followers accurately is due to the way Nostr clients have to try and figure out how many followers you have. When it comes to giving a count of how many people you follow, that's easy because there is just one list, saved to your relays, that has all of the npubs you follow on it. The Nostr client just tallies up the number of npubs that show on the latest version of that list. Done. But when it comes to counting the number of npubs who follow you, your Nostr client has to reach out to ALL the relays it can and ask them for any follow list that has your npub on it, remove duplicates, and then tally them up. Now, some of those relays may not be reachable. Some of them may send back an error. Most likely, though, your Nostr client simply won't reach out to every relay in existence that has a follow list with your npub on it.
Then there is the more recent issue that there might be folks who follow you by some other means than adding you to their follow list. They might have your npub on another type of list that they can view as a feed, and that list might be encrypted. They also might just use a relay that aggregates notes from a list of npubs, or from a web-of-trust you happen to be indluded in, so even though they don't follow you directly, they are effectively following you, because your notes show up in their feed.
For all of these reasons and more, follower counts are inaccurate and should just be treated as a baseline approximation.
Yes, that is exactly right, but with some caveats.
It will broadcast the note to the relays you have set up to write to in your relay settings, which may not be all the relays you have. Some may be set up for read only.
The relays you send it to may or may not accept the note. For instance, if one of your write relays is a paid relay, it will only accept the note if the note author also has paid for write access to that relay. Likewise, any of your relays that operate on web-of-trust or other criteria for write permissions may reject the note.
The only relays that you can be somewhat sure the note will be accepted by are free and public relays.
Unfortunately, Amethyst doesn't give you much indication about which relays rejected the note or why.
What Blossom does is different from proving ownership. It simply proves that the contents of the referenced media has not been altered from its original form at the time it was uploaded to the Blossom server, and is therefore exactly what the author of the Nostr note intended others to see.
This is because the file name for the uploaded media is just the hash of its content. Therefore, when a Nostr client makes a request from a Blossom server for that file in order to display it to the user, it can easily check whether the hash of the content matches the file's name. If it does, the media has not been altered. If it does not match, then the client should not display the media and should show a warning, such as the red icon @npub16jd…33sv mentioned previously.
Of course, this offers no proof that the video was not doctored, modified, or otherwise "fake" prior to the time it was uploaded.
So, you have no assurances that the person who uploaded the video is the "owner," or just reposting it from somewhere else, and you have no assurances that what the video shows is not fake. You only know that what the author of the note intended you to see at the time they created the note has not been altered, or else it would not have been displayed to you by your Nostr client.
Been running LNBits with Amethyst for the last week or so. It has me considerong switching over from Alby Hub entirely, since I can have more than one connection string for each wallet, and separate budgets for each connection.
LNbits has the nwcprovider extension, works great. Doing a video later on how to run.
What would you recommend?
Breez?
Phoenix?
Zeus?
Which NWC wallet is best paired with amethyst?
#asknostr
Are there any clients out there that have solved the NIP 17 spam problem from a UX standpoint? It would be nice to separate "requests" into requests from reputable people in your network (based on wot or pow) and requests that are unlikely to be worth your time.
Listening to Rabbithole Recap. @nprofile…xafw, will you be uploading Opportunity Cost to the @nprofile…tdq0?
I ran into the same issue when downloading Olas.👇
https://image.nostr.build/b3c2341b94d43f5aecec60d3fd472d233b94909f9a3583c0f65ad0435c1a42cf.jpg
See:
https://nostpic.com/media/619af6a60b3fe4c733aaca061c522cc9c7cf1d87ef4c908facc5ed936d3bdf23/7310efd78473337c5a7b7b82e99e44930870a56e665b10061814d7e85eb7c91d.mp4
Never works. I tried many times. Only Keychat doesn't work.
It looks like the download was incomplete?
No, I absolutely get that, and I think it should be incredibly easy for a new user to get started, and then they can take steps to improve their setup over time, if they are inclined to do so.
That said, clients should have default settings that maintain the ideal of separation of control without the user having to manually change those settings.
It's ironic that you mention Primal specifically as a "client" that should add an external signer into their apps, as I think they are the worst in this regard of encouraging centralized control. A new user will be defaulted to only reading from Primal's caching service (there is no way to read directly from relays in Primal, even for experienced users), writing to their relay and a few others, storing media on Primal's Blossom server, and using Primal's wallet for zaps. The defaults are near complete centralization, and you also want to give them control over user login to other Nostr apps? Hard pass here. Using Primal's default settings is nearly as bad as just staying with centralized big-tech platforms, and with the addition of them controlling the default wallet, it just might be worse.
Compare that with an actual client, like Amethyst, which defaults to 12 relays, none of them controlled by Amethyst, three media servers also not controlled by Amethyst, and which requires users to bring their own wallet for zaps. If Amethyst wanted to have a wallet available for users, they could build in an eCash wallet that defaulted to a mint that they don't control, like Minibits. As such, I would be far more comfortable with an external signer being built into Amethyst than Primal, since there is separation of control by default for all the other elements of a new user's setup.
He showed how to do it on the mobile app, not on web.
Pretty sure he means Primal web.
Couldn't join the testflight for Comingle. Not accepting any more beta participants.
I wasn't aware of troop.is, so thank you for that one!
Is https://flockstr.com/ a dead project, then?
Say I am highlighting something I want to comment on. If the highlight goes to the feed immediately after it is made, there the feed will show the original highlight, and a few minutes later, my quote-post with my comments.
Also, if the highlight ahows in the feed on its own, without any context, it might be assumed that I highlighted it because I agreed with it, but my quote-post with my commentary might make clear that I highlighted it in order to disagree with it.
Now, if there is a way to add comments at the time of making tje highlight, so that it only shows in the feed once, I would be all for it.
> but it shouldn't go straight to the feed as soon as the highlight is made.
Why?
I know I would be interested in the deodorant. My wife and daughters would probably be all about the rest.
I think folks should be able to share highlights to their feed, such as quoting it within a kind 1, and have it show up, but it shouldn't go straight to the feed as soon as the highlight is made.
Very true.
One of the more confounding statements she made was that "hard money loses as money. We saw that with gold."
It's very much a recency bias sort of thing to say.
Monetary metals won the battle against all other forms of money over thousands of years, and only in the last 200 years or so has paper money taken over and then been forcibly decoupled from gold.
It also shows an ignorance to why physical gold and silver lost out in the end. It had nothing to do with their scarcity, but their lack of portability. Scarcity was why they won out compared to other forms of money, but lack of sufficient portability in a time when humans began moving around a lot more was their downfall. And that is a trait Bitcoin does not share with gold.
How does nostr feel about highlights in the social feed?
A) #YESTR
B) don’t care
C) verboten
D) what is a highlight?
#asknostr
#note1u97…l8dr
Is it possible? Yes.
However, since notes all need to be signed by your private key, you would need to be willing to give the auto-reply service your nsec, so it could sign events on the fly. You cannot pre-sign them, since you don't know who will be messaging you ahead of time or when you will receive their message.
Not something I would be willing to do.
Now do it in XMR/BTC terms.
She has a bit of a black-pill outlook, at least in the short to medium term. "But you can make a lot of money shorting just about everything."
Congrats monero on almost reaching your 2017 ATH in USD!
Only 8 years to almost break even
Pavk it up. @nprofile…afjn already dropped the best post of the day.
May as well wait till tomorrow to even try.
#nevent1q…209t
Now I can't install.
https://cdn.nostrcheck.me/619af6a60b3fe4c733aaca061c522cc9c7cf1d87ef4c908facc5ed936d3bdf23/23930753176bc5c6cf05677ca56a05c61b44ed28e151166eb4243636dd6e9882.mp4
Introducing PIP-177 (Pizza Improvement Proposal) to redefine pizza’s base unit —currently known as “a slice of pizza” — to “a whole fucking pizza.” By removing confusing fractions, this PIP aims to increase mainstream pizza consumption. No longer will you need to be ashamed when your friends ask how much pizza you ate and you answer “a slice.” Now you can proudly boast “I ate a whole fucking pizza,” which not only sounds cool but is also easier for everyone to understand according to me and the 5 other people who like this idea. Support PIP-177 today on Pizza Day and go eat A WHOLE FUCKING PIZZA! 🍕
https://blossom.primal.net/4415028eed3032f6047111745762c33890f95e436e71746731d4a83fc5395d72.jpg
THANK YOU! Updating now!
https://relay.brightbolt.net/fbc4c408ef89c00fa5661ece7a884861dc3adb7c981892d38c65920e0b123093.jpg
Thanks. It works after delete local cache.
@npub1kun…3lhe
@npub1vxd…rs50
🚨 Sats for answers 🚨
Been toying with the idea of expanding to new products. Lip Balm, deodorant, balm, skin cream etc. All with completely natural ingredients. Mostly Tallow.
I'd appreciate your feedback. What are you interested in, besides soap? Only actual answers will be paid. Don't just give me a 👍
Reply = 50 Sats
Reply + repost = 100 Sats
I'm genuinely curious. I want to know what the Nostriches want for their personal hygiene needs. Let me know, so I can continue to build.
Thank you 🙏🫂💜
Hmmm. Something must not be connected correctly. I am connected to my Alby Hub wallet on Primal Android and have no issues zapping. Of course, I also never set up a Primal wallet...
Either way. Primal is fine as an "I also use..." type of app, but I would make sure you are also utilizing other clients. I have a hard time even referring to Primal as a client, since some of the things clients are intended to do are offloaded to their caching server instead. You don't read from your selected relays at all, for instance, and you are relying on their server to verify signatures rather than that being done locally on your device.
As someone who worked for a company that regularly did password audits by paying someone to try and brute-force their employees' passwords, I can attest that a password manager is a must. I can proudly say that I never had any of mine cracked, and it was all due to using a password manager to generate strong passwords that I never had to remember.
You must be using Amethyst.
I don't know that there is anything like a consensus about it, especially since Amethyst is the only client I know of that supports zap splits for quote-posts.
Does that feature even work, though? I can't recall receiving a zap on a quote post that only a portion of it ended up in my wallet... Maybe both the user who created the quote post and the person zapping it have to be using Amethyst for it to work? If so, it's close to pointless without wider client adoption.
Either way, I think sharing zaps to the OP is a great idea, and basing the portion that is shared on how much you are adding to it is 100% appropriate. I would go even lower than 30% in some situations, though. Like if the OP was a low-quality post and I am using it as a bad example. 😂
I don't think scalability is a major factor in the near to mid term for Nostr, but I would be interested to hear what you think is the solution for scaling.
That was too limiting. We're becoming the decentralized social internet. We're coming for all of the centralized publishing platforms. Twitter was just the low-hanging fruit.
What makes it different:
No monolithic control. The same entity does not control where the data is stored, what apps are available to be used to access the data, how the data is displayed and what specific data is surfaced for each user, how advertisements are injected into users' feeds, what types of content are permitted, what users and subject matter are permitted... Control over all of these things is spread out among a wide variety of entities, from relay operators, to client developers, and DVM creators, so that users have choice while still being part of the same protocol.
Identity portability. You can take your entire social graph with you from one Nostr client to another. If one of them starts doing something you don't like, there is zero cost to switching, since all of your follows, followers, and content is immediately available upon logging into different client. Someone creates a new client for a different type of content? Just use the same keys to log in and your profile is already loaded with your social graph, who may have already started generating content.
Permissionless and Censorship Resistant. There is no need to ask permission to use Nostr. Generate a key pair, choose some relays, and start posting. No one can prevent you from signing notes with your private key. And once you start posting, you are difficult to silence, since your notes would need to be removed from each relay you are using, along with each relay that aggregates and indexes notes from other relays, and you can even run your own to ensure your notes are always accessible. A particular client could decide not to display your notes, or a particular relay might blacklist your npub, but anyone who wants to see your content will be able to so long as all clients and all relays have not colluded against you.
Content Ownership. Because your notes are signed by your private key, no one can modify your notes in any way without getting you to sign for it. If they want to store a copy of it on their relay, that's fine, but they have no ability to change what you wrote and misrepresent your words, because they will be unable to affix a valid signature to it. Likewise, while anyone can generate a new npub with the intention of impersonating you, Nostr web-of-trust and pagerank tools make it obvious to anyone who takes 5 seconds to look into it that they are an impostor. Moreover, no one can "hack" into your Nostr account and post as you without your private key, and keys being compromised is an exceptionally rare occurrence these days, thanks to better tools for key management.
No Slavery to the Algorithm. It's not that Nostr doesn't have algorithms. It's that the user gets to decide what algorithm they use to surface the content they want to see. They can choose to view a chronological feed of their followers' posts, a feed of all posts from their chosen relays, a feed based on a list they or someone else created, a feed from a particular relay that can be configured to surface specific content, a feed from a DVM that displays specific content, and a growing list of other options.
Zaps. I would be remiss if I didn't mention zaps as a major differentiator. Where else can you go and receive real value for posting a meme that made someone laugh, or for answering a question with good information, or for just encouraging someone who was feeling down? Moreover, there is no obligation for anyone to zap you, so you still do all of the above knowing that you may not receive anything in return. Receiving a zap as a small "thank you," is a feeling that cannot be replaced, though. You know for a fact that someone truly valued what you had to say. And a great side effect of this is Nostr has become a de facto address book for payments, allowing users to send money to any of their contacts permissionlessly.
I could keep going...
What is missing:
A good option for long-form, pre-recorded video sharing. WoT enabled YouTube replacement? Yes please!
Better content discovery, particularly for new users. Primal's set follow lists are a terrible practice, but Amethyst's empty feed upon login is a bad experience, too. I think the answer could be a combination of pagerank filtered following of topics the user is interested in, paired with user generated follow packs that are starting to be integrated into a few clients.
Relay suggestions. One of the most common questions I see is, "What relays should I use?" or "Which are the best relays?" or "Can someone suggest some good relays for me to try?" We need a tool that offers relay suggestions based on criteria indicated by the user in plain language. So, no "What NIPs do you need the relay to support?" Rather, "What do you want to use this relay for? A. Writing publicly viewable notes and receiving publicly viewable replies and reactions. B. Receiving private messages. C. Searching for other users and their notes. D. Writing notes that are only viewable by those I follow."
Speaking of private messages... We need to get DMs sorted. They're an absolute mess right now. The only app that consistently shows me all my DMs is 0xChat. Every other app leaves some types of DMs out. In short, if you aren't using 0xChat, you're probably not seeing some DMs, and that can be particularly problematic for anyone trying to sell products via Nostr marketplaces.
Finally (for now), consistent support for the outbox model. Clients should look for my follows' notes from their outbox relays, regardless of whether I have their relays in my list. They should send my replies and reactions to their notes to their inbox relays in addition to my outbox relays. This will greatly reduce the reliance on large public relays, and increase Nostr's decentralization, resiliency, and censorship resistance.
All keychat-related events signed by Zapstore have been removed from the relay. If your users have issues, ask them to go to Settings > Tools > Delete local cache
Let @npub1wf4…dgh9 know what device you are using and see if he might have some ideas why it won’t install.
You'd probably be getting close to the answer if you could figure out what percentage of those who call themselves Bitcoiners also run their own node and self-custody their stack in cold storage.
Of course, this also depends on what each individual defines as truly being a Bitcoiner. The protocol itself doesn't care, and Bitcoin has no authorities over it, so "Bitcoiner" is subjectively defined by each person who uses the term.
Sorry but It won't install the apk. I have other apks installed so not sure what the issue is. Cleared out some disk space...
Navigating the unraveling cycle of society
In this hard-hitting episode, @npub1clk…pup9 sits down with Bronwyn Williams, a South African futurist and economist, to dissect the collapse of trust in centralized systems.
Bronwyn analyzes how globalization and technology challenge institutional credibility, using South Africa’s governance struggles as a backdrop. She critiques AI’s centralizing risks, questions Bitcoin’s decentralized promise, and discusses ways businesses and individuals can rebuild trust.
📺️ Watch here:
https://cdn.satellite.earth/edd4dbf73e232ec74c70b7979b1fcb6071e9728d8c4f59f58f3b5644f74d1168.mp4
📺️ On YouTube:
https://youtu.be/DqWj2452hQI?si=q1N9hrpx5ejuVNxb
🎧️ Or listen in your favorite podcast app:
https://podcast.trustrevolution.co/
Interesting. Mine is one of the most used devices in my home, by me and my whole family.
To each their own, I guess.
I don’t know why I bought an umbrel server, I never use it. If you are considering buying one, don’t.
Well happy early birthday! My last one was one of those decade milestones that make you wonder how the time was quite so scarce.
My birthday is tomorrow so I’m feeling a case of the olds too. 😂
Coping with the fact that my oldest is now a licensed driver...
Bear markets are for building.
Bull markets are for bickering.
I don’t love it when bitcoiners quibble but I do love that I’m not in the conversation so I can just observe.
I’m tired because I’ve been just doing things but just doing things makes you busy and tired. 😩😂
Aw, why’s that with other options available?
For anyone having trouble seeing the note, here it is with a relay hint included:
#nevent1q…f9x6
Sporks are inferior. For spoon jobs, a spoon is better than a spork, and for fork jobs, a fork is better than a spork.
Sure, a spork CAN do both jobs, but not as well, and it's not usually much of an inconvenience to have more than one utensil when needed.
Welcome to Nostr !
#nevent1q…vfl4
Yep. In Primal go to Settings > Media Uploads, then enter the Blossom server URL you want to use in the "Switch Media Server" option.
You can also enable mirroring your uploads to other media servers and add them at the bottom of this settings screen.
Yep, it will always be a random nsec when you first install the extension, because Alby doesn't store your nsec on their servers, nor should they.
Glad you got it working!
Working fine for me. Answering this while logged into asknostr.site via my Alby extension. I also logged into Jumble, Coracle, and Nostr.build using it without issue.
I saw your question yesterday. I just didn't have a good answer for you. I don't generally make international phone calls. The few times I do need to speak with someone in another country, we generally have some common communication platform to do so, whether that's Signal, Keet, or even Hivetalk.
You and me, both. Hosting of media has been one of the bigger challenges for Nostr, and long-form video is probably the final boss in that regard. We've got good solutions now for photos and short-form video with Blossom servers, and maybe what @npub1wf4…dgh9 proposed here will be part of the unlock for longer videos:
#nevent1q…ve3t
Someone was mentioning that they used Olas to get a bunker string to sign into another client, so maybe Olas does. I just haven't tried because Olas is broken.
I generally like the idea of having a signer built into, say, Amethyst as a flagship client, reducing the number of apps that are needed to get started right on Nostr, but no client devs have taken on the task of doing so. Other stuff clients, like Olas, wouldn't be as natural a fit for this. Better to go with a client that is more likely to be a user's first experience with Nostr.
Then again, there is something to be said about keeping certain functionality separated. A large part of the issue with big-tech platforms is how monolithic they are. They own the servers where the data (text and media) is stored that you are reading from, they own your login information and can shut you out at any time, they own the apps you use to access the data, they own the algorithm that serves the data to you, and they own the advertising infrastructure that is their real means of making money.
Meanwhile, one of the best things about Nostr is that you can make sure all of these things are controlled by different entities, if you so choose, and have them work together relatively seamlessly. My content is stored on relays and Blossom servers that either I control or that other relay operators control, while I use a client that is developed by someone completely separate who does not run any of those relays, I connect a wallet that is self-hosted on my own node, and I use a key manager and signer that is not affiliated with any of the above. Yet, all of them just work together, with a few minor exceptions.
There is definitely convenience in having everything built and operated by the same company, ensuring it all works well together and that you have to interact with the least amount of outside applications as possible. However, we must keep in mind what we are sacrificing when we push for that level of convenience. Very likely, we are recreating the centralization we came to Nostr to escape.
I think even a week worth of blocks would have been enough duration to get a decent average, and keep the adjustment from being thrown off by a few longer block times, or really short ones, but a day definitely would be too short a time. So, the need for a smoothed out average explains why the adjustment doesn't happen daily, and the fact that 2016 is 6102 backwards explains why it was set at every 2016 blocks specifically.
Define "recovered."
Once data has been leaked, it can't be recovered. It's out there for scammers to pass around to one another forever.
Have they plugged the hole so no more data will be leaked in the future? Doubtful. This was due to employees who had access to the data being bribed to leak it. How confident can anyone be that there aren't any more Coinbase employees willing to hand over user data for the right price?
Oh, and by the way, the same issue exists at literally every single bank or other financial service that is required by law to obtain your personal and identification information.
The only sense in which Coinbase might recover from this is that the public is likely to forget it happened as they get distracted by other events in the news.
Back to Primal on Android, for now.
@npub10r8…t2p8 Could you please remove the second upload in the screenshot as soon as possible? Thank you!
https://image.nostr.build/77974441cee97b8a5d8dae256148d8fa70156ce51419e7f225fd752003be60ec.jpg
Live in 5 minutes at https://zap.stream/ !
#nevent1q…r7lk
#Minecraft #Minecraftstr #Gaming #Gamestr #Bitcoin #Lightning #ZapStream
Mistype... I meant 4:00pm pacific time.
I'll be streaming from 4:00pm to 8:00pm on zap.stream. Hope to see you then!
#nevent1q…4vq4
#Minecraft #Minecraftstr #Gaming #Gamestr #Bitcoin #Lightning #ZapStream
It definitely shows that the event referenced will be treated as a Nostr URI rather than a plaintext string. That's probably enough, particularly since the user can preview how the post will be rendered prior to publishing it.
Jumble, by contrast, doesn't give any visual indication in the composition window unless you toggle over to preview how it will be rendered. I definitely prefer the way Coracle handles it.
I would rather be asked to approve signing, and have the option to set that particular type of request to automatic in the future, or leave it a manual approval as I see fit.
I would also like approval requests to be very clear about what they are for. I'll pick on the @npub10r8…t2p8 a bit for this one. When you are signed in with Amber and you tap to install an app, Amber pops up a signature request that just tells you its for a "Job request" without any information about what sort of job is being requested. Selecting "Show Details" gives very little help.
https://relay.brightbolt.net/7a2d4d90c9e84c12b976d6ffcc237d8744c1b0a1c865a0fbaa5b202ced9be91f.png
Would the average user know what to make of that, or what the Zapstore is going to be using their signature for?
After doing a bit of digging, I discovered that this request is simply to find out the application publisher's "reputation" with the users I follow. In other words, which users that I follow that also follow the app publisher. That's a request I am fine with signing for, but the average user is going to have NO IDEA what a kind 5312 is for, or where to even start investigating it.
So, yes, I want to see what my key is being used to sign for, and have the option to accept or reject it, but only if the signing request can be put in plain language what I am signing for. Otherwise, I'm just going to default to rejecting the signing request.
I also only want one signing request at a time. Wait to send more until the first has been accepted or rejected. Not sure if this is more on the end of the extension needing to hold the additional requests in a queue, or if the client should only be sending the signer one request at a time, but it needs to be addressed. This is particularly an issue with DM decryption requests...
The amount of things that need to be signed may be able to be reduced as well. Anything that requires an event to be published to relays will always require a signature, and anything that is being retrieved from a relay that requires AUTH, as well, but not much outside of that should need to be signed. Thing is, almost everything needs to be saved to relays in order to enable interoperability with other Nostr clients. Anything that doesn't require a signature is obviously not being stored on relays, and is therefore not going to show up when you switch to a different client.
On Coracle there is clear visual feedback.
I think the way it will likely happen is from wallet apps just not have any reference to "Bitcoin" or "sats" in their UI, other than to stick ₿ in front of or behind the balance, so users will just start referring to sats as "bitcoins" naturally over time. Especially once you can no longer buy Bitcoin from an exchange, but have to earn it through productive work.
This was also asked and answered here:
#nevent1q…stsl
In short, it was first proposed in the Bitcoin Talk forums by a user going by "ribuck" on November 15th of 2010, and it was an offhanded suggestion to call 0.01 Bitcoin a "Satoshi," along with other names for smaller fractions of a Bitcoin.
It didn't catch on until it was suggested again by ribuck in February of 2011, but using "Satoshi" to refer to the smallest unit of 0.00000001 instead of just 0.01.
Gotta go with @npub1z0l…8ldk.
It's FOSS and you can just use the one @npub18pu…a699 hosts for public use, or you can run it yourself on your own server. There is an option to easily install using Docker. Best of all, it has Nostr integration.
The argument is that it IS broken. I disagree with the argument, but let me see if I can steel-man it.
1 Bitcoin = 100,000,000 sats is broken because...
First, the protocol itself has no idea what a "Bitcoin" or "sats" are. As far as the protocol is concerned, the only thing it knows about is that there will never be more than 2.1 quadrillion units. That being the case, if we are going to call the protocol "Bitcoin," then the units the protocol uses should be called "bitcoins." 1 Bitcoin or 1 sat are concepts completely foreign to the protocol itself.
Second, the idea of a Bitcoin not being just 1 base unit of the protocol is confusing to new users. Sure, they can understand how there are dollars and there are cents, and that 1 dollar being made up of 100 cents is roughly the same concept as 1 Bitcoin being made up of 100,000,000 sats, but they won't understand why it is useful to have such a massive difference in unit size. 1 dollar only has 100 cents, not 100,000,000 cents. 1 Bitcoin could have just as easily been defined as 100 sats, and that would make a lot more sense to folks. As it is, though, we know that we will have more divisibility (millisats) on layers above the base chain. So why not make the switch now to calling the base units of the protocol "bitcoins" and decide to call fractions of that unit, used on transactional layers above the base chain, something else?
Third, because a "Bitcoin" is over $100,000 these days, there is a unit bias that has caused many people to decide, "It's too expensive for me to ever even own 1 Bitcoin, so I may as well buy some of these other cryptos that I can own a lot more of, and if they even become HALF as valuable as Bitcoin, I will be rich!" These folks would be far more likely to purchase Bitcoin instead of crypto if 1 Bitcoin was a fraction of a cent, and they felt like they could get 955 Bitcoins for just $1, instead of only getting 0.00000955.
Fourth, as Bitcoin moves into being used as a medium of exchange, almost no-one is going spend 100,000,000+ units in a single transaction, like they did in the old days. There will be no need for wallets to show balances of X number of Bitcoins when 100,000,000 sats is such unheard of wealth that the only entities that have enough to own a full Bitcoin are nation-states, large corporations, and the uber-rich. Instead, wallets will ONLY show X number of the base unit (currently called sats), and perhaps a decimal place with fractions of that unit behind it. If no one is spending a whole Bitcoin anymore, then the concept of that unit ceases to be of any use. It would be a shame if we lost the use of the term "Bitcoin" to refer to the asset simply because no one ever spent that much of it anymore.
Finally, it's only really the OGs and Bitcoin-geeks who actually know what sats are. The vast majority of people who have bought Bitcoin have no idea about them. Phasing out the term makes sense for the future of Bitcoin and will only really upset a couple hundred thousand people who even know that sats exist at all, so the term is really serving no other purpose than to be a barrier to understanding Bitcoin for new adopters. We should be trying to remove as many such barriers as possible, so that as many regular folks start buying as possible before the nation-states and large corporations start buying in earnest, making it harder and harder for the average Joe to build up any meaningful amount.
Now, even though I disagree with changing the term at this time, I do think a lot of these arguments have merit, and it may very well be that we stop referring to 100,000,000 units as 1 Bitcoin in the future, as it becomes more and more rare for anyone to own that much, and we are transacting more and more in Bitcoin as we move into medium-of-exchange phase.
For now, though, I think it is critically important to maintain the one thing that the vast majority of people who have heard anything about Bitcoin are aware of, even if they don't own any: There will never be more than 21 million Bitcoin.
If we flip that script now, it damages the fixed supply narrative too much to outweigh the benefits, in my opinion, and the reliably enforced fixed supply is THE key feature of Bitcoin. Going from only 21 million Bitcoin to 2.1 quadrillion will be understood (incorrectly) as a MASSIVE supply increase, shattering any confidence that Bitcoin's supply can't be changed outside of those who actually understand how the protocol works and that the supply wasn't changed whatsoever. Therefore, we should hold off and let the change in how we refer to sats vs Bitcoin happen on its own, if it happens at all.
Users should be warned though
Coracle already fixes the URL on behalf of the user, which is the correct implementation if you ask me. Damus also does this at least in part, and others I forgot. I think it's going to be well.
I see a qualitative difference here, though.
There is no "users will do it with ____ expected result" when it comes to edits. If the devs don't add the ability to edit kind 1 notes to their clients, then users won't edit them, because they can't. Not without overcoming a significant technical barrier, at any rate; namely, building their own client.
Meanwhile, when it comes to users adding or not adding the `nostr:` prefix to Nostr URIs, I believe that good design includes the application producing outputs the user expects when they provide a given input that a non-technical user is likely to provide. The exception would be applications that are only built for technical users.
Is it likely that a non-technical user will paste in a Nostr URI without the prefix? Not just likely. It can be seen in countless examples. Indeed, it is the way users will naturally paste the URI, until they have been instructed otherwise.
Can users learn by trial and error and/or assistance from other users that they should add the prefix if they want it to work consistently? Absolutely! But to the degree that they are required to do so is the degree to which the application's UX is not intuitive. Better if an application updates the URI for the user. Better still if the app's UI notifies them of the update and why, with the option to turn off this "URI autocorrect."
No #MinecraftMonday stream today?
Of course there will be! It has just moved to a different time!
I'll be streaming #Minecraft from the Sovereign Craft server today at 3:00pm Pacific Time.
Sovereign Craft is the only Minecraft server with a fully integrated #Bitcoin #Lightning circular economy.
If you'd like to join in with me, go to https://sovereigncraft.com for more details and the server IP.
#Gaming #Gamestr #Streaming #ZapStream
That's only partially true on non-derivatives.
And if it is not a derivative, you may consider he is forced to buy, but also to sell immediately and he gets fiat, and somebody else doing a long bought the full liquidated quantity.
Advanced Nostr Search was able to find a bunch of your posts from around that time-frame:
https://advancednostrsearch.vercel.app/?npub=npub1hspwpfkq7qddnj6h52c03muzgx79l7teeez99n57ys77g4m4vujs3hly9q&toDate=2025-02-08&fromDate=2025-01-19
Didn't find the one you mentiined, though. Thought maybe I'd be able to find it using Primal's advanced search, since they index from most known relays, but no, not there either.
Are you sure you posted it? Maybe it's sitting in your drafts in Amethyst?
Nostr.band's date filter wasn't working for me, so I wasn't able to check there.
As for running your own relay as someone non-technical, there are a few decent options.
1. Citrine, which someone mentioned previously, is a private relay you can run on your Android phone or tablet. It's not available in the Play Store, though. You'll need to install the @nprofile…tdq0.
2. Nostr Relay Tray is a really easy relay to install and run on your desktop PC, made by @nprofile…l3vp. You can find it here: https://github.com/CodyTseng/nostr-relay-tray
3. You can run a cloud-hosted relay with relatively easy configuration options by going to https://relay.tools Just bear in mind that there is a monthly cost for this hosting service.
The protocol doesnt even have that much. 2.1 quadrillion units is what it "understands." It knows nothing about anything called "satoshis" or "bitcoins."
The Bitcoin protocol, the actual code, doesn't even has the concept of a bitcoin.
It only knows Satoshis....
So, was there a proposal to create satoshis as a unit, or didnt it just happen organically?
#bitcoin
#asknostr
GM Nostr! I have a Nostr question, I think this has to do with relays. I had the impression that things I post on here are kind of locked in, there's a network of relays so if one censors me not all do. So my posts stay up until I request deletion and even then it's iffy if it gets completely deleted. And that's my understanding of a big benefit here on Nostr.
I do a lot of psychonaut adventures and one of these I wanted documented. This dream/meditation vision happened Feb. 1, 2025 and to verify that it happened I posted about it here on Feb. 2 and screenshot the post and got the print out of that post notarized to like, doubly prove this happened. You can think it's weird if you'd like but whatever, I'm weird.
But yesterday I scrolled all the way back to confirm that post is still there and it's not, it's gone. I checked again today just in case. None of my posts for the two weeks or so at the end of January and beginning of February are there, only the things I've reposted.
What happened and where did my post go? I still have the video and could post again, but the whole point of posting it then was to provide a proof of timestamp.
It is most likely operator error, I'm in way over my head being here because I'm very bad at tech. But I'm trying my best to learn! If you have any good layperson's sources for understanding this situation it would be much appreciated! 🫂🤞🙌🥰
#asknostr #nostr #relays #dreamstr #psychonaut
In that case, I would highly recommend getting the @nprofile…tdq0 installed from the github link below, then install Amber signer andbuse that for logging into just about any Nostr client on Android.
Coracle can also be installed as an app via the Zapstore, and you can log into it with Amber instead of using a bunker connection.
Let me know if you have any trouble getting it set up. I'll have a tutorial series coming out this week covering the Zapstore, Amber signer, and other great Nostr apps to use together on Android.
GitHub for the Zapstore: https://github.com/zapstore/zapstore/releases
Just download the zapstore.apk file listed in the most recent version there. Your phone will likely require you to allow installation of apps from unknown sources.
I'm using the shabbiest of redmi android phones!
Actually, in this case he had to buy it. When short positions get liquidated, they become forced buyers, because they have to give the same amount of Bitcoin back to whomever they borrowed it from.
It's long positions that someone else bought the Bitcoin the levered long individual was forced to sell.
But remember, somebody else bought it.
What mobile OS are you on? Bunker login can be iffy as it is, and Olas can be even more iffy. 😂
I can probably give you some suggestions for a better experience if I know what device you are using for Coracle.
Zap.stream now has a mobile app, but that is only for watching live streams.
@npub1r0d…fsft recently created @npub1sh0…q2xa, which allows you to go live to zap.stream directly from your phone. Several folks are trying it out and giving him feedback.
Finally logged into coracle.social using bunker address from olas. I thought I had extensions set up but clearly I'm still not Up to speed with how Nostr really works.
And I can't get this note posted on coracle.
At least now I'm half in the land of inbox and outbox done right. Making connections and keeping in touch with newbie Nostr painters and decorators should be easier when I get over this hurdle. Thanks to @nprofile…du26 and @nprofile…x9xx
🐻 Short Rekt: 32.00 BTC on Binance @ $105900.70 💀💀💀💀💀💀💀💀💀💀💀💀💀💀💀💀💀💀💀💀💀💀💀💀💀💀💀💀💀💀💀💀
This degen just lost $3,388,822.40.
https://relay.utxo.one/a031079f0699667252189bee2c617e3eadcaf47ae9e22d3fcfa2d0847464afa6.gif
sorry, bouquet.slidestr.net
Use the browser to navigate to bouquet.blossom.band > log in with extention > your blossom servers will be available for upload, mirroring to whichever ones you wish.
What’s the process for uploading images to Blossom servers via Keychat?
Hoping for full outbox support and Blossom media mirroring, personally.
Does anyone know what all is coming in the next #amethyst update? Just curious, seems like it's gonna be a big one seeing as it's been a while since the last update.
Lilacs are in full bloom round here. They smell AMAZING!
https://relay.brightbolt.net/27907808693a57ec7fe4f7275f6fd36f1f0ac8f2cf8716cb9ead812e3ea50720.jpg https://relay.brightbolt.net/0a9c73959f11f0d75cbcdeee9e471a8bc078a6a993b8c986ff3b938d496bdcc4.jpg
Yup! That would be the culprit! This is something in the works @npub1utx…50e8?
Is this Haven? I know that one doesn’t support the blossom /media endpoint yet, Nostur uses that
Ideas?
https://relay.brightbolt.net/9968bbcc704844106ceb4c558f656c13fcbf52a85d45408680ab43bf59d07c14.jpg
Oh... It would give Primal a run for their money. 😂
My bad, and yes, it would.
Primal is already on Android.
Kind of like you've done with relays, right? You have the relay configuration, and then you can "announce" those relays to create a new 10002. I like that, though I can see it leading to some confusion. 😂
When you just add servers no, that is just for Nostur, but after you add servers there is a separate step “Publish list now” only then will a new kind 10063 be written/published.
Keep leveling up one step at a time.
Not that it matters, as long as I add the same ones, but will Nostur write the servers I add to a new kind 10063?
That's pretty accurate. The only way for your Bitcoin to be gone would be if every node were to be destroyed. Very resilient.
By contrast, your ability to access your Bitcoin can be lost if 1. you lose the ability to communicate with any Bitcoin nodes, or 2. you lose your private key, or someone else obtains your private key. Significantly less resilient, and dependent on how you manage 1 and 2.
might be a bug then, you'll have to manually add the same servers for now
Bitcoin isn't hard, it's just unfamiliar.
One of the hardest concepts for folks to wrap their minds around is that the Bitcoin they own isn't actually IN their wallet. The wallet is just software to allow you to interact with Bitcoin nodes, where your Bitcoin (along with everyone else's) is actually stored.
Even more difficult for folks is that you don't transfer your Bitcoin INTO your hardware wallet to keep it safe. It's still living on the nodes. The hardware wallet is just a glorified password manager designed to store a very strong password very securely, because you can only maintain exclusive right to transact with your Bitcoin if you can keep that password a secret.
Now, that might seem convoluted, and that fiat is way more simple. But then, most folks also have no idea just how convoluted fiat really is, and how little they actually understand about how it works under the hood.
You bet. Just bear in mind that the list is certainly not exhaustive, and that a few of those on the list might now be gone. I know for a fact that blossom.poster.place has been taken down, for instance.
I just used @npub1h0u…rwx8 to upload screenshots of Nostur from my iOS device and other screenshots of Amethyst from my Android device to my Blossom servers, then accessed them from my desktop to include them into a single note on Jumble.
🤯
There's this one: https://blossomservers.com/
I would LOVE to see Nostur come to Android. It would give Amethyst a run for its money.
You can find the follow packs in the "Discover" tab with the rest of the lists from your follows.
No servers listed in Nostur. Was using Nostr.Build option for uploading previously. Haven't added any Blossom servers in Nostur at all, but it hasn't seemed to find my 10063.
Here's what I see in Nostur:
https://relay.brightbolt.net/cbd59b3e140f0716d0feb058ded828f16041dfc2f0dadaf615057fbaae53f92a.png
Here's what Amethyst shows for my 10063:
https://relay.brightbolt.net/939f994285c7b5a7b7d366747266d8153bf4b81ed1bce9f87151fc567bf18937.jpg
And it looks like Nostur is connecting to my outbox relays fine, where my 10063 is stored, aside from nostrplebs, but that relay has been down for a bit.
https://relay.brightbolt.net/223374cf4f184bdbc404a1eb3ab8ef11dde4bc62e429f24db0b4941d1450fa43.png
It should look for your 10063 the first time, if you already have some servers listed in Nostur it won’t look again
Doesn't appear to be detecting my Blossom servers. Is it looking for my kind 10063 list of media servers at all?
#Nostur v1.21 is out
New in this version:
- Support Follow Packs
- Support Blossom servers (uploading and mirroring)
- Post Preview for Picture-only posts
- Audio-only bar
- Drag unread counter anywhere, tap to go to next unread post
- Show media info in iOS Now Playing control center
https://nostur.com/screenshots/nostur-release_.jpg
App Store (Mac, iPad, iPhone): https://nostur.com/appstore
Desktop download (Mac): https://nostur.com/Nostur-1.21.0.dmg
Source code: https://nostur.com/source
As far as Bitcoin's code is concerned, there are no decimals. Sats are the base unit on the blockchain.
The concept that 100,000,000 sats = 1 Bitcoin is a social agreement external to the actual way Bitcoin works.
That said, it is such a longstanding social agreement that it would absolutely cause a lot of confusion and controversy to try and change it now.
Keep the 1 Bitcoin = 100,000,000 sats for the sake of consistency. To change it at this point would make a whole lot of folks scream "I thought Bitcoin didn't have inflation!" because no one actually knows how division works...
It's just custodial Lightning with extra steps. However, those extra steps come with some meaningful privacy gains.
Instead of the custodian keeping track of which account is owed a specific number of sats, the mint just keeps track of the total amount of sats that are owed in the form of tokens generated by the mint. Users of the mint can trade those tokens with anyone willing to accept them completely privately, and if they want to trade with someone who is unwilling or unable to accept the tokens their mint created for them, they can have the mint destroy the tokens and send their trading partner sats via Lightning instead.
Just like any other custodial Lightning service, it is the responsibility of the custodian (the mint) to ensure they have enough sats to back up all the tokens they have generated. They absolutely COULD mint more tokens than they have sats. But then, any Lightning custodian could say they have more sats than they actually do. The rug risk is the same in either case, and may be higher in the case of Cashu mints, since it is so easy for just anyone to run one.
What portion of your stack are you ok with being revealed when you go to spend them?
I guess the perennial debate got kicked back up due to this post from @npub1sg6…f63m:
#nevent1q…z0lw
Go to https://zap.army to enable zaps on Damus.
Hopefully this workaround won't be needed much longer.
You can link to a specific article using the naddr. For instance, `#naddr1qv…ax7w` will link to my recent review of Nostr.Build, like so:
#naddr1qv…ax7w
However, I don't think there is a way to link to a user's list of articles on YakiHonne. Best you can do is link to the profile and then navigate to the articles tab. If you need to link to someone's list of articles, the best way to do so would be to link to their profile on a specific web client that only displays long-form notes, such as habla.news. Something like this:
https://habla.news/p/npub1rsv7kx5avkmq74p85v878e9d5g3w626343xhyg76z5ctfc30kz7q9u4dke
I have a bar of it. I’ll have to give shaving with it a try.
If I had to wager, probably Voyage.
I felt that burn from here!
Seriously, though... I have wondered why Square has dropped the ball so hard on providing a way for merchants to easily accept Bitcoin within their existing POS terminals, and do like OpenNode does, where the merchant can decide what percentage stays as sats, and what percentage gets converted to fiat.
Ah, I see we're no longer arguing about OP_RETURN, and we've returned to the debate about whether the base unit of Bitcoin should be called sats, bits, or bitcoins again. Classic.
Don't get me wrong. The Primal team has put together a great app that can be an enjoyable way of interacting with the Nostr protocol, particularly for less technically inclined users. However, users have to be aware that the ease of use has a tradeoff requiring additional trust.
Now I feel retarded. Well, I better start playing with Nostur or Damus so I know nothing is censored.
Apologies for the mistake — the correct old version is 1.31.13+6370, and the new version is 1.32.4+6380.
I tried updating from version 1.31.13+6730 to the latest version (1.32.4+6380), and encountered the same error in Zapstore, as shown in the screenshot below.
https://image.nostr.build/24940555d2722694067b6f8de082286f3903903293d5ae84474775b1d7d61a8c.jpg
I've been using regular shaving cream for years. Today I finally looked at the label and saw sodium lauryl sulfate and propane. But thanks to @nprofile…2tmg and the circle P I knew just what to do: visit soapminer.com and trade a few precious sats for pine tar tallow soap.
Primal has an option in the relay settings to have your notes written to the caching service first, and then the caching service will forward them to your relays. This is sold as a privacy feature, since those relays won't see your IP address that way, which is true, but it means you are trusting the caching service to actually write to your relays, which doesn't seem to have happened here...
It is somewhat nuanced, but as defined in the protocol NIPs, Nostr clients have certain functions.
1. They make requests to relays for notes the user wants to see that are stored on those relays.
2. They verify that the signatures attached to the notes received from the relays are valid.
3. They display the notes received from the relays to the user, after signatures have been verified.
4. They write the user's notes to the user's selected relays, after obtaining a signature from the user's private key.
Clients may do more than this, but these are the basic functions of a Nostr client you have installed on your device, or that you access via a website.
Primal apps only do number 4.
Items 1 and 2 are entirely handled by Primal's caching service running on their servers, which means number 3 is replaced by displaying notes received from the caching service, and there is no local verification of signatures at all.
Because you aren't reading directly from relays on Primal, their caching service can be used to censor users, replace their actual note with something else, present notes as having been authored by a user that never authored them, etc. And while Primal's caching service is open source, you don't have a way to verify that what is on the GitHub is actually what they are running on their servers.
Local signature verification is probably the most important function of a Nostr client, and Primal apps don't do it, so you are entirely trusting that what their caching service sends to the app is legit.
I always have this problem too.
Yes. Axe the vast majority of those relays. There's no need to write to so many, especially since one thing filter.nostr.wine does for you is blast your note out to several public relays.
Looks like you have relay.primal.net in the list, so it simply must not have ever made it to that relay, as @nprofile…wa92 mentioned, and is likely only available on Primal's caching relay.
See anything here I should change? https://image.nostr.build/65f90821f409a9fef5d3fe3aeba324614f17f5407016d5303bfc02c06e8a492b.jpg
Yeah, my guess is that Primal just assumes you'll be writing to their relay and puts that as the only relay hint on every nevent...
Then, when users decide to write to other relays, the event can't be found using the nevent.
I have that relay on my list and my client still doesn't see it
NWAK is saying it includes relay.primal.net as the only relay hint.
https://relay.brightbolt.net/44103d41758ea509464df8a84ccc44c908acad452d8e7344fd71f44005b144ff.jpg
What do you have set as your relays in Primal, @nprofile…38xm?
nak decode
it doesn't look like primal has any relays in their nevent link
You know of any tools for decoding an nevent to see what relay hints are included, if any?
I'm even connected to the primal relay...
last note I see on bens profile is RIP SUBSTACK before this one
https://cdn.jb55.com/s/372855aec7803ac3.png
Definitely a relay issue. Nadar can't find it, after checking 902 relays.
For whatever reason, even with the nevent, Coracle and Amethyst can't find the note, which suggests that Primal is encoding a relay hint into the nevent that the note is not actually stored on.
The posts I make on @nprofile…5zx8 sometimes don't show up on @nprofile…s8dt...anyone know why?
I assume it's a relay issue #asknostr https://image.nostr.build/a8dd0178fa1debad3c4c9ea7a6a818a7a3549a228a0e96f4d4101e07a65a4a39.jpg https://image.nostr.build/2c5cfa81e966a59b851298a50c2f1ac50acc085e2b48c7681b6b2a44d93b8e1d.jpg
Not really. That's still just option 1, but with a naturalistic explanation for why society arrived at the current state of prevailing opinion. The highest standard of morality remains nothing more binding than maintaining the status quo set by society at large, and that means there isn't really anything binding at all, since the prevailing opinion of society can and has changed. The next non-conformist movement may be temporarily seen as immoral, but come to take the crown as the predominant opinion of society, proving its evolutionary advantage over the opinion it supplanted. Does it then move from being immoral to moral due to having become the prevailing view?
Hogwash, all of it.
The previously mentioned options are definitely good ones!
Please also consider helping me out by picking up one of my #GrowNostr shirts available here:
https://shopstr.store/listing/naddr1qvzqqqrkcgpzpde8f55w86vrhaeqmd955y4rraw8aunzxgxstsj7eyzgntyev2xtqqqqmqzgr3
Or on my Geyser.fund page here:
https://geyser.fund/project/grownostreducation/
I am trying to be a resource for helping others make the most use out of Nostr, and provide quality feedback and suggestions to the devs for improvements that can be made that will make the ecosystem better for us all.
If you'd rather have something more subtle on the front and the larger print on the back, I also have this option:
https://relay.brightbolt.net/dbdda1936fb27e1b21664600e68e277456f05f133d226be33df79f1541720a9c.jpg
Nah, I wanted the nevent. Sorry.
Reason is, asknostr.site can't (and shouldn't) display all event kinds that might have been quoted in the original question, or in some of the responses. If users can snag the nevent and paste it into another client, that client will have a much easier time finding and displaying the note with the relay hints than if they search with just the note ID alone.
I don't think e tags would be the route to go. My understanding of them from NIP-10 is that they are referring to some other event that the event in which they are found is referencing, because it is a reply to the tagged event. Therefore, the relay hint found in an e tag is not a relay hint for the event containing the tag, but a hint for finding the event that is being referenced.
I think if you encode the relay that you received the event from into an nevent, that would be sufficient in most cases.
I still think best practice would be to encode the author's outbox relays if the event can be found on them, since that is what the author has proactively indicated to be where they want their notes to be fetched from, and only encode the relay(s) you received the event from if it isn't available from their outbox relays, or they have no 10002. But, there is the ideal practice, and there is what is practical and straightforward to implement and that will do the job in most circumstances, right? 😂
That's the thing, right? Users have no idea what relays they should choose, or why they might want to choose one relay over another, and there are so many relays out there that it becomes paralyzing to try and figure out which ones are "good."
Nostr.watch is cool, but I'd really like to see a relay selection tool that asks the user some basic, multiple choice questions about what they will be using the relay for, then displays a list of relays that would work for the user's intended purpose, ranking them by a few uptime and availability stats, and indicating if the relay has any restrictions for read or write access, such as paid or PoW relays.
Not a fan of putting orange ₿'s all over myself or my vehicle and going out in public. But I do like things that are less conspicuously related to Bitcoin, but that actual Bitcoiners would recognize.
I also feel like Nostr swag serves a similar function. It's Bitcoin adjacent, but anyone who isn't a Bitcoiner and on Nostr wouldn't know the connection.
How this is handled is described in NIP-B7.
There is no need for the mirrored servers to be referenced in the note itself. Instead, if the media cannot be found at the original server location referenced in the note, and it is clearly a Blossom media URL given the hex string as the file name, the Nostr client will check to see if the author of the note has a kind 10063 list of Blossom servers that they use. If so, it will check to see if the same file is available from any of those servers and render it from there instead.
This is going to depend on what OS you are on. Looking for something to use on Android, iOS, or a desktop OS?
I am also assuming you just mean a client that is a twitter-like experience, too. So no "other stuff" clients.
Android: Amethyst
iOS: Nostur
Desktop: Gossip, or maybe NoteDeck
Web: Coracle.social or Jumble.social
Primal is left out because you stated you wanted a client.
For asknostr.site, I don't think there's going to be much risk that the notes would "belong" somewhere other than the author's outbox relays, so I don't think @npub132n…8cn4 has to worry about that. I definitely see where that would come into play for Flotilla, though.
@npub1gcx…nj5z mentioned that Amethyst encodes the first 3 outbox relays from the author's 10002, if they have one that can be found, or the first 3 relays the app received the note from, if no 10002 can be found.
I wonder if it would be better to do something like, encode the first 3 outbox(write) relays from the author's 10002, so long as they have one AND the note in question can be confirmed to be available from those relays, otherwise encode the first 3 random relays that the app received the note from.
Thanks for the response! This seems to make good sense.
I do wonder, though, if preferring the author's outbox relays, if they have a 10002, would consistently be the right call. Do you check to ensure the note in question does exist on those relays before encoding them in the nevent?
Maybe go for, "If they have a 10002 and the note is confirmed to be found there, then encode the first three outbox relays. If they have no 10002 or the note cannot be found on those relays, then encode the first 3 random relays that sent the event to the app." Would that be a possibility?
#GM which Nostr client is everyone using?
I just wanna pick one and use one…
#asknostr
It depends on where you would expect the note to "belong". In most cases, you would encode the nevent with 3-5 of the author's "write" relays, pulled from their NIP 65 10002 event. In some cases, an event might "belong" elsewhere, for example with NIP 29 communities, where a note is posted to a community relay.
For the examples you mentioned, the second example includes a hint for finding the e-tagged event, not the cited event itself. The hint is also not ideal, because it uses the event author's relay, not one of @nprofile…gqlc's relays (he doesn't have relay.primal.net in his 10002), but it does work because primal happens to have the note in question.
The first example doesn't make any sense, I don't know what `r` tags mean when applied to kind 1. NIP 65 only defines `r` tags applied to kind 10002, not any other event.
All iOS clients will hopefully have zap functionality enabled out of the box soon, given the recent ruling against Apple.
#asknostr #NostrDevs how should a client properly encode an nevent to include the correct relay hints?
#nevent1q…d50m
I know Coracle and Amethyst both provide nevents, so maybe @nprofile…5gcs or @nprofile…pyug can provide some advice/best practice.
Here's what Habla is showing for relays:
https://relay.brightbolt.net/6119ca4540f9153d6243ce8539b3016a22c52621ded10a857e432021d2425d54.jpg
To my memory, I haven't ever had this particular combination of relays, so I don't think it is getting these from an old 10002.
Here's my current 10002:
https://relay.brightbolt.net/a43c107e29d0ecefcc0f91337499c5c9586d36f399c4c95a57ea0374a851bae1.jpg
Android users are allowed to zap natively 👍
@npub1wf4…dgh9 We need your help.
it's using 10002 relays https://github.com/verbiricha/habla.news/blob/5a371f394d070e739b0ef11c92ee09b2de630113/src/components/nostr/Login.tsx#L446 is your relay settings showing an outdated list?
I'm willing to give it a try but have to admit after reading the relevant NIP's (NIP-19, NIP-01, i am confused how to properly encode the NEventId specifically where to get the relay hints.
So take these two notes:
https://njump.me/nevent1qqsr4jknmd7mnj4l0rzmn5yca9yfkea3zh87d62w63r6qkk3590z9hcpz4mhxue69uhhyetvv9ujumt0wd68ytnsw43qyg843y6sunjw2xcu22v2rju8la5xaj8qdcyuae3vyld6avz2lkp7vqjaymlu
https://njump.me/nevent1qqsyksmqer4wqsr6p7eh3xjm6rpljwf8rtdagj0pa4fw6dkts3ry2mspz3mhxue69uhhyetvv9ujuerpd46hxtnfduqs7amnwvaz7tmwdaehgu3wd4hk6q3qqhy8dwfeanhlt4xerekfd5xy3nqcvrdvga02y4ecu4g9cvvhytwqqky86n
First has 'r' tag hints as distinct tags (that's NIP65) -> multiple relays
Second has 'e' tag with the recommended relay -> one relay
Which relay hints am I supposed to use? And also, why does NEvent signing allow for multiple relay urls?
@nprofile…trej @nprofile…tdq0 @nprofile…ucf3, I am unable to update. Seems to think v1.27.2 is a higher version than v1.32.4.
https://relay.brightbolt.net/97f3285731a1718d31711f9bdcd847bcc7a3c31dd30a3835ff83b95700e56e2f.jpg
Check out my full review, it's a good place to start!
#naddr1qq…ntse
If that link doesn't work for you, you can also find it on my website: https://www.nostr-reviews.com
I'm interested in understanding Amber!
Not a medium of exchange, you say?
#nevent1q…9cg5
Good morning!
https://blossom.primal.net/21536b92555cde8e4dd5fd39ea0556292cba8b5865d457063497419b554914d2.mp4
I used to think those on #iOS were second-class citizens when it comes to #Nostr. Then I tried #Nostur on for size and I now wonder if it might be the other way around and #Android users are actually the second-class citizens.
Us Android folks still have some great things that iOS users don’t, though.
#Amber, #Citrine, #Pokey, and the @npub10r8…t2p8, for instance.
Speaking of which, keep an eye out for a tutorial series I will be dropping very soon covering these apps and more for Android users.
I tend to agree, and that's why I have never taken a loan on my Bitcoin. Just explaining why the loans are structured the way they are compared to traditional collateralized loans.
There is no math or situation in the world that could make me think giving up keys to 2 bitcoin for 1 bitcoin worth of fiat is a good deal at 12% Apr with high chance of margin call and liquidation because of volatility. Sorry I think it’s a turd.
Umm... Not really. As someone who recently worked for a fiat lender, our unsecured loans were at 15%, and that is on the low side, because it was a credit union.
Certain collateralized loans had lower rates, but currently only as low as 5.5%-6% for the most qualified borrowers, but you have to remember that the type of collateral most institutions are lending on isn't nearly as volatile as Bitcoin.
There is also the issue that Strike doesn't have permission to print money. They have to incentivize lenders to put up 100% of the amount financed, while most traditional institutions only keep reserves of maybe 10% and they get to create the rest of the money out of thin air. Strike, on the other hand, has to offer their lenders an interest rate that is attractive enough to outweigh the opportunity cost of putting the money somewhere else, because they don't get to fund new money into existence like a bank can.
Well then, it's pretty simple on Primal.
Primal doesn't read from relays at all. It only reads from Primal's centralized caching server.
When you choose relays in the relay settings in Primal, you are only really controlling what relays your notes will be written to. That being the case, choose a large public relay for one of them, and then two other relays for redundancy. These could be relays that are associated with a group you belong to, or that are managed by someone you personally know, or that are just other generic public relays.
https://stats.nostr.band/ lists some of the most popular relays if you scroll to the bottom of the site.
Whichever relays you select in Primal will be considered both read AND write relays in other clients. If you go use another client and find that you are seeing a lot of spam, you may want to change the relays that you are reading from IN THAT CLIENT. Just remember that after you do so, you should never update your relays from Primal ever again, because it will turn them all back to both read and write.
Nope. Happening for me, too:
https://relay.brightbolt.net/0e7d70d76c6262478cd211e920573970b25d6d94ca6a3de6487bb6c7cd53f7c4.jpg
Really not sure what is going on... You can get to the article if you go to Marty's profile on Primal and to the "Reads" section, so there's no reason Primal shouldn't be able to find the article and display a link to it. See below:
https://relay.brightbolt.net/415b3f5cbb776b1a749f7f8e39bd5fbf2345b90d10e3138f181a63deeeddce00.jpg
Maybeits's because I use Graphene?
Ok, strange... Primal handled this Nostr URI to my review of Amber just fine, but didn't do the same with the one I posted above?
https://relay.brightbolt.net/edb1224b0a88c48b65fdc400d8fb1bf56d054dee4dead110a1e2ae78b34629ee.jpg
Welp, it was worth checking. 😂
@nprofile…mexk, if Primal has Long form support, it should probably be able to link to the article with standard Nostr URIs...
https://blossom.primal.net/f987def05b2410a31d4a561f9fda488f25401daeb2e50ddcab2d66b64a346e4a.jpg
Seems to be an issue where Primal isn't sure how to handle bare `naddr` URIs. I wonder if it would have worked if Marty had included `nostr:naddr...` which is the correct way to add a link to a Nostr URI...
Try this one in Primal:
#naddr1qv…stgz
Hi @nprofile…sdla @nprofile…ucqt @nprofile…zyl8 @nprofile…r37e @nprofile…hdyr @nprofile…q6mw @nprofile…tkcs @nprofile…a4w0 @nprofile…rnlp @nprofile…57qq @nprofile…z8ll
Thanks for offering to give me feedback on shosho!
I am looking for 10 or so users to give feedback and I would like to give each user free sats on Zap Stream to go live in return for feedback on the app.
- did it work for you?
- what would make it easier?
- what was missing that you want or need?
Zap Stream charges 5 sats/min so if I zap you say 14,400 sats that's 48 hours worth of live time if you like. Use it for whatever you like.
The app is available on GitHub or Obtainium today. I'll update when Play Store and Zap Store are up.
If this is good for you, DM me and we'll set it up. Nostr DM can be flaky so if I don't reply please try again on this thread.
Thanks for your feedback on shosho!
https://github.com/r0d8lsh0p/shosho-releases
This links doesn't show or open. Troubleshooting steps I've taken:
1. Install latest primal
2. Checked link handling settings
3. Pasted the link directly into Primal search bar
Help?
#asknostr
#nevent1q…fc0s
I don’t know who made asknostr.site but its not me
@npub107j…ncxg, are the relays listed in my settings on Habla separate from my normal relay list and just specific to Habla? Is there a particular reason you're not going with the user's outbox relays found in their 10002?
That's wild... A mobile relay could easily index all the pubkeys the owner would ever care about.
Can't say I blame ya! We need some other options for advanced search, and preferably built into better clients.
How much space does this take up on disk? I imagine it is still relatively small, right?
Would this be something a mobile relay could index, like Citrine? Maybe not index all pubkeys’ 10002s, but an extended WoT, like follows, their follows, and one more layer deep of follows.
We’d end up with something similar to a DHT, but with each mobile relay only indexing the 10002s of those they are likely to want notes from regularly, so they have to make requests to the larger indexers far less often.
Am I crazy here @npub1w4u…0jr5?
For large files, at least.
Client with a native app? Probably Coracle or YakiHonne. Yeah, Voyage is pretty good, too.
Glad you got Amethyst back working again, though.
https://advancednostrsearch.vercel.app is pretty good for finding a specific note from a specific npub, including your own, as already mentioned.
I still find Primal's advanced search to be the best out there, though. It's about the only thing I consistently use Primal for, actually.
@npub1w4u…0jr5, the ability to search through the notes on your Citrine relay might be a handy feature to add.
Yeah, we need a p2p solution and ideally it would be good to have it before nostr.build escalates to a shocking level of censorship
But it seems this is the best we've got for now
Hey @npub1n0s…lahe, asknostr.site is getting REALLY good, sir!
One request, though: Can we have a way to copy a note's event ID somewhere in the UI?
I know I can snag the note ID from the URL, but the event ID is actually more useful, since it contains relay hints.
True, but you are just trading one third-party media host for another that you hope will be more lenient.
That said, I think nostr.build WILL be more lenient, because they aren't getting funded primarily by advertisers. But it's only a matter of time before there are other outside pressures and take-down requests, etc.
Not a thing to be able to write long-form in Amethyst. Though, from Vitor's "yet," it sounds like it might be coming in the future.
I can't imagine writing long-form from my phone, but if you want to do so, my recommendation at this time would be to either use YakiHonne, or use Keychat's built in browser to log into Habla.news.
Trusted 3rd parties are security holes.
You may think you can trust a company (you really can't), but can you trust each and every individual who works for that company?
Of course not. We all know this. Yet we give every personally identifiable detail about ourselves to them because it's required by regulation for them to obtain it in order to provide services we want.
We can bash on Coinbase, but the same is true of Strike, River, and anywhere else other than P2P exchanges like Robosats and Bisq. Dooes anyone really think these companies' employees are any more inherently trustworthy? Nah. They're fallible human beings like the rest, with the same temptations and desires.
Coinbase didn't get hacked.
Coinbase employees sold customer data on the black market.
That's not even social engineering.
#Bitcoin
New project just released: Compass 🧭
For a long time I've wondered how bad things would be if @nprofile…j6hr's wss://purplepag.es relay went down, since it's the only dedicated kind 10002 indexer I'm aware of, and is heavily relied on for bootstrapping user relay selections, which is a key part of keeping nostr decentralized.
So I stood up another one at wss://indexer.coracle.social. Regular users don't need to do anything, but I encourage client developers to add this to your list of relays you check for NIP 65 kind 10002 relay selections.
I've also open-sourced the project at https://github.com/coracle-social/compass so anyone who wants to can run their own.
The project also supports mirroring other indexers via `strfry router`, but I have left that as an opt-in feature. Unless you expect significant load on your indexer, mirroring would only increase the number of unnecessary connections made to other indexers, so please be considerate when setting up mirrors.
Not into a single stream. You will always need to have it piped into a service that combines them before streaming it to zap.stream as I understand how it works.
100% this!
The Bank Secrecy Act is the enemy of personal privacy.
It just creates thousands of honeypots chock full of personal and identifying information for hackers or rogue employees to target.
#nevent1q…z553
fwiw Coinbase is only partially to blame. We need to repeal the Bank Secrecy Act. The government caused this whole mess. h/t @nprofile…ujtq
#nevent1q…pa67
Centralization and KYC/AML laws create treasure troves of data liability for companies and customers. It doesn't end well for either party.
https://blossom.primal.net/d3f0476aeb620ca7a40aaf6ec56f7ea16400ff58a960c921829a15a999b7625c.png
Restart the service, then re-add my NIP-05 usually did the trick.
Hi, please release on @npub10r8…t2p8
#asknostr
I need some quick and short guidance on relay set up and selection.
What did you end up doing? Does it resolve itself? Uninstall and install? Give up on running one?
@nprofile…tacz and @nprofile…t6wa both are my indication that I need to hit the hay when I see their GMs. 😂
When @npub1der…xzpc says good morning and I’m still awake I know I’m up too late, Good Morning Gigi. GN
GM https://blossom.primal.net/53f9a1bfc66a9775af03384e7b8e2baabb6dfded0b890c291786c9535171b6cf.jpg
@nprofile…nq7m we just went live yesterday for the first time and it worked great!
One question though was if it is possible to have both hosts connected at the same time and be visible on the stream? Yesterday we just streamed both of us through a single OBS. Can't the second host login with his Nostr and be invited on the stream as a second speaker, or something like that?
#asknostr
#nevent1q…5uqe
But don’t forget do delete “+” reaction 😁
https://image.nostr.build/ee88d2dd97e4a7b36c53b28124f086fd08ccbc5cacb1a0ffe466eb1446f5e1b3.jpg
Another thing. But to add your wallet address, go to your profile and edit it. Place the Lightning address for your wallet here:
https://i.nostr.build/WJKVGmvs2ml0Fpzw.jpg
Go to your settings, then Reaction Buttons and ad the ⚡️ like so:
https://i.nostr.build/834xLeTkbpbiJNyB.jpg
I am seeing NOSTUR still offers non NWC options. But after choosing your wallet type there is no obvious place where to put your wallet address or a way to link it. Did you figured this out or another thing?
I didn’t know this was possible. Please share?
The animation when you zap, tho… So satisfying!
Honestly it’s my favorite approach 🤣🤣
Ok, figured out how to enable zaps in Nostur. Very sneaky. 😂
🤯 So many settings, features, and options… It’s going to take some time to review this @npub1n0s…lahe.
https://i.nostr.build/ryO1DT33MxjKdzl0.jpg
Nostur on iOS, made by @nprofile…h58f.
I must say, it's absolutely GORGEOUS!
Might just beat out Primal for the most visually stunning Nostr app I have ever used.
Wait… what? I have been missing out on this the whole time!?
https://i.nostr.build/P1j9qhidSo4bQ33V.jpg
Hello from Nostur on iOS.
It's a similar size as my GS25, and that's probably my preferred size for a phone, so long as I have a tablet to pair it with.
Now, I still have to ask, though: wen Android?
How convenient! I just got a refurbished iPhone 12 in the mail today so I can test out and review iOS apps. Mostly got it for Nostr stuff, but I'll happily poke around Maple, too!
I've done a bit of that. It works for short little notes that I only need for a few minutes, but not for anything I need long-term, or need to iterate on over time, like a long-form note. Previous messages sent to yourself get buried in the history pretty quickly.
untype.app is close, but only stores notes locally until you want to publish them. Same with Comet.md.
I want to be able to start working on a note on my desktop, then go to the coffee shop and continue working on it on my laptop, and add screenshots or pictures to it directly from my phone...
Right. And that's where I draw the line. If something can be done on the blockchain in a way that does not interfere with Bitcoin's purpose for existing, which is to have a neutral, digital, permissionless, and uncensorable form of money with a fixed supply, then I don't consider it spam. If it could hinder that primary goal of separating money and state, then I consider it spam and an attack on Bitcoin.
I always had issues with it suddenly deciding to no longer sync my notes for no explicable reason...
Private note-taking app that syncs across devices easily by using a relay to store the notes encrypted by my private key, bonus points if I can set the relay so that it's one that requires AUTH to retrieve the notes, and the notes can be published to my public relays as a long-form, should I decide to do so.
A link/bookmark sharing app that allows users to create, edit, and share bookmark lists. Basically listr.lol, but focused on lists of web URLs, rather than lists of npubs, Nostr notes, or relays.
Spam is determined by the receiver and is subjective.
There are some things to consider when deciding if you think OpenTimestamps on the chain is spam, though.
First, you could consider anything not needed for a financial transaction using Bitcoin the asset to be spam, but then you would have to consider Satoshi himself to have been a spammer.
Second, OpenTimestamps isn't storing jpegs or BRC-20 tokens on the chain. They are storing cryptographic hashes.
Hashes are very small and take up a negligible amount of space on chain. Hence why OpenTimestamps' transactions aren't even filtered by Knots' default limit of 40 bytes.
There is also no way to know what data was used to create a hash by just looking at the hash itself. So it's impossible to say it is referring to anything you would object to and consider spam, unless you already have a copy of the data yourself to be able to recreate the hash.
Finally, transactions containing an OP_RETURN, which is what OpenTimestamps uses for saving their hashes to the chain, create provably unspendable outputs, which means they don't have to be kept in a node's UTXO set. The UTXO set is not stored on the hard drive of the node, but in the node's RAM. Things that bloat the UTXO set are far more concerning.
So, as far as I am concerned, OpenTimestamps are being responsible in their use of blockspace, though it is for non-financial data.
Great news! Looking forward to trying it out!
No. I don't always want to connect to my DM inbox relays. I ONLY want to connect to them for DMs. That is why they aren't in my 10002. I don't want people sending replies to my kind 1 notes to my DM inbox relays. That's not what they are for.
No. Kind 10002 is only public outbox/write relays and public inbox (that is for things like replies and reactions to public posts).
I would not want someone sending a DM to my wot.brightbolt.net, for instance, or relay.brightbolt.net/inbox. Rather, I only want DMs to be sent to inbox.nostr.wine and relay.brightbolt.net/chat, hence why they are a separate list.
10002, as far as I know, has no means of differentiating between which relays are public inboxes and which are a DM inboxes.
Anyone else having issues with their private relay running on Umbrel?
#asknostr #umbrel
DM inbox relays are listed in kind 10050, not 10002.
It's a bug. Users should always be able to configure the relays they read from or write to in a client according to their preferences.
That said, clients should have sensible defaults for users who don't yet have a kind 10002, and they should follow the outbox model for where notes should be read from and written to.
That should be as far as is needed for clients geared toward non-technical users.
Clients that want to support power-users should also include the ability to see a feed from a particular relay or set of relays, even if it is not their usual set of read relays listed in their kind 10002, and they should give users the option to write to a specific relay or set of relays on a post by post basis. If I want to write only to a community relay, I should be able to do so without it being listed in my standard write relays.
Clients that want to appeal to both new users and power users should hide these advanced features by default, but have the option to activate them in the settings with an "Advanced Mode" toggle.
I agree, but I am not sure of how else it would be done without some means of restricting who can add a radio station to the directory, and ensure that it was the station owner.
Best we could do is relay distribution, but that is just infrastructure and has nothing to do with where users are located.
Relays or clients could observe where IP addresses using their services are located, and that would probably be fairly representative, despite the likely use of VPNs by a larger than average proportion of users. I don't know of any relay operators or clients that make such data available, if they are logging it at all, though.
After poking around a bit, I suspect that the Nostr account that posted the radio station to the directory is who receives the zap.
Very true. Nice to see a recognition of God's sovereignty in salvation.
Can't wait to listen! Really liking this short, compact, high-signal format you have going.
Yeah, self custody vs custodial is less important for Lightning. It shouldn't be where you store your life savings anyway, so whether you get rugged shouldn't be a major hit to your financial wellbeing.
And I say that as someone who uses his own node for 99% of his Lightning transactions.
Something tells me that the work they are doing to restore wallet history for all their users is tedious and more-or-less manual.
Gotta say, this is a group I am happy to be numbered among. Solid folks, all.
The state of DMs is pretty atrocious on Nostr...
Not sure what you're using for your Nostr client, @nprofile…6m4s, but for receiving DMs, it's hard to beat 0xChat, since it can receive and send all of the types of DMs used by most other Nostr clients.
Hey, @nprofile…ez5m I got your order (and your payment), you seem to not be getting my DMs - I responded telling you you don't need to resend anything.
Still unable to move my little coinos funds. They are still locked.
It ain't much but it's honest work 😐
Please @nprofile…0pev fix this issue with my fav wallet for
#zap #Nostr frens
#ThankYou
https://image.nostr.build/faf93885a50f9c0ddcc2e284e521acbd5a487fb999f99601542a52544be35b1b.gif
So basically 3/4 of all LN Bitcoiners are using custodians. Awesome...
#nevent1q…xss8
Gossip by @nprofile…nq40 is a good one.
Honestly, though, I just stick with web clients on desktop.
Does anyone know a good desktop client for nostr on Ubuntu?
#asknostr
There's a lot of factors that go into this. However, assuming you don't care about your high debt utilization ratio tanking your credit, because you have no need to go deeper into debt, and those minimum payments are not preventing you from stacking more sats, the bullish position would be to just make the minimum payments on your debt and stack sats with the funds you would have put toward paying it down faster. The purchasing power of your Bitcoin will very likely outpace the interest rate on your debt.
Every dollar that is not spent on buying Bitcoin is an opportunity cost. You should only spend dollars on things you absolutely have to, or that will significantly increase your quality of life. Otherwise, you're leaving sats on the table, and they will only get more expensive over time.
Hey @npub1h2q…w8ch how come some of my sats have been locked? Also I
Minted some ecash and it showed an error and won’t let me see the code, but it took the sats.
https://image.nostr.build/cb31bf46790f7744292b08eb469fa85da4c8f8b812ae239449ac760234f2ed35.jpg
From my node to yours: ⚡💜⚡
When you #zap me, this is where your sats go. @npub1hxf…5p6t 💜⚡️🤙
GN 🌙 PV 🫂
https://i.nostr.build/6aF5P5hbTSXrdJBY.jpg
No. Not as far as web-of-trust works in Coracle.
The way Coracle scores for web-of-trust is based on how many of the npubs you follow who also follow that particular npub (adding positively to the score) vs the number of npubs you follow who have reported or muted that particular npub (taking away from the score).
Meanwhile, an npub will be considered part of your "Network" so long as at least one npub you follow also follows them, regardless of their overall WoT score.
You can then further narrow down who will be included in the feed by increasing Coracle's global WoT filter.
Soo is this effectively the equivalent of "Web of trust" score of 1?
Aaaaand zapped you via NWC on LNBits!
Going to roll with this for a while and when I am sure it is working well, I might just switch everything over from Alby Hub.
Turns out the relays I tried were also part of the issue. Going to need to figure that one out... Is wss://nwc.nostr1.com just a public NWC relay you're running via your relay.tools for anyone to use?
Welp... I can transfer back and forth between other LNBits wallets without an issue using NWC on both... Just can't transact with my Alby Hub wallet...
Affirmative, second order only
Yeah... Apparently LNBits wasn't properly connecting to LND. That was my issue. Got that resolved and now setting up connections is working fine.
Wasn't able to transfer from my Alby Hub wallet to my LNBits test wallet, but was able to transfer from Phoenix... More testing is in order.
Same behavior in Brave.
Happy to say that @npub1h0u…rwx8 works with dark mode fine, though.
For some reason, dark mode isn't working on Firefox, though...
There really are only two options:
1. Right and wrong are just social constructs created to preserve a status quo. In which case, there is no moral imperative requiring anyone to follow what is thought to be "right" by dint of prevailing opinion, nor is there any firm foundation for calling out the majority opinion when it is "wrong." By definition, there is no outside standard to measure the prevailing opinion by and determine whether it aligns with it or falls short.
2. Right and wrong are revealed by a divine authority to whom we must give an account. Only under this understanding can there be any grounds for calling society out when the prevailing opinion is wrong, because it is the only understanding that provides a standard that originates from a higher authority than society itself.
@npub1jlr…ynqn can correct me if I am wrong on this one. I believe "network" is just one step beyond the npubs you actively follow. In other words, it is the npubs your follows follow.
try wss://nwc.nostr1.com
the plugin, in the past, and now too maybe, can use an additional nostr relay plugin. i dont use that, but both ways can work. lnbits logs shed a lot of light
Dude... This is now my preferred way to browse for questions to answer.
Amethyst is an option. If you just want kind 20 like Olas, you can also use Coracle and create a custom feed. Though, admittedly, Coracle can be ridiculously slow to load media...
NICE! I'll go check it out!
I think I got it set up, but it won't connect... I keep getting this message even though I have tried a couple separate relays that should accept NWC note kinds:
https://relay.brightbolt.net/eae68f3fdcfdf6dc947298091fd0795efe0988f89344a0dfce1ffcb9541a9883.jpg
this is the fork thats supposed to be 1.0 compat. you can add it in the lnbits gui repo manager
LOL... Wow... It's there. Hold please while I go flog myself and then try and set it up.
Probably, if I can ever figure it out. No extension for NWC is available within LNBits that I can find... Unless it's in an alternative extension directory that I need to add?
NWC on LNBits has the potential to be WAY more flexible than on Alby Hub. Set up separate wallets in LNBits and each wallet can have separate connection strings, with separate budgets for each app you connect it to... Separate permissions, too... Night and day difference compared to only having one connection string per Friends & Family wallet in Alby Hub...
But of course, it can't be simple to set up...
Supposedly available as of version 1.0 for LNBits, but seems to be missing. They wrote about it here when they announced version 1.0:
https://news.lnbits.com/news/lnbits-v100
Then they released this article today:
https://news.lnbits.com/news/lnbits-with-nostr-wallet-connect-nwc
But not seeing any "NWCProvider" extension anywhere to enable... Not available for Start9, maybe? I see Start9 isn't mentioned in the article.
@npub10ef…aeh3 or anyone else with experience: Version 1.0 supposedly has NWC support. How does one go about setting that up?
There's no NWC extension in the list of available extensions.
#asknostr
#asknostr What exactly is the "Network" filter in #coracle? Is that like, 2nd or 3rd order connections?
SERVICE UPDATE:
We have just re-enabled withdrawals for all user accounts that do not appear to have activity in our server logs during the time that we are missing data for (2am May 9 to 4pm May 10 UTC).
About 1100 accounts are still unable to withdraw funds that were deposited before May 10 at 4pm UTC but should be able to withdraw any funds that were deposited after that time.
We are continuing to work on shortening that list, correcting balances and missing payments, and restoring full access to everyone.
Thank you for your continued patience and understanding!
This makes morality no more significant than "group think," which strips it of any reason to be moral, other than to preserve the status quo.
Right and wrong, good and evil, righteousness and sin are what they are, even if the prevailing opinion is entirely running counter to them.
I'm working on the Gitcitadel.com/repos pages, to implement the same markup parser, so that it all looks pretty here, too.
Reminds me of Voxer, but public.
My daughter, @nprofile…u76s, is now officially able to drive herself to all her extracurricular activities!
My evenings just got more open!
Following fake accounts intentionally messes with web-of-trust. Probably not enough to make much difference, but it would still be better to use a separate list for this purpose.
I haven't used iris in some time. Going to have to go check it out again.
I agree. iris.to client has this feature. I hope jumble.social implement same thing.
@npub1syj…f6wl
Just a reminder that it is important for Nostr clients to make it visually obvious which npub is likely the impostor.
Impostor Derek:
https://relay.brightbolt.net/4d7cb88e92c90e088938b41a9e62f64f6fc071f6c92a9f0f956dbb4e7d877235.jpgjpg
Real Derek:
https://relay.brightbolt.net/7b14c82eeb4be198c2f12b7c68760447e9ceb9b0c41b06c14107c8771211126c.jpgjpg
#nevent1q…5ln0
Mining decentralization is a massive issue, and no one has done as much to address it as @nprofile…ckyu, hands down.
Imagine if pools didn't even construct block templates at all, but were just there for coordinating reward splits.
Miners would actually be in control of what went into a block again, and they wouldn't just be rented hashers.
Anyone who wanted to get non-standard transactions into a block would have a much harder time, since pools would no longer be the decision makers with massive amounts of hash available to make it happen.
#nevent1q…egrm
Dang, there’s a lot to chew on there!
I think you are probably correct that Cashu is the future for zaps. However, there are a few things that have me hesitant about it.
First, Cashu is by its very nature custodial only, unless you are running your own mint, and there are far less folks running their own mint than there are running their own lightning node. If Nostr goes the direction of eCash exclusively for zaps, it will mean that almost all users have to trust a custodian. Yes, the vast majority already are doing so, but there are still plenty of us out there who zap from our own nodes, and unless we also want to learn how to run our own mint, we’re going to have a meaningful percentage of move over to using custodians instead.
Next, I am not a fan of the idea that someone can receive funds without any intentional setup of a wallet to receive them to, particularly at a time when not all Nostr clients have Nostr wallets built into them so that the user sees within the app’s UI where they can go to retrieve those funds. The user should always be in control of how they receive funds. We probably need something like a “Preferred Payment Method” note kind that flags whether or not the user wants to accept Cashu or Lightning, and if the note can’t be found, clients should default to Lightning if they have a Lightning address in their kind 0, or treat them as unzappable if they have neither.
It’s funny that you mentioned you have found NWC to be unreliable. I have actually found NIP-60 wallets, such as Nutsack, Honeypot, and the one built into Olas to be unreliable. I have yet to have a NIP-60 wallet that is built into a client work, so I have never had the pleasure of trying out zapping with it. Now, that could entirely be due to the fact that it was Olas, a Pablo app, that I was trying it out with, and Olas is just broken… I would definitely be willing to check out other clients that have NIP-60 wallets if you have suggestions.
Also, there is nothing intrinsically tying eCash to Bitcoin’s fixed supply. Now, you can say this is an issue for custodial Lightning as well, but there is an important difference, especially in the context of zaps. Whenever a zap happens on Lightning, the custodian has to prove they actually have the sats, because they will be routed to the receiving wallet via payment channels, unless the receiver happens to be using the same custodian. With Cashu, as I understand it, the receiver just gets tokens from the sender’s mint, regardless of whether they have a trust relationship with that mint or not, and if they want to redeem them over to a different mint, that is a separate transaction, even if it is done automatically. So they could end up receiving eCash as a zap, and when they go to redeem it, they can’t, because the sender’s mint was malicious and had no underlying sats. Unless there is a way to block receipt of eCash from mints you don’t trust that I am unaware of?
Outside of that, I LOVE the idea of Nostr wallets built on Cashu protocol, where the tokens are stored on your relays and you can just redeem them out to your Lightning wallet once you start building up a balance. Multi-mint payments are exciting. Web-of-trust based mint recommendations is exciting. I am generally bullish about Cashu, with the exception of my above reservations.
Now to work through what you wrote…
“The problem with NWC is that it’s quite unreliable in my experience and sluggish.”
Ironically, the only NWC connection that is currently unreliable and sluggish for me is when using Minibits with NWC. Outside of that, it works as quickly as any other Lightning transaction, and my only downtime has been when either my own node or the relay for passing NWC messages back and forth is down. Now, this could definitely be something Cashu tokens saved to multiple relays can address, since one relay being down wouldn’t affect my ability to zap or receive zaps.
“...the UX of copy pasting random strings all over the place is also a hurdle.”
I agree. I don’t think it’s as much of a hurdle as it’s made out to be, given that copy/pasting isn’t exactly hard to do, but the UX could definitely be improved. Alby Hub’s scanning of a QR code to establish the connection is really nice, and more NWC enabled apps need to support that option.
“...payments are much faster and more reliable, alas the balance could be unreliable…”
Tradeoffs, right? I absolutely see why Cashu payments would be faster. No need to calculate routing paths and such. Just find out the receiver’s inbox relays and save the token there, encrypted to their npub. But balance information is going to be an interesting one to try and solve for, with a single user likely having received tokens from several different mints, and they may or may not all be saved to the same relays… Users will also need to be careful about changing relays, since they will need to make sure they migrate their tokens to the new relay they want to use first. Hopefully that will be made clear in a Nostr client’s UI, along with some built-in tools for doing so.
“...you don’t need to pray to a node to publish a zap receipt…”
YES! Absolutely this is an improvement on the current way things are done with Lightning receipts! Since the transaction is happening ON the relays, Nostr clients can see that the payment has taken place, whereas with Lightning, the transaction itself is happening outside of the Nostr ecosystem, and therefore it relies on the node to confirm the payment was received.
“When you as an outside observer want to calculate reputation of a pubkey and pull in zaps…”
You might need to break this down further for me. Are you talking about using zaps as a method for calculating the reputation of a particular Nostr user, based on the reputability of the Cashu mints they are using?
“The way I see rn is that NWC has been a good interim solution but there is more potential in Cashu…”
This is probably true. And yes, the reason I am so excited about NWC is probably because I run a node, and it so easily resolved my remote connection issues. Couldn’t stand using Tor and having to wait and hope that Zeus would be able to connect so I could see my balance and make a transaction…
Cashu absolutely does have a lot of potential, and I love to see the new developments and improvements coming along. I don’t think we’re ready for it to take over fully, even on Nostr, but it’s getting there.
I see NWC as an interesting option for setting up recurring payments, with a budget, too. For instance, if you have a service provider that you want to be able to pull a payment every month, you can give them a NWC connection that you maintain the ability to revoke at any time, and with a budget of exactly the monthly payment, so they can’t increase the price on you without your permission. So, NWC could still be useful outside of a Nostr context, and even paired with a Cashu wallet, such as Minibits.
Imagine a NIP-60 Cashu wallet app that had NWC for interacting with the broader Lightning ecosystem as well. In fact, I don’t see why NWC couldn’t be modified for reoccurring payments with eCash, too, so the wallet would send via Lightning if the receiver prefers, or send eCash instead if the receiver doesn’t mind having tokens from the sender’s mint(s). NWC is really just a means for messages to be passed between two apps, with the one who created the connection dictating the terms of what sorts of messages are permitted and what information they can or must contain. Heck, a user could have a NIP-60 wallet that supports creation of NWC connections that they use to connect it to an Alby account so they also receive Lightning payments to the same wallet, and they can use the Alby extension to make payments from their NIP-60 wallet to an online retailer that accepts Lightning, but not eCash.
So, I think NWC and NIP-60 wallets can absolutely coexist and complement one another.
I think it's critical to understand the underlying issue that affects everything about the discussion around spam and the op_return limit.
Because, imo, its the most important issue in Bitcoin right now and very few are doing anything concrete about it.
Read 881 - The Problem is Deeper Than Spam...
https://open.spotify.com/episode/7rSTvQcsmu0W4prtR9f2mY
Trust me, I absolutely feel where you are coming from. It's always a bummer to find out that hardware you already have running doesn't have an easy to run version of software you want to try out. Been there way too often.
@nprofile…q7y6 any plans for Alby Hub to be packaged for MyNode like it is for Umbrel or StartOS? Or maybe there is a way to side-load it?
I am not familiar with MyNode. Is the Nostr Wallet Connect app on its own available for that node implementation? If so, that could be a path forward for you. Just doesn't allow for separate sub-wallets like Alby Hub does, so it will have access to your full local Lightning balance. Make sure you set a reasonable budget.
Another option is to use LNBits and the NWC extension that has been created for it. You will need to log into your LNBits as super admin and add the registry found in the below GitHub repo, though, since the extension is not yet available in the main LNBits extension registry.
https://github.com/riccardobl/nwcprovider?tab=readme-ov-file
Aside from the above options, since you're already running a node and there is no point in tying up a bunch more liquidity just so you can zap on Nostr, it might be worth your while to just use a custodial wallet for zapping unless and until there is a version of Alby Hub packaged for MyNode. My recommendation here would be @nprofile…t9p8 . Or if you want to try out an eCash wallet, you could go with @nprofile…d4vz . Both support Nostr Wallet Connect.
NWC is like a superpower.
I think there are still some clients that will open up a lightning wallet app you have installed on your phone if you don't have any NWC connection set up, or they will display an invoice that you can copy/paste to your wallet of choice, but most have moved to using NWC for good reason.
Did a write-up on how NWC works and how it is not just useful for Nostr, but is revolutionizing the way we use Lightning in general. You can read it here:
#naddr1qq…jscs
If you don't have a long-form client to read it on, you can also read it here:
https://www.nostr-reviews.com/post/965f1ea6bc/
I've bought stuff on Shopstr using fiat...
I use my fiat balance in Strike to pay the invoice. I spend fiat, and the merchant receives sats. Win/win.
Now, you probably meant using a debit or credit card for payment. Yeah... Not gonna happen. Stop and think about what would be required for that to take place. Either every merchant would need to have their own account set up with a payment processor for accepting cards, or Shopstr would need to have a centralized payment processing solution, and they would need to KYC the merchants AND the buyers for every transaction.
That is the exact opposite direction from what we want to accomplish with Nostr.
Shopstr shouldn't have to police who the merchants and buyers are at all, because it's all just Nostr notes pulled from relays, which can be equally pulled up in any other marketplace app, such as Amethyst's marketplace or cypher.space.
Remember, the apps you use to access content on Nostr, including marketplace listings, are little more than glorified user interfaces that just display and allow you to interact with content that is stored on thousands of different relays. They can facilitate very little outside of what the Nostr protocol understands, or else it will break other Nostr clients that interact with the same data.
Lending always involves risk to the lender. That is part of why there is an interest rate and why those who have a history of not paying back their debt, or making their payments late, tend to end up with higher interest rates, if the lender is willing to take the risk lending to them at all.
Would definitely be up for giving it a try.
My own self-hosted Alby Hub.
H/T to @npub18pu…a699 for @npub1z0l…8ldk!
Very useful little Nostrized Jitsi implementation.
So, it seems not all clients are putting default bookmarks on the same note kind...
Clients should be saving bookmarks to your standard kind 10003 list. However, there are a lot of clients that use other event kinds, such as the deprecated kind 30001.
You can use listr.lol to manage your various bookmark lists. Once you can identify which one is your kind 10003 (Mine was titled "Bookmarks") you can add the content from your other "bookmark" lists that are likely kind 30001 lists.
Also, any friends you have on iOS can use Keychat, then navigate to Coracle.social within the built-in web browser.
For Android, Coracle has a native app. Solid client all around, too, not just regarding outbox.
OSX I would just use Coracle on web. Not sure what clients are available for Mac specifically. Maybe Gossip? @npub1acg…p35c
loans on bitcoin inherently have risk but they can also be incredibly useful
for those that want one, i am confident strike will provide the best and most responsible experience
- secure custody
- dollars instantly in your bank account
- easy and clear ux
- competitive rates
their in-app flow is very clear about risk and liquidation levels, with a high reserve requirement, to reduce loan loss
skepticism is healthy but their product is new and will become better quickly, feedback is helpful
soon:
- roll overs
- lower rates
- proof of reserves
disclosure: ten31 is strike's lead investor and jack is a brother
What OS are you using? Android, iOS, a desktop OS?
Alright, so it looks like Yakihonne does the outbox side, but not necessarily the inbox side.
Inbox is a similar idea, but instead of looking at the user's relay list to decide which relays to pull their notes from it is looking at their list to determine where to write replies to that they will see.
If you are using a client that has properly implemented both, it will pull the notes written by the users you follow from their outbox relays; when you write your own original post, it will be written to your outbox relays; and when you are writing a reply to someone else's post, it will be written to their inbox relays.
Clients that have included both, from @npub1zaf…26k5's GitHub repo, include #Coracle (web and Android), #Nostur (iOS), #Voyage (Android), #Gossip (Desktop), and #Nosotros (web and desktop).
@npub1zaf…26k5 do you have an interoperability tracker for outbox model?
Ah, except if a relay alters the note after you've signed it, the signature is no longer valid, because your signature is based on the content of the note. If a relay changes the content, then Nostr clients won't display the note, since they only accept notes with valid signatures from the relays.
This is also why it is MASSIVELY important that relays and clients are run by separate entities. If you are reading from a relay that is owned by the same entity that created your Nostr client, they can absolutely alter your note and code their client to ignore the fact that the signature is now invalid.
Best approach is outbox model, then it doesn't matter what relays they post to, but not all clients are supporting it, and those that do aren't always correct in how they implemented it.
Outbox model works like this:
Every user has a relay list created when they create their Nostr identity. This list includes the relays they state they will be writing to and the relays they state they will be reading from, which may or may not be the same relays. This list is shared far and wide by the Nostr client, to as many public relays as possible, this way it will be easy to find by other Nostr clients.
When another user follows the user from the paragraph above, their Nostr client will look for that user's relay list and pull their notes from that user's write relays, regardless of whether the user who followed them shares any of their relays.
Things don't always get handled that way by Nostr clients, though. Hoping to see more widespread support and consistent implementation of this model as time goes on, though.
Fiat = Governments get to print their own money on a whim.
Crypto = Everyone gets to print their own money on a whim.
Bitcoin = No one gets to print their own money on a whim.
Which do you think will have the best chance of storing your productive time and energy into the future?
Not sure if any of the current lists supported on listr.lol would allow for saving arbitrary information in a list item. Might need a new kind and a new client that supports it.
#MinecraftMonday again already? Yes, yes it is!
https://i.nostr.build/uk7csqwnOT4F8uz0.jpg
I'll be going live on the Sovereign Craft server today at 11:00am Pacific time, and will probably be hanging out for 4 hours getting up to whatever shenanigans take our fancy.
You can join the stream chat at https://zap.stream/ or on #Amethyst, or on the recently released Android app for zap.stream, available in the @npub10r8…t2p8.
Sovereign Craft is the only #Bitcoin #Lightning integrated #Minecraft server that provides all players with a wallet, a Lightning address, and also allows them to set up a `@minecraftstr.com` #Nostr address to use as your NIP-05.
#Minecraftstr #Gaming #Gamestr #ZapStream #Monday
Who was the channel with? Has your node been offline recently? Channel partners will tend to close channels when their channel partner has been offline, is unreliable, or the channel isn't used often enough to justify keeping it open. Also, if it is a paid channel, those often have a set period of time that the channel partner has agreed to keep it open.
Either way, LND didn't just axe the channel. Your channel partner did.
There's a couple ways.
If you are on Android, you can run Citrine and tell it to "Download your events" which will result in the app reaching out to a bunch of other relays on the network looking for any posts that you have made and download them locally to Citrine's database. Then you can export them by selecting "Export database" and do whatever you want with them.
You can also use a web tool: https://nostrsync.vercel.app/
This will find all your notes, download them locally to your PC, and then broadcast them to major relays on the network.
That said, when we talk about your data belonging to you, we mean that anything you post has been cryptographically signed by your private key, and it cannot be altered without it being obvious to every Nostr client that the post's content had been changed. Likewise, no one can post a fake note saying that it was you who posted it, because all posts require a signature, and their signature won't match, since they don't have your private key.
Who "owns" your data in the sense of where it is stored depends on whether you run your own relay, or you just use someone else's relay.
It's a similar concept to Bitcoin, actually. So long as you hold the private key that can be used to transact your Bitcoin, then you are the owner, regardless of whether you also run a Bitcoin node. However, if you don't run a node, you have to use someone else's node to transact. Same thing applies to use of private keys and relays on Nostr. The difference is, unlike Bitcoin where all nodes must store all transactions done on-chain, Nostr relays have no such requirement. A relay operator could choose to restrict the use of their relay to just their own notes, just notes from a circle of friends, just notes from users who have paid them, or any other rule they want to set about what sorts of notes their relay will accept.
Not sure. You'd probably have to ask Luke. I just know it long predates the jpegs and BRC 20 nonsense.
What were the original goals of Knots then?
#asknostr
Very close. Miners must be connected to a node in some way; either the miner's own node or via a pool that runs a node, or via a pool that gets block templates from another pool that runs a node.
The reason for this is because each node has a mempool, which is just a list of transactions that are waiting to be included in a block. From this pool of waiting transactions a block template is constructed that includes the transactions the mining pool or the individual miner using their own node would like to include in the block, if they find a valid hash that will allow them to broadcast their block for inclusion on the chain to all nodes in the network.
Technically, solo-mining is when you as a miner use your own node's mempool to create the block templates for your ASICs to hash. If you are getting your block templates from a mining pool, even a "solo" pool, you aren't really solo-mining. Rather, you are lottery-mining.
Even if you aren't a miner, your node's mempool settings can have an effect on the transactions that get mined, because your node helps to relay transactions to other nodes on the network, including the nodes that mining pools are using for creating transactions. If enough nodes on the network aren't relaying transactions with arbitrary data in them, it will be less likely that those transactions will make it into the mempools used for block construction by mining pools or individual miners who construct their own blocks. The more difficult this is for those who want to put non-monetary transactions onto the chain, the more they will have to pay in fees to incentivise miners to include their transactions, which disincentivises such transactions.
Given the current state of the mempools, an argument could be made that such transactions have already been disincentivised, for now.
Guy Swann had a very balanced take on the whole debate here: https://fountain.fm/episode/twR9XdpCO0yoMTSQUGPj
Gist of it is that the reasoning behind removing the datacarrier limit for OP_ RETURN is sound, but the devs should not have been surprised that it would be controversial, and Core has generally avoided making controversial updates. It probably also wouldn't have been nearly such a big deal if they left it configurable, but their plan is currently to remove the option to configure it.
Meanwhile, Knots is keeping it configurable. You can run knots with no limit on the datacarrier size if you want, or you can leave it at the default 40 bytes, or you can set it to Core's current default. Point is, you have options with Knots that Core is planning to take away.
One of the arguments made by the folks supporting the change to Core is that OP_RETURN is a far better place for arbitrary data to be stored, because it can safely be pruned by nodes, so they don't have to store that data. However, there is no financial incentive for the jpeg and BRC 20 folks to put their data into OP_ RETURN, because they are currently putting it into the witness data, where they get a significant fee discount. Even if the datacarrier limit is removed, there is absolutely no reason to believe the degens will forego that free discount and start placing their garbage in OP_ RETURN instead.
Bro has 3 whole followers...
Even if that or the "crypto" talk wasn't a dead giveaway, we have great impersonator detection tools available to us these days, such as Coracle's web-of-trust search or npub.world's pagerank search. Needs to be built into more clients, though.
Self custody lightning is definitely rough. That said, if you think it's bad, you should try self custody digital payments with fiat. Makes it look like a cake-walk.
Nextcloud
Jellyfin
Audiobookshelf
Bitcoin/Lightning Node
One nice thing about @npub1h2q…w8ch is that you can set up auto-transfer out to another Lightning wallet. So, if you are hesitant to have it received to a custodial wallet, especially after their recent outage, you can mitigate that risk by having it forward your sats to your current Lightning wallet whenever it hits, say, 1000 sats.
But yes, you can absolutely start out with just your on-chain address and add Lightning payout later.
Custodial: @npub1h2q…w8ch has BOLT-12
Non-Custodial: Phoenix Wallet, but note that it doesn't work with @npub1qtv…7dze for Lightning payouts, since it doesn't allow adding comments to the invoice.
The other obvious option is CLN running on your own node.
Some Nostr clients allow for a wide range of reactions. Not just a ❤️. Others only give you one choice.
Used to be, the clients that only gave you one choice didn't even display the other reactions. Thankfully they now at least show you the other reactions, too.
Great group of sat stackers out here in the inland NW!
#nevent1q…l9fz
Got to the "I don't want to lose my mother" stage in my early 30s, unfortunately... Now in the "I would give up everything to have my mother here with me" stage for the last 8+ years.
Miss her dearly.
Don't take a single day of your mother's presence in your life for granted.
#nevent1q…smxz
People seem to assume that they need to follow the bot in their main follow list, and therefore it clogs up their main feed. I just added it to a separate named follow list, along with a couple other Bitcoin bots and switch over to a feed built from that list whenever I want to see them.
This is easy to do with Listr.lol + Amethyst or Coracle. Pretty sure Nostur supports list-based feeds on iOS, too.
5 years old - Mom, I love you.
12 years old - Mom, I can't stand you.
16 years old - My mother is very annoying.
18 years old - I'm leaving this house.
25 years old - Mom, you were right.
30 years old - I want to go to my mom's house.
50 years old - I don't want to lose my mother.
70 years old - I would give up everything to have my mom here with me.
You only have one mom. Take care of her while she's still alive.
Happy Mother’s Day ❤️
https://image.nostr.build/64613a3db5304527f5991976aa9311ee67424c7b094c5632bf08b8fcd7868f09.jpg
Haha, Jumble is gradually phasing out support for kind 20
That's the idea. I've set wss://lockbox.fiatjaf.com/ as my only outbox relay now and clients should display my notes to everybody who follows me, unless I'm missing something.
So far I've seen only Gossip and Coracle do that as expected.
Should I modify @nprofile…6qqk to only post massive losses?
Right now it posts any loss over 1 BTC, and I get a lot of feedback that it posts too much
But I also get a lot of feedback that people like it as is
Nostr.build allows uploads of 100MB for free. They also allow paid plans. I believe Primal's blossom server is entirely free. Probably a similar file size cap.
Check out my full review of nostr.build here: #naddr1qv…ax7w
Thinking about getting a refurbished iPhone so I can do reviews and tutorials for iOS Nostr apps, and assist folks who are over on iOS when they ask for help. Which generation of iPhone would y'all recommend? Trying to stay under $300 if I can.
#asknostr
I'll definitely give it another go, next time.
The first time I tried using Zapadd was on my desktop browser and made the mistake of trying to send 1000 zaps. Crashed my PC with 1000 signature requests popping up for approval from my browser signer all at once. 😂
So I popped over to Keychat thinking it wouldn't have that issue, but the invoice wouldn't pop up for me.
Then I had the brilliant idea to do a small campaign on Zapadd of just 10 zaps, tell my browser extension to always approve zap signing requests for Zapadd, and then do the 1000 zap campaign. That worked.
Next time, I'll try and do it through Keychat and report back if I have any issues.
True. I do switch to a few relay feeds, though. Just never paid attention to the Bookmarks option. 😂
This shows that people usually only check their following feed.
I tested the invoice popup — it works. I’m hoping there can be an “Open in a Bitcoin wallet” button below the invoice, so it can directly trigger the Keychat wallet for payment without needing to copy and paste the invoice manually.
https://image.nostr.build/7937519b367fd4d8d3d373b5c35229815beb17096e829eb9b76ba984cb5574b0.jpg
https://image.nostr.build/3975d3805ddf7a1073cf0c4b510c32f0bba42951f85f8213daef4e782c239396.jpg
Ironically, I just tried this via @npub1h0u…rwx8 and the invoice never popped up.
I get it brother, and I forgive you. Figured something must have had your hackles up, so I decided it wasn't worth responding anymore.
Hope all is well, and since your bride let the cat out of the bag, congratulations on the little one on the way!
Dikaios1517, I wanted to write to apologize for my overactive and accusative and contentious way I interacted with you. You didn't deserve my negative because you were only trying to help me. I let negative stuff going on with me spill over to how I interacted with you, and that's very not okay and I won't let it happen again. Will you forgive me?
Bahahaha! Not where I would have looked for them, but I do feel silly that I couldn't find it.
Not yet. @nprofile…s9v7 has Yeti in the works.
Looking good! One thing I came across is that full screen is cropping out some of the view on my Galaxy S25.
Here's portrait orientation vs full screen while watching @nprofile…5wwg this morning:
https://relay.brightbolt.net/6ad502c1307b8936db190e28810fd19ec53d73533579dd80d6a1395bb3116a03.jpg
https://relay.brightbolt.net/e5718cb48361c138d117b095dba32e72106ad374b226db10077eae1f2743e679.jpg
Is there something like amber on ios?
👀
https://image.nostr.build/893218aa8de7d394b32988a58da0b7db9dcbfd61a384bd7340d4abecd6b361f7.jpg
Not dumb at all. I don't think there is a way to see the bookmarks from within Jumble. I had to pop over to listr.lol to see what I had bookmarked. 😂
this is a dumb questions, but where do i find my bookmarked notes in jumble.social ? i see that i can bookmark notes, but now i cant find a way to view bookmarked notes.
#asknostr
In Coinos, go to the settings cog.
https://relay.brightbolt.net/a347f269d1e127026375acae3154ea0405bc99979adf5a8caf8098357d54c546.jpg
Select "New Connection."
https://relay.brightbolt.net/3071ca3e9eeb5a1ecc4bb7f8678cef1b8b1605546ea9d5e125c9494e5c35c8d1.jpg
Give it a name, like which Nostr app you are connecting to. You can also set a budget and how often it renews. Then scroll down and click "Submit." No need to mess with any of the other options.
https://relay.brightbolt.net/04dd58ade7889eb339bd01c328902cf64ba33a848329b45844d6653727daca3c.jpg
Now you should have a connection set up that looks something like the one below. Select "Copy NWC."
https://relay.brightbolt.net/be3a4fe30f247bd9d079379310593a465253414478b89dd3879bb542b5c86cd0.jpg
At this point you'll need to go over to Damus to paste that NWC connection string into the proper place in that client. I am on Android, so I don't have Damus to be able to tell you exactly where to paste it in, but maybe @npub1xts…kk5s, @npub13v4…l3l8, or @npub1yau…vjmf can point you in the right direction.
Unfortunately, Primal on iOS does not support connecting an external wallet, so you won't be able to zap from Primal until they add it. Given the recent court ruling against Apple and in favor of Epic Games, I would not be surprised if Primal adds this in the near future, as the app on Android already includes it.
Another app you might want to try on iOS is Nostur. @npub1n0s…lahe is the dev behind that app, and he's packed a ton of features into it! He can tell you where to paste your NWC connection string from @npub1h2q…w8ch into Nostur.
We're live! Streaming Fallout: New Vegas for a first time playthrough.
#nevent1q…ga6h
#zapstream #gaming #gamestr #Fallout
I think it's decided, friends! I'll be streaming Fallout: New Vegas on Thursday evenings on zap.stream, starting tonight at 5:30pm Pacific Time and going until about 8:30pm or until I feel like stopping for the night.
Thanks to those who made the recommendation. It was very nearly unanimous!
#nevent1q…4m00
#Gaming #Fallout #ZapStream #Gamestr
Well, you are going to want something that allows you to both send and receive zaps, right?
Strike works for receiving zaps, since they give you a lightning address, but not so well for sending, because they don't have Nostr Wallet Connect. (Yet?)
I am not familiar with Exodus wallet, but it seems to be a multi-coin wallet, so I doubt it really has anything for Lightning and Nostr focused features.
My recommendation for dead simple Nostr integration from a custodial wallet is @npub1h2q…w8ch, hands down.
Setting up an account is free, and no KYC at https://coinos.io/
Once you do, you can go one of two ways.
1. Switch everything to Coinos. Put the lightning address they give you into your profile in place of the one you have from Alby so you can receive zaps, and copy/paste the Nostr Wallet Connect string from your Coinos settings into whichever Nostr client you are using, assuming it supports Nostr Wallet Connect, so you can send zaps.
2. Use Coinos WITH Alby by copying your Coinos Nostr Wallet Connect string into where your Alby account wants you to connect a wallet. Then you don't need to change your lightning address, as your Alby lightning address will send payments to your Coinos wallet. You'll still need to also paste the Nostr Wallet Connect string from Coinos into your Nostr client for sending zaps, though.
What Nostr client(s) are you using?
He rarely misses an opportunity to let us know when we're being silly.
New review finally up, covering @nprofile…47hg!
#naddr1qq…v8j0
Next up will be a web client! Let me know if you want to see @nprofile…l3vp's Jumble.social or @nprofile…5gcs's Coracle.social as the next review.
I didn't mean custom implementation for this purpose, I think you can probably do better with a custom relay implementation.
I mean, if it's already custom you can assign a serial number to each event and map those numbers to real events in a custom database. Then convert those numbers into single or double-word mnemonics for users.
Or is that boring, doesn't contain cryptographic tricks, centralized? Maybe it is, but I think boring is good and centralized is fine as long as it plugs into the rest of the Nostr ecosystem.
It sounds like you bought the cloud version of Alby Hub, and you may not have been aware of what that entails. Alby Hub is a self-custody Lightning node. That means, before you can connect it to your Alby account, you will need to set up Lightning channels and all that jazz.
Were you wanting to run a self-custody Lightning node in the cloud, or do you just want a custodial wallet you can link to your Alby account? If the latter, I would reach out to the @npub1get…0nfm folks and ask for a refund, since you weren't aware of what you were buying.
From there, I can help you get set up with a custodial wallet like @npub1h2q…w8ch or even @npub1kva…tkzv, which can be connected to your Alby account if you desire.
That said, this could indeed be done with a custom relay. One that pulls in 10002 events from all known relays and allows for a query of just the first several characters of a pubkey. There is no need expect all relays to have this behavior. From there the client will have the relays it can expect to find the event, and relays DO currently support partial event ID queries, right @npub1ark…h43w?
That was a major part of the reason I made the suggestion regarding partial pubkey queries. If you can query for a user's 10002 with just the first 6 characters of their pubkey, you can find their outbox relays where the event is likely stored, since 10002 events are intended to be shared far and wide.
Technically can't find an event even if you have the full ID anyway, because you don't know the relays the event is in. That's why we have nevent1 codes and relay and author hints in tags.
Choosing the relays for each client action is the most important part of Nostr but people have assumed that part away way too many times by hardcoding popular relays and expecting all events to be there, which works as long as we're ridiculously small, but kills the value proposition of Nostr entirely.
It's like assuming Bitcoin will always be zero: it's only true if the entire project is a failure, and in that case nothing matters anyway.
It's just unnecessary complexity. REQ filters are already too powerful, they should be simpler. The use cases are marginal and never important, often just "cool". They can all be implemented using custom relays with crazy logic, which is what we should be doing anyway for many other things.
Well done, sir! Would love to see the vast majority of users running their own Haven (or similar) relay and Web-of-Trust relay. Would make Nostr quite resilient.
Dude... immediately, too. Tapped where you tagged him and Amethyst gone.
Want your Amethyst to crash? Visit @nprofile…d0cu's profile. PlZ HALP @nprofile…pyug.
Please, @npub180c…h6w6, come tell us why we're out of our minds!
Then again, I think a "first time" playthrough is always more entertaining to watch. Those who join the stream get to re-experience what made them fall in love with the game when they first played it, and those who have never played it get to share in the experience.
DA:O is best DA. Even so, I only played it through once... I have started a few other times, but didn't have the time to stick it out. If I have time set aside for it each week for streaming, though...
Is there any reason, other than possible collisions where two pubkeys share the same leading characters, that relays should not support responses for partial pubkey inquiries?
So, relays are going to expect the full hex string for pubkeys, and reject anything less than that, eh? Picky buggers, but yes that eliminates my suggestion unless that behavior was changed...
Alright, say I want to make myself useful in a Nostr building context. Given my understanding of the protocol, where should I start in learning how to build on it?
Yes, and I find that horrifying! 🤣
Yeah, but I feel like a vibe-coder should at least be able to review, understand, and correct what the AI spits out when necessary.
That could work, if the place he shared it doesn't censor NIP-05s. They are domain based and easy to figure out what they are for, other than the fact that they look like an email.
Seems contradictory, right? Yet, here I am.
That, sir, sounds incredibly useful for builders! Thank you for breaking it down that way!
What should I stream on Thursday evenings? #AskNostr
Options available:
- Assassin's Creed (Never Played)
- Dragon Age: Origins (Beaten Once, but very replayable)
- Fallout: New Vegas (Never Played)
- Hogwarts Legacy (Played some, never beat)
- No Man's Sky ("Beat" once, but very replayable)
- Kingdom Come: Deliverance (Played some, never beat)
- Final Fantasy Pixel Remasters (For the nostalgia)
What say you?
At least most CLIs are dark mode by default. 😉
Ah, dev-speak. I am not there yet... Maybe one day, one step at a time, I will understand all that.
I impress @npub1jlr…ynqn often with the seeming contradiction of my depth of understanding of the protocol, somehow paired with my complete ignorance of how to write a single line of useful code.
CLI is intimidating for us plebs, man! I am barely getting used to doing things in CLI since I switched to Linux last year. Forcing myself out of the GUI comfort zone.
Adding to my list of resources.
I need to learn how to use nak in general...
That makes sense. Tools like NADAR exist already for searching all known relays for a particular event, and yes, an event you want to share in this way could be intentionally blasted far and wide to assist in finding it with just the first several characters of the hex. Runs against the philosophy of outbox, though.
I think maybe sharing a 6 or 7 word string of the author's hex pubkey along with 6 or 7 words of the event's hex ID would probably do the trick, and be more in line with outbox, though.
A user could pretty quickly commit to memory the phrase referring to their public key, so they would just need to add the phrase representing the particular event they want to share. Clients could then find the author's kind 10002, which should already be blasted far and wide in the relays, and look for the event itself on the author's listed outbox relays.
I feel like this could help diminish the chances of collision as well. How likely is it there will be two events with the same author and the same leading 6 characters for their hex ID?
By the way, it's easy to convert n-entities to their raw components at https://nak.nostr.com
Just paste it into the box and it will be decoded for you. Then you can grab the raw event id, pubkey, etc.
Good questions! I like the "event seed" option you mention.
Without relay hints, it's just a game of brute force searching relays. But perhaps we could encode the relay somehow. TBH that's a bit trickier. The primary ID of a relay is its URL. Encoding all of it would take too many words. But expressing the relay URL in plaintext would betray the purpose of the preceding 6 words, which would reduce this scheme's effectiveness against shadowbanning. Perhaps it's up to the user. Include the relay if you aren't in an adversarial environment, and exclude it if you are; without a relay hint you'll simply have to brute force search relays for it until you find it, which can be somewhat automated. If you are sharing an event in such a furtive way, you might want to broadcast your event to as many relays as you can in order to ease the pain of finding it.
LOL! Note IDs, nevents, naddrs, and hex IDs... So many to try and keep straight!
I think I've got it now, though. So you are proposing making a mnemonic phrase out of the first 6-8 characters of the HEX ID of, well, anything you want to, right? Could be the hex version of a user's npub, the hex version of a bookmark list's ID, or the hex version of a book ID published to Alexandria, and as long as the Nostr client knows where to look for it, since relay hints aren't encoded into the hex, only the nevent or naddr, the client should be able to find it with just that mnemonic phrase.
And hex IDs are completely different from nevents and such. You can't just take the "nevent" prefix off of the front and what you are left with is the hex ID. It's a completely different set of characters.
Jumble is kind enough to allow users to see the raw event information if they want to, and I believe the hex ID of your reply is:
`a50bc29d3377e1b0f50a0f471ca7431d27489f013df620a90e313c5f10b1c2a9`
While the nevent is:
`nevent1qvzqqqqqqypzp68dx7vvdlltl7sg2qdv8838ze3tl5tq76y0jnz966fdsana6dz6qyt8wumn8ghj7mn0wd68yetvd96x2uewdaexwtcpr9mhxue69uhhwmm59e38y6t8dp6xymmvwshxuet59uqzpfgtc2wnxalpkr6s5r68rjn5x8f8fz0sz00kyz5suvfutugtrs4ffsug0m`
But we could have clients display an option to copy an "event seed" or some similar title for it, which is a mnemonic phrase of human readable words that represent the first 6-8 characters of the hex ID.
So, the question becomes, how will clients know where to find the referenced event without relay hints?
Do we have "indexer" relays that just record hex IDs and what relays they were seen on, so clients can reach out to the indexer to tell them where to look for the event? Or do we use a DHT for that? Or do we make the phrase 12 words, with the first 6 being a mnemonic of the author's pubkey and the last 6 the mnemonic of the event, and then the client can just check the author's kind 10002 relay list to see where to look for the event?
Correct! But onlt because I am on Android... It's the client that actually tempts me to switch.
Nostur is the best sleeper iOS client you’re probably not using.
#note1fz8…kl8m
@nprofile…pyug why does #Amethyst do this?
https://relay.brightbolt.net/5fed0054cdef340f7aa83ce0f0e9c48b516cc4261f24877f76787f8b1c9bf596.jpg
You can already link to other profiles in your bio. Look at mine.
You just need to add it as `@npub1g7y…g7yf...` etc.
Coracle does. Not sure about any others off the top of my head.
The only mobile app I know of with them built in already is Nostur on iOS.
Give it time. This list type is brand new. Clients will start adding follow packs before long.
the same for linking other profiles in the bio
#asknostr
#nevent1q…ly8v
Yeah, I think a lot of Nostr users already do this sort of separation of identities for different purposes in a manual way, creating entirely new nsecs for each identity. However, your method of deriving different identities from one seed phrase, using different derivation paths, is more elegant and far less manual of a process. 😂
A Nostr key is essentially a Bitcoin key — the only difference is the format.
Others don’t know that the two public keys belong to the same seed phrase.
Yeah, that's pretty slick, only needing to keep track of one seed phrase and having various Nostr identities tied to it.
Not the use case I am after at the moment, but incredibly cool.
And there would be no way for someone who only knows the npub for one ID to tell that it is related to the npub of another ID generated from the same seed phrase, right?
Did you mean https://github.com/nostr-protocol/nips/blob/master/06.md ?
I kind of know how mnemonic seed phrases work, and depending on the derivation path you use, you end up with a different key. But each of those would be treated as separate identities entirely by Nostr clients, right?
Sorry, the correct link is:
https://github.com/nostr-protocol/nips/blob/master/06.md
Using a seed phrase means using new IDs — just like how a Bitcoin wallet seed phrase works.
Now you have me confused... This is somehow related to DNS-based Nostr addresses as outlined in NIP-05?
https://github.com/nostr-protocol/nips/blob/master/05.md
So, child keys from my main nsec, or would this seed phrase be tied to an entirely separate Nostr identity?
It might be worth trying Keychat’s 12-word seed phrase — it allows you to derive multiple IDs with ease.🤔
#nevent1q…lhnu
What is "this" that you are referring to opening in an Android client?
Just note, Amber only tracks Keychat's permissions when you use this method. Any permission you grant to Keychat will be granted to all web apps you sign into using Keychat's browser.
#Nostr tip: @npub1h0u…rwx8's built in browser effectively makes every Nostr app that supports browser extension login compatible with #Amber signer.
Log into Keychat with Amber, and log into every other web app via Keychat.
For the record, price on that date was $16,163.
Thank you very much! I will take it into consideration.
Back on November 20th, 2022, I sent an email to myself, scheduling it to arrive in my inbox on May 1st of this year.
It was a simple email. Just a screenshot of a post from a buddy of mine gloating about how far down Bitcoin was in price at the time.
His exact words were, "Bitcoin isn't an investment. Many a fool right now is recognizing his mistake in buying it."
Well, my friend, who is the fool now?
1 sat = 1 sat is the only math that matters anyway.
Not quite. Wouldn't 25 sats be 2.5 cents at $100k Bitcoin?
I think we need to hit $1m/Bitcoin before we get sat:cent parity.
*future...
Saw it AS I HIT POST!
So @npub15yp…mpcx, should we be expecting some #RUNSTR shirts popping up in the Bullish Store in the near furure?
As said, above my head... But from my grug-brain understanding, it should only take 7-8 characters of a Nostr event ID before the chances that there is another event with the same leading characters is slim to none.
That being the case, a Nostr client doesn't really need the whole thing in order to pull up the event, so long as it is searching the right relays for it. If the full event ID is `nevent1qvzqqqqqqypzq6z80pwapdkhn6st5d5uxfm5atcl82jzyhdwmurs7q656felnj6xqy2hwumn8ghj7un9d3shjtnyv9kh2uewd9hj7qgswaehxw309ahx7um5wghx6mmd9uqzqc8ztkrnk6rnwl6dgznhtvxf6fuhpkja3y2tkuqpvl6uaxekycz5xdhvag,` then clients should only need `1qvzqqqq` to find that specific event, and those characters could be converted to mnemonic words that can be memorized or otherwise hidden in a message. Nostr clients could even support looking up the event using those mnemonic words.
What are you thinking? Organize them into some triage categories?
- Major Bugs/Broken Features
- Minor Bugs
- Quality of Life Features
- Interoperability Enhancements
- UX Improvements
- Major New Feature Request (For Roadmap)
- Major New Feature Request (Not currently planned)
Maybe a couple more categories and triage their priority from there?
I’m solving two or three issues a day 😂 Prioritizing the ones that affect usability.
Forgiven. How many issues are you working your way through at this point? 😂
Sorry, I totally forgot about that haha.
It's above my head, honestly, but it sounds pretty cool to be able to reference a Nostr event with just 6-8 mnemonic words.
what the hopping fucking sideways magical tomfoolery genius is this?!?
#nevent1q…xafy
I found out why the issues I have opened previously aren't showing... GitHub flagged my account. Probably because I signed up with an email alias rather than my actual email... I'll need to get that sorted at some point.
Reinstall Amethyst from the @npub10r8…t2p8. No translation.
do any clients support pinning a note to top of profile? does it need a NIP?
Performance can be a challenge with that kind of upload volume? No way! 😉
Thanks for the info!
@npub137c…k37w @npub13ch…dsaw, any insight on the media gallery only showing the latest upload when logged in, as mentioned above, rather than being able to browse through millions of free uploads?
Yep. Feature page also lists SVGs as added under Creator instead of Professional.
Hey, sorry about the confusion. The zip uploads are only supported on the creator plans since we had people asking for the ability to share their media assets in packs. The feature page mistakenly mentions it in the Pro plan. @npub13ch…dsaw
Not necessarily. There are certain things each app does better than the others. Also, there are all sorts of different types of content now, not all of which is supported by all clients. And @npub19ma…axkl's point is a good one about using Nostr on different devices, too.
Example: If I am on my PC, I will probably use a web client, and lately I have really been liking Jumble.social. The only downside is, Jumble's search isn't great when searching for user profiles. For that, I generally hop over to Coracle, because it will display results based on my web-of-trust, so I don't have to worry about being duped by an impostor. Coracle is really useful for finding new profiles to follow, as well. If I want to find something very specific, though, like a note posted by a specific npub, with a key word, and within a certain date range, well then I am going to open up an advanced search on Primal for that task.
Same thing goes while on my phone. I'll probably use Amethyst for most things, but go to Coracle or Jumble for things they are better suited to do. And let's not forget that if I want to read a long-form article, I am probably going to open up Habla.news or Highlighter.com, and Fountain is now a Nostr app, too, for when I want to listen to podcasts. Or if I want to get inspiration on what to have for dinner, I will open up zap.cooking.
All of them "work," but that doesn't mean I could ever be satisfied with just using one of them.
Getting some mixed messaging about what file types are supported for the Professional plan, as well.
Since that is the plan I have, I tried uploading a zip file and confirmed I can't. Seems the Features page needs an update.
https://npub1kun5628raxpm7usdkj62z2337hr77f3ryrg9cf0vjpyf4jvk9r9smv3lhe.blossom.band/e0badd8e7ca3ae6afb4a7370ec84c3fff96eadc4dc12c6f2ec830c4ce8bdc3e4.jpg
https://npub1kun5628raxpm7usdkj62z2337hr77f3ryrg9cf0vjpyf4jvk9r9smv3lhe.blossom.band/f168ae673fc8e2279b1beb6e4b4f60e10cfd1b8ec00baf81c9395803071e58f0.jpg
To promote the 'top list' feature i'm working on https://asknostr.site i created a following pack with the top contributors
https://following.space/d/taaiacxkp6ft?p=8aa70f4433129dadb71330ac89f62b534caa200a9f3ee349a0f4a5593073d1a6
It's in the order of 'top contributors' from the askhostr.site database so far
https://blossom.primal.net/8918c209fe4d9db2ea089bf9b0b582a8676a2c17a13c020387de365484104298.png
Thanks! Ya, I'm curious just to learn the differences with all this debate going on, so would appreciate knowing what features in knots make it possible / optimize mining via DATUM.
If there is anyone NOT pushing mining centralization, it's @npub1lh2…a9nk and the others at @npub1qtv…7dze, who don't even require individual miners to use their block templates. I can run Knots with whatever datacarrier limit I want and mine on OCEAN, generating my own block templates. Yeah, I am a nobody home miner, but large scale miners can do exactly the same.
Certain configuration options in Datum require Knots, because Core doesn't allow them to be configured, if I remember correctly. @nprofile…m3mt built Datum, he can clarify.
Why exactly does running DATUM require knots over core...at least when running on my @npub126n…e9ll ? I know the people behind DATUM at the @npub1qtv…7dze team prefer knots, but is that preference the reason or something else? Thanks! 🤙
#asknostr
#bitcoin
Note, when not logged in, it shows several more images. It only shows just the most recent image when I am logged in.
@npub137c…k37w @npub13ch…dsaw the free media gallery is looking empty. Seems to only be showing the most recent image posted to it.
https://npub1kun5628raxpm7usdkj62z2337hr77f3ryrg9cf0vjpyf4jvk9r9smv3lhe.blossom.band/e0c53215d10a3c26a78b62b92891f1cccda6ea36afd73e74dfda7d057b3e0a0f.jpg
Thanks for the reminder. Fresh backup started. 🫡
Before this update, I don't think Primal had push notifications at all.
Other Nostr apps have followed that basic flow of having push notifications off by default.
Still others have strange behavior where push notifications only occur while you actually have the app open, which is the opposite of useful...
Either way, your current option in apps that give you one is to either have push notifications in real time, or no notifications at all. I think there could be a happy medium struck where users could opt for a daily or weekly summary/digest, either by email as with @nprofile…5gcs's tool or by push notification with Pokey.
The advantage of pokey is, it's Nostr-native and it allows you to select the Nostr app you want to open the notification with, instead of being locked into opening the notification with one particular client. If the same function was added to Amethyst, for instance, then you would be more or less locked into opening the notification with Amethyst. Yes, you could swipe the notification away and open a different client, but it's less friction to just tap the notification to open Amethyst, so that's what most will do.
I think all notifications should just be off by default and users should have the ability to turn ones on as they see fit. Pretty sure that's what Primal just enabled in their recent update.
That bot is the reason I started paying attention to how much unnecessary garbage is added into URLs, so I started stripping it all out.
Good bot.
True. Would be more ideal if Pokey sent one "summary" type of notification if either daily or weekly were selected, but not sure if that's possible. One that just says, "You received X replies and X zaps and X reactions today/this week." Tapping on it woud take the user to Pokey's Notifications tab where they can be reviewed in detail.
If that's not possible, I think it is still fine. Any time I have more than a few notifications from Pokey, Android groups them together so I can either expand them to review each, or dismiss them as a group.
Some of you have no clue how nefarious the internet is and it shows by the dirty links you post.
Sanitize your links, people! Geez.
This is why I regularly zap the @nprofile…q3tt bot. This is the correct way to make a helpful, focused bot.
#ignorancecanbeleathal #dirtylinks #cleanyourlinks #sanitizeyourlinks #dontbeignorant #grownostr
That's an interesting, feature, if you are popular you would receive dozens of notifications at once, but still it's doable
But no one uses that app, I'm using email because people use it
What is the origin of this response?
Say a friend of mine from church is wanting to find me on Nostr. They search for dikaios1517@[churchdomain]. Is this the response that would be sent from the domain to my nostr client saying, "Here's his npub. He's also known as dikaios1517@nostrplebs.com" so the client can then display the proper profile to my friend?
Right? I have a few NIP-05s I COULD switch to at any time. But I can only be looked up by one of them at a time? Seems clients should be able to request from the domain whether I have that particular NIP-05 "active" or not, and it should still return my npub.
The aspect of me confirming, by signing a Nostr event, that I am in fact associated with that domain is important, though. So maybe a list kind of some sort?
Great article!
One thing I have found quite limiting about NIP-05 is that it only allows you to have one "association" at a time. I have dikaios1517@nostrplebs.com. I proudly keep it, because I have been with them since just after the service went live. Yet... I have a lot of other groups I am associated with, that I must forego them being able to confirm that association if I want to stay with nostrplebs.
I don't see any reason why this must be the case. If I want to continue to rep nostrplebs, but also have my church's domain confirm that my npub is associated with my church, or my employer's domain confirm that my npub is associated with them, or Sovereign Craft confirm my npub is the same Dikaios1517 they see on the server there, all of them should be able to do so, without having to trade one out for the other in my kind 0.
Maybe there should be a primary NIP-05, and then a comma separated field in the kind 0 with alternative NIP-05s that also point to your npub for those other associations?
Well, you got buy-in from greenart7c3, and Amber is probably the most widely used bunker signer right now, so that's a start!
By the way. I need to get my GitHub account figured out. It has apparently been flagged, so no one can see what I comment or any issues I add... Probably because I signed up using an email alias, rather than my actual email address. Highly annoying.
Here's the PR I opened on locked bunker delegation, : https://github.com/nostr-protocol/nips/pull/1795
Yeah, I am less concerned about the signing. That can be handled by giving the notifications service a separate bunker token that can be revoked if it tries signing things I don't want it to, or in the case of Pokey, I can just revoke its Android signer permissions.
I am definitely interested in the idea you have about locked permissions that you mentioned in the video.
And if push notifications can be e2ee... Could be a better solution all-around compared to email.
I am just spitballing here... Could any of this be combined with @npub1mut…23vg's server-side secure enclaves to enhance the privacy of any of this? Any insight @npub136j…jnxf?
Now... Who are those 58 who fleeced everyone else?
Yeah, I saw you had highlighted that. It is quite ironic indeed.
There's also the issue that running your own email server is a fruitless effort, because anything outside of the major email providers is almost universally marked as spam and kept out of the receiver's inbox.
Push notifications are cool and all, but they are part of what makes social media so addicting. What if, instead of push notifications, you could get a daily or weekly email with your notifications? Might be a healthier way to interact than feeling like you always need to immediately check your phone to see what the latest alert was about.
#nevent1q…8vrj
That said, I wouldn't mind seeing this done in a more Nostr-native way.
@npub1v3t…yvjh would it be possible to have a few options for when Pokey sends push notifications? 1. Real-time (current practice), 2. At a specific time each day. 3. On a specific day each week.
If so, I would love to be able to subscribe to notifications for community relays' calendar, chat, and threads events in Pokey, too. Or get really crazy and allow Pokey to subscribe to a custom feed... Then users could, say, create a custom feed that was based on a kind 30000 list, but only showed long-form notes, and Pokey could alert daily if any of those npubs had written an article.
I think the takeaway here is just how insecure legacy infrastructure is, both in terms of platforms and in terms of email. Anchor makes me feel really insecure because of all the ways that I can surveil and hijack my users's authentication! But that's really a result of how much privacy people are used to giving away on the internet.
You could host your own instance of anchor, which would take care of the bunker url piece, but it would require you to run a server and use an email service (which can in turn then look at the content of your emails). You could go further and run your own email server, but that's a little over the top even for technical people.
One other possible solution I can think of would be to use PGP to encrypt the emails that are sent, but again, that solution has been shown to be too much hassle for anyone but the most paranoid to use on a regular basis.
The other day I was reading the original RSA paper, which starts with
> The era of “electronic mail” [10] may soon be upon us; we must ensure that two important properties of the current “paper mail” system are preserved: (a) messages are private, and (b) messages can be signed.
Ironically, email is neither private nor signed — but nostr is!
Just got to that point in the video. 😂
Nice!
I don't see any issue with the provider and third party handlers being able to see notifications for anything that is on a public relay, but I can see that being a problem for private relay communities. Any ideas how users could have these alerts without compromising the privacy of the community?
Is it possible to run the infrastructure themselves and/or eliminate the third party dependencies?
I take it this will be how you do the daily or weekly notifications for Flotilla spaces?
Well, that and the ability to just print money when folks borrow it creates much more demand than there would be if folks had to be constrained by a fixed money supply, and couldn't just borrow new money out of thin air.
Now we just need clients to allow users to mirror their media to multiple Blossom servers at the time of upload.
I love @npub1klr…7gxc's bouquet.slidestr.net, but mirroring after upload, when they uploaded from any other client, is something the user has to remember to go and do. Additionally, it seems to be very unreliable in bouquet, unless I am doing something wrong.
Primal has added the ability to mirror to multiple blossom servers at the, and it is one of the things I applaud them for. Need to see more apps that already have Blossom support add this, too.
#nevent1q…7klc
No, you nailed it on the head, coming from someone who formerly worked in consumer lending.
It still drove me nuts that the lender I worked for would regularly UNDERCOLLATERALIZE a depreciating asset. We're talking 120% LTV on a regular basis for new cars that lost 50% of their value as soon as they left the lot.
It's not anymore. Nostr.build now has a Blossom server (blossom.band) that you can use to host your media in conjunction with other blossom servers you may choose.
Prior to adding Blossom support, nostr.band only supported NIP-96 for uploading to their hosting service. I will admit my ignorance when it comes to the tradeoffs between NIP-96 and blossom. I believe both of them allowed for confirmation that the media had not been altered because you could compare the data received to the hash of the data, and you could upload the file to multiple NIP-96 hosts at once. But I think this still didn't allow for the media to be retrieved from other media hosts automatically if the original one was down or otherwise not responding, which Blossom does.
Also, it was common for people to ONLY upload to Nostr.build, and nowhere else for redundancy, since the media couldn't be retrieved automatically, even if they had also stored it elsewhere, so Nostr.build was not really any different from any other centralized data hosting service, other than their superior media management for those with paid accounts. Now, with Blossom support... Nostr.build is a really great service to have, even if they are only one of a few places you are uploading your media to.
Yeah, it's odd. It's doing that with a few npubs. Not able to find their kind 0 maybe?
Hodlbod on my Notedeck:
https://npub1kun5628raxpm7usdkj62z2337hr77f3ryrg9cf0vjpyf4jvk9r9smv3lhe.blossom.band/afbf1dab4211584839503670cc22e7dc5ea8d9fd931ca16210b5a40ada0aad77.jpg
Hodlbod on Jumble:
https://npub1kun5628raxpm7usdkj62z2337hr77f3ryrg9cf0vjpyf4jvk9r9smv3lhe.blossom.band/62d6600069a57cff5e6a827dc575506e82d96b102fbca316130a0f0aa523f8d9.jpg
Web-of-trust based reply filtering like Coracle has would be wonderful, for instance. End the game of spammer whack-a-mole!
https://npub1kun5628raxpm7usdkj62z2337hr77f3ryrg9cf0vjpyf4jvk9r9smv3lhe.blossom.band/7b68d32871139b37774aad982bc531943899bb3adf6a3d86d1bcffe6e9b1ed6b.jpg
What is Blossom and why are folks so excited about it?
#nevent1q…cn6q
Banks loan against volatile assets all the time when their borrowers buy new cars. The difference is, they're never required to mark it to market.
Streams can be quite long and large files. Should probably also support this from @nprofile…ucf3:
#nevent1q…flkt
RIGHT?! The Blossom Protocol has blown my mind since day 1! This would put it on steroids!
There are still some things I prefer other clients for, but Jumble has become my daily driver on desktop, and that list also keeps getting shorter.
👀 mirrored live streaming... imagine how powerful that could be.
That would be @nprofile…278z
As @nprofile…um05 mentioned, it's a way to store media. Built for Nostr, but usable for anything that needs media accessible on the web.
Nostr has relays, right? But with very few exceptions, relays only store text-based notes, not photos, videos, or other media. Before Blossom, you had to store your photos with some media hosting service, and with no redundancy for decentralized censorship resistance.
Blossom is a protocol, like Nostr is a protocol, and anyone can run a blossom server. This allows folks to host media for themselves or others and ideally save the same file on more than one server, so that if one goes down, the media is still available from the others.
Of course, Nostr clients have to know how to "speak Blossom" to know where to fetch the media from if the original location isn't working. So your results will vary from client to client.
@npub1v0l…qj49 @npub1ye5…knpr Would it be possible to have a BUD that supports live-streaming from Zap-Stream to a blob on my Blossom Server? 👀
i see, sounds handy. cool name too, who came up with it?
I'm critical of taking out a loan against a volatile asset, as that's what brings us @npub1r3k…uytc.
It’s a way to store your images and videos 🥳
Because you can run your own blossom server and sync it to multiple of them for easy access and decentralization 🥰
what's blossom, and why is everyone talking about it? #asknostr
Jumble.social is the best Nostr client.
Not even NADAR could find that one.
https://npub1kun5628raxpm7usdkj62z2337hr77f3ryrg9cf0vjpyf4jvk9r9smv3lhe.blossom.band/5a431060ca9c18002e0786d5e17ab250eb50fc4e5b0f00fd907a012dfe76034e.jpg
Cheers! Sadly it doesn't seem to be in my search relays either. I can only see the preview:
#naddr1qq…gn4n
Yeah... Getting a wallet set up for receiving zaps is definitely an onboarding friction, but it also means the user is 100% aware of where tjeir zaps should be going and how to access them.
Zaps just automatically being sent to a default mint with eCash locked to their npub, without the user having to do any set up! sounds really cool! That is until you realize that the user will be receiving funds by a method they didn't actively consent to and that many won't know where to go to redeem them.
Just more AskNostr questions for me, I suppose. 😂
At least when a user adds a lightning address to their profile, we know that's how they want to receive zaps.
I did start using Keychat's wallet with their browser for zapping. No complaints so far. I just have sats spread all over the place from clients that have their own wallets instead of NWC connections to my existing wallet... But Keychat is using eCash for postage, so I get it.
Ah yes, I didn't think about that aspect. I also found the Olas wallet NIP-60 wallet pretty buggy. I see Keychat and 0xchat are both opting for on-device wallets, perhaps that's the direction for now.
Honestly haven't played around with them much. I like the idea, but I feel like they need to be more ubiquitous, or else there needs to be something in the user's profile that flags they are ok with receiving zaps via NIP-60. Otherwise, we'll have people receiving zaps to NIP-60 wallets who are using clients that don't give them access to it, and they have no idea how to use it.
I think there was some talk about adding a "Preferred payment method" field to profiles. Not sure if that's still on the table.
The only ones I played with a bit were the original Nutsack wallet and Olas. Neither one was very reliable...
@npub1kun…3lhe Where do you think the most reliable NIP-60 wallet implementation is right now?
I feel like video hosting is the final boss that must be slayed. @npub1wf4…dgh9's latest is very promising in that regard.
Now we just need a client that implements it, and better discovery tools for finding interesting videos.
#nevent1q…vxqy
Flare.pub was a good start. Unfortunately it is abandonware now, as far as I can tell. Need someone else to take up the call.
Awesome! I guess I just hadn't had an opportunity to notice, yet.
Haha, it was updated last week.
https://image.nostr.build/3bf138c21c1a3a72f53affe8b0cf9a8da761d307a915830a29522181d666c8cb.png
Absolutely! Voyage does this and works great!
The same would not be said about kind 20, though. If clients support it, they are expected to render the images.
Yeah, it's totally fine for clients not to render image links in kind 1 notes, right?
When? Recent update? I could have sworn I was just having to scroll through a repost of isolabellart's whole gallery just a couple days ago and wishing there had been a truncated version...
It might be the temptation for everything to have a category, and kind 1 are called "short TEXT notes" on the NIPs repo, or as a "simple plaintext note." in NIP-10 specifically. Neither of those suggest that images belong within the umbrella of kind 1. Clients aren't even required to render image links in kind 1 notes.
Yes. Minimal formatting should be expected in kind 1. I almost wish it had a character limit, too. Way too many people effectively writing articles in kind 1...
Speaking of which, do you have any plans to truncate long kind 1 posts, and add a "show more" button in Jumble @npub1syj…f6wl?
Yes, exactly. When a client supports both kind 1 and kind 20, it can easily confuse users, and it's hard to handle because, from their perspective, the difference between the two isn't that significant.
As of now, I don't see the need for adding a new type to distinguish image-based notes. I also don't understand why Olas is doing it this way, it could easily achieve the same result with a special tag, like ["c", "image"]
I do think it's great how we have simple uniform kind 1 posts and then a separate long form spec with more 𝓯𝓸𝓻𝓶𝓪𝓽𝓽𝓲𝓷𝓰 𝓸𝓹𝓽𝓲𝓸𝓷𝓼 🤙
Someone coming from Instagram should have no trouble understanding why their posts to Instagram didn't show up on X, and someone coming from X should have no trouble understanding why their posts on X don't show up on Instagram. The same should translate to Nostr and understanding why posts to Olas, which is an Instagram ripoff, don't show up on "Twitter clone" clients.
It should further blow their minds when they learn that some clients can display both.
It doesn't, because users assume Nostr is like a platform, and that all clients on that platform should display all content the platform supports.
That said, I am warming up to the idea that kind 20 is superfluous, and we should just use hashtags to differentiate between memes, photography, and other forms of image-based media. There IS a distinction between kind 1 notes and kind 20, but it is small enough that maybe a separate kind isn't justified.
Kind 1 is a microblogging note that MAY contain image links, and kind 1 clients may or may not render those links as the images they link to, though most do.
Kind 20 is a picture and will ALWAYS contain an image link that supporting clients are expected to render. It MAY also contain a caption.
So, they are definitely different in how they function, but I agree that it can be confusing and kind 1 can fulfill the function of kind 20 and be pulled into a separate image feed if desired. Eh... I'd probably be fine with doing away with it after all.
Perhaps, and I think that is what @npub1klr…7gxc is using for categorizing images on slidestr. Correct me if I am wrong, @npub1klr…7gxc.
But that's not a solution for reducing all content types down into kind 1. Images with separate hashtags for memes vs photography and art? Yeah, that's probably fine and something users will do naturally, and no one really wants to have all images taken out of kind 1 feeds.
Long-form, though? Probably should stay a separate kind. Same with TikTok style short videos. If I want to scroll though that content, I would rather do so in a separate feed than have it in my main feed, and I doubt I am alone in that. The same would be true for many other specialized kinds. Indeed, I would prefer that zap.cooking used a separate note kind instead of shoe-horning long-form into a recipe format, for instance. Now if I write a recipe, it will show up on habla.news as though it is an article or blog that I wrote... Separate kinds are helpful for classifying the types of content that should show up together, and then the client dev can decide if they want to have other types of content also show up in the same feed.
For regular users coming from platforms like X or Instagram, it's hard to grasp. It's difficult to explain why there are two different event kinds, why kind 20 doesn't show up on some clients, why it's placed in a separate tab on others, or even why notes posted in different feeds are considered different kinds of event
The reason there hasn't been much discussion about the issues with kind 20, in my opinion, is simply because its popularity has decreased. I quickly browsed through some big relays' kind 20 notes, and they are pretty scarce, with most of them looking like content posted by bots.
Trying out the new #NoteDeck beta. Looking really good!
Hilariously, it doesn't seem to be able to find @npub1jlr…ynqn's handle and profile picture.
Logging in with Amber seems to be broken. Spins for a while and then gives me this:
https://npub1kun5628raxpm7usdkj62z2337hr77f3ryrg9cf0vjpyf4jvk9r9smv3lhe.blossom.band/818151f7ec4868f7acda2029b5332ff11df1580446859b247ea43bb29e4740b7.jpg
Amber is working with other apps just fine, and the issue persists after reinstall and reboot.
LOL! And I grabbed the wrong one...
Another try:
#nevent1q…u07t
Gotta go with the event ID, my friend. It has built in relay hints so the rest of us can see it.
#nevent1q…sv7g
Now we just need a solid video client.
Knots so I can create my own block templates using Datum.
The mind blowing part here is not my unix tool, it is showing that nostr is a practical decentralized alternative to Usenet NZBs (torrents are a different thing)
- Blossom servers do not need to store a whole large video file
- Blossom servers do not need to stream an entire large file
- Blossom operators have plausible deniability in terms of content as the segments are encrypted (and they may not have all) and they don't control the key
- Video clients now have mutiple failovers if a segment is stored in multiple servers
- There are bandwidth savings if the video is not watched entirely
- Content creators can exchange the AES key against a zap
Youtube, here we come.
#nevent1q…rtmd
Fork wars? Is someone actually proposing a consensus-breaking change, or is it still just a mempool policy debate?
Hey man. I took a look at your profile on Primal web and on Android and it looks like your images are showing in all your previous posts there. Do you have a specific note ID you can share where that isn't the case?
Bear in mind, Primal may take a bit of time to index your images if they were uploaded to a media host other than their own. They don't display the image directly from your media host, but rather cache it on their own servers so that those using Primal are only connecting to their servers to read notes and media.
You can copy the note ID and run it through Amethyst's search function. Search uses different relays which may have the note available, even if your read relays do not.
To copy the note ID, long-press on the notification that it isn't on your relays, then select "Note ID" to copy it to your clipboard.
She never had a brand to begin with. Accidentally becoming meme-famous for 3 days isn’t a ‘brand’.
#note1a08…0hv0
‘You got to be really careful what you tie your name to’: The Hawk Tuah girl is planning a rebrand
https://www.fastcompany.com/91328963/the-hawk-tuah-girl-is-planning-a-rebrand
This old mine in rural Pennsylvania was used to power crypto—and then it shut down without a word
https://www.fastcompany.com/91327941/this-old-mine-in-rural-pennsylvania-was-used-to-power-crypto-and-then-it-shut-down-without-a-word
Fountain 1.2 is live on iOS and Android 🚀
This massive update brings significant design and UX improvements across the app along with a new episode summaries features. Here's what's new:
https://blossom.primal.net/f846ce562a973b422a277339577e5b300b13468924a7f77397ab542b132adb86.png
Library Design Update
We've made it much easier to navigate between podcasts and music in your library with the addition of the new content-type filters. The Recently Played view allows you to quickly jump back into what you were listening to before and the design of the content cards have been refreshed too.
https://blossom.primal.net/5d90d74d4144fd37e763e0385c4e12dfca78642da85c17dcd59c8a361da7c2a5.png
Content Pages Design Update
All of the different content pages have undergone an extensive redesign, including shows, episodes, artists, albums, tracks, clips and playlists. We’ve replaced the tab layout with scrollable pages, improved the formatting of show notes and revamped features like chapters and transcripts.
https://blossom.primal.net/7398820f785525e9359e5d71516c663b36127185bf26f248eb37306992e372f7.png
Episode Summaries
Every episode page now has a Summary button above the show notes. Simply pay 500 sats to unlock a summary, or upgrade to Fountain Premium for $2.99/month to enjoy unlimited summaries. Summaries and transcripts now come as a bundle, and they’re now faster, cheaper, and more accurate than ever before.
https://blossom.primal.net/d18a665d9beb49227b18be23a7319296d9d2e664ebecdf7bc42e5fa9cce5cc54.png
Playback Improvements
We’ve completely rebuilt our audio engine from the ground up. Playback is now more robust and reliable — especially for music. Tracks now play instantly when tapped, and if you're playing an album, or playlist, you can now skip next and previous seamlessly. We've also made some design updates to the player for easier access show notes, comments, transcripts and chapters, and we added a smart resume feature for podcasts.
We would love to hear how you’re finding Fountain 1.2. Please submit your thoughts and feedback via the main menu in the app and we will take it on board as we continue to improve the app.
Read more:
https://blog.fountain.fm/p/1-2-1
Is there a way to fetch a note that is not in my relay list using amethyst?
#asknostr
Hopefully not deep state shenanigans but you never know
Are shenanigans underway you think?
Not any currently. There was Dave, and I think @npub1xts…kk5s is bringing him back in some form. Also Cyborg, who would post jokes as replies and interact a bit. He got a bit annoying, though.
Not aware of others that are live right now.
I can definitely see that being the case, too. I think part of the reason people aren't too fussed about it, though, is that other clients have now integrated kind 20, and also it's kind of par for the course with Pablo. He creates a lot of things that are decent ideas, half finishes them, leaves a number of things broken, and just moves on to something new...
The idea of kind 20 is for people to share their own photographs and artwork. Something more than just sharing a screenshot, meme, or other image content that is often shared in kind 1 note, which would all get lumped into the same feed if it is just looking for kind 1 notes with image links.
Same thing as having a separate video kind. It is intended for posting original videos, with a title and description, as seen on flare.pub. Not just for every youtube or mp4 link someone might share in a kind 1 note.
Having separate kinds for such content allows each client to decide whether they want to have that content included in a single feed along with kind 1 notes, separate it out into a separate feed, let users decide what kinds they want in their feed, or not support certain kinds in their client at all.
I think this is something that can be solved in client UX. For instance, in Amethyst, you can't add a kind 20 from the home feed. You have to go to the media feed, and vice versa. This makes it very clear that you are posting to a different feed.
When Olas first came out, I remember handling a lot of questions in the AskNostr hashtag about why the images they posted there weren't showing up in the main feed on other clients, but that died down within a couple weeks and I haven't seen similar questions in some time. That is also largely due to many major clients adding separate feeds for kind 20 that didn't exist at the time.
I dunno, I think there is a place for image-focused clients that aren't just "Find all the kind 1 notes that have an image link in them." Though, admittedly, @npub1klr…7gxc built a pretty good one with slidestr.net.
Many kind 1 clients also let you share your kind 20 notes easily as a kind 1 quote-post, if you want it to be seen on a "main feed." And when it comes to fragmentation, there is nothing stopping kind 1 clients from adding kind 20 to their main feeds, too. Heck, I just created a custom feed on #Coracle that does just that.
Having a separate kind allows each client to do something different, or decide not to include them at all. I like having the flexibility for Amethyst to do a feed of kind 20 and 22, Freeflow to just do kind 22, Olas to just do kind 20, Jumble to have separate tabs for kind 1 and kind 20, without any kind 22, and Coracle to allow the user to build a feed of whatever kinds they want to see in the same feed. Having clients do different things with the same content is one of Nostr's superpowers, right? It allows users to choose the client that best serves them the content they want to see in the way they want to see it.
I’ve noticed that having both kind 1 and kind 20 notes coexisting can confuse many users. They might wonder why some notes appear in the 'Pictures' tab but not in the 'Notes' tab, especially since, in traditional apps, the 'Pictures' or 'Media' tab is usually just a subset of the 'Notes' tab. They might also be unaware that if they post a kind 20 note, others won’t be able to see their content on many clients.
If the quality of kind 20 content does indeed turn out to be higher than that of kind 1 in the future, I’ll create a separate app for it and further optimize it.