Delete is and has always been a core part of the nostr protocol. Essentially Nostr delete is just like on centralized platforms, not all copies of content are deleted when you request servers delete something.

I fundamentally don’t understand why nostr app developers keep insisting on disabling delete and pretending that nostr doesn’t support it. Delete works in nostr and it is a large part of why we switched from secure scuttlebutt to nostr. Delete can’t work in scuttlebutt, but does work in nostr.

Users should be informed that there is no way to force relays to honor your delete requests. And i think dishonest relays should be something we can rate and track in nostr clients. But to say we don’t have delete or edit in nostr is both incorrect and undermining the adoption of the protocol.


I would like to send 33 billion BTC to my cold storage but bitcoin is censoring me 😘


85% of whirlpool users.

Not wallet users. It is absurd to suggest that 85% of any wallet's install base has a private node running alongside it.

Lunacy.


Developers censor tx with OP_RETURN > 80 bytes = GOOD
Developers censor tx with OP_RETURN > 40 bytes = BAD

I made a new coinjoin tool that needs 84 bytes of OP_RETURN data and devs are censoring my transactions :/


42 is 40 + 2 opcodes (which are counted in the current versions)

If you think Core gets to just dictate things, get over your centralization mindset.

Knots has used 40/42 since 2013. Samourai are the ones who chose to exceed it.


Don't forget BlackRock can decide on behalf of all their spot ETF investors which fork of #bitcoin is the "real" bitcoin.


I just don't get NFT's. I don't. How many of your friends collect things? Like *really* collect them? Obsess about display cases and acid-free backing and all that shit? Not many right? Why am I supposed to believe that NFT's are no less of a niche thing?

And how the fuck is anyone supposed to believe that these minting events are actually bootstrapping something that will be coveted in the future? Collectibility is an organic story. Something might be collectible because a huge amount of the original issuance was destroyed or there were misprints, etc...etc...hardly anything is collectible because some fuckstick on Twitter ran a few prompts through Stable Diffusion.


NRC-20, NostrSwap and "Nostr Assets" are scams that exist only to steal your money. Do not fall for it. Tell your children.


Listening to the Ordinals episode of the bitcoin review podcast, how can you be against Drivechains and promote Ordinals? They have the same eternal shitcoin incentive misalignment. They are the same thing.


Indeed. Somehow they got tons of people to repeat that it’s somehow “decentralized” despite not being in any way decentralized. Quite impressive.


We live in a time when it's more socially acceptable for a child to be on
amphetamines than it is for an adult to smoke pot.
	-DrSkyentist, Nov 2015


I regret leaking that I am a cat. Now everyone thinks I’m a pussy.


Exploding pigs sound scary af 🙀 nostr:note1qg2e5xdp5nqc9qlh3nwhqh3ptx4snw8re3u0ps8e0x3anhyfh70s5muvpa


Wen OLYMPUS tho?


Shit my iPhone seven glitched and posted my note way too many times, sorry for the spam fam.


Most bitcoin "accessories" that you see for sale this black friday are pointless, overpriced, regular consumer products repackaged in premium branding.

You don't need a $150 kit to hammer seed phrases into washers. You need a hammer and washers and a letter punch kit, all of which you can get at Harbour  Freight for like $25.

You don't need a waterproof HWW case with custom cut foam. You need a Pelican 1120.

I COULD GO ON


YOU DONT NEED A COINKITE $30 INDUSTRIAL MICROSD CARD

nostr:nevent1qqs86pvl0k2rknqy2cnp80vcllra74s0ns206uxkmq9vptjkqwwvjdgprfmhxue69uhkummnw3ezuumpw35x7ctjv3jhytnrdaksygqnhj2ajgwgk6exeu65jjtymtuxlycjlegfy3yr6fngy7temqyf05psgqqqqqqsm8sdnt


WoS didn’t rug you.
The US government did.

Wake the fuck up.


Craig Wright hired a private intelligence firm to spy on hodlonaut, in an attempt to spin an appeal case narrative that he was part of a large, organized cabal devoted to destroying Wright's reputation. Because that's a perfectly normal thing to do.

https://twitter.com/hodlonaut/status/1726286758713737538

https://image.nostr.build/1a234986135e59e51fbf941ca8b56180efc6f8efed6acde6ce8161c16c958192.jpg

https://image.nostr.build/70fef3be137919c8de582192c152cb54c680be2886652866744b5ba7fd3da741.jpg


Why the hell do USB type A ports with 10Gbps exist

What next, we are going to run DisplayPort using USB4 over a USB-A to USB-C cable?


SEX is great and all but have you ever solved a programming problem that's stumped you for weeks?


I agree that what nostr:npub1xnf02f60r9v0e5kty33a404dm79zr7z2eepyrk5gsq3m7pwvsz2sazlpr5 is doing right now could lead to elevated force closes. I also agree that LND is shit.
But this does not justify nostr:npub1mutnyacc9uc4t5mmxvpprwsauj5p2qxq95v4a9j0jxl8wnkfvuyque23vg outright blocking zaps to them in my opinion. In no case should a wallet, especially a competitor, attempt to block payments to another wallet, with no option given to users to turn it off.

Hold invoices and stuck HTLCs are still going to exist, whether nostr:npub1mutnyacc9uc4t5mmxvpprwsauj5p2qxq95v4a9j0jxl8wnkfvuyque23vg blocks nostr:npub1xnf02f60r9v0e5kty33a404dm79zr7z2eepyrk5gsq3m7pwvsz2sazlpr5 or not. We need proper solutions to HTLC resolution in low-uptime wallets.


These two 💜🐈🐈⬛ https://image.nostr.build/40b90037fa269ce0b4c0d7d0bcc64459ce3c4ff6f63051f4074948a244663e1f.jpg https://image.nostr.build/145f3ea6464c0ab9fff3c356b13d3f696045c83991f53842d76fdd05e0144be6.jpg


mempool composition, in MvB
https://image.nostr.build/8ab10f8cb22158ba4fd00ddb37f3e7bd8ee931921af6918d7d2f42051af3a8a6.png


an LLM is just the views of another executed by a computer


The longer Wallet of Satoshi exists without being forced to add KYC, the more it seems to point to them being a honeypot.

Lots of user info to harvest there. Feds have done crazier things.


Good thing those app reviewers that make you jump through hoops to get "approved" for the "store" are there to protect you!

(Not a dig at apple, could be any of them)

https://image.nostr.build/02cd66d1ffacbcfbdf1caf6882f3beca5e5f3640049b00435ec288bc4c85275f.jpg


Nostr has a funding problem. Developers and infrastructure is severely underfunded and reliant on flawed economic models, and this could pose a risk to the future of Nostr as a protocol.

To understand it, we need to understand what resources are needed to make Nostr work, how they aren't funded properly and what could happen next.

# The costs of what makes Nostr work

Nostr works because:
1. Developers build clients on it
2. There is infrastructure to support clients

If there are no developers, there are no clients. If there is no infrastructure, clients have no purpose.

## The costs of developing a client, and the reliance on developers

Clients require time to develop the client, and money to run infrastructure for it.

Without developers, there would be no clients, and no Nostr.

Developers have lives and need to make money somehow in exchange for the time they spend. Developing a client is a significant cost, even for small ones (assuming 1 hr/day, no infrastructure costs and the average salary of a software developer, **$1500**) and needs to be covered somehow.

We have multiple models, all of which have large downsides:
1. Donations/V4V/Bounties:
   This model suffers from the problem that a minority pays for the majority, which will lead to the majority demanding exclusive benefits for their money or otherwise cutting off funding since they have no reason to pay.
   This also suffers from the fact that donations are unreliable.
2. Grants from OpenSats and similar non-profits:
  These suffer from the same problems as the donations model, but also suffer from the following problems:
    - the managers of these non-profits may have views not aligned with their donors, leading to misfunding.
    - that such projects are mostly stopgaps that add additional complexity to a direct donation model.
3. Paywalled features:
   It is very hard to find the balance between paywalling enough features to make money, and discouraging too many users from using the client. There may not even be such a sweet spot.
4. Cuts:
   It is extremely hard to balance these so that people don't complain, and it is likely that there will be forks of FOSS clients that remove these features by some users.
5. Paid clients:
   People do not want to spend a lot on services that they expect to be free or cheap, and spending $5/month on this client, $10/month on that client, so on won't scale, even though that is way less than the actual value they are getting.
6. Ads:
   Ads are usually underpaying and mostly make money for the ad companies instead of the client developers. Ads are also an invasion of privacy and may not be well received by some users.
7. VC funding:
   VCs put profit above protocol health, which may accelerate some issues that I will discuss later. They also may disincentivize the development of some apps (uncensored social media for example) for pushing their own agenda.

Even if we find some good way to fund clients, it doesn't end there...

## The cost of infrastructure

There are multiple types of infrastructure for Nostr, such as relays, services like Noswhere's search relay, push notifications, etc. All of these cost money to operate, and are the other half of what make Nostr work.

These have even more limited funding options, which have even bigger downsides:
1. Client funding:
   Clients already struggle on funding as I discussed in the previous section. This would mean infrastructure is even more underfunded.
2. User payments:
   Users do not understand the details and importance of infrastructure, and have no reason to fund it. Making this problem worse, infrastructure providers can falsely advertise their services, diverting money away from infrastructure that is higher quality and should be funded. This is already happening.
3. Grants from OpenSats and similar non-profits (*relays only*):
   Again, these suffer from problems specified in the last section about grants. These entities will likely want the highest value from their donations, therefore leading them to encouraging a few big relays than many medium sized ones. Since relays are more important infrastructure, and they could have more control, these entities can also exert more control over the network.
4. Data harvesting and selling:
   This would discourage people from using their providers, but this is likely going to happen to some extent. The issue is that it would not generate sufficient revenue for the amount of users it will drive away.

Both infrastructure and developers being underfunded can lead to issues that may kill the protocol, which I'll discuss in the next section.

# The risks of improper funding

## 1. The protocol fizzles out and dies without reaching critical mass

This is one of the less likely options since there will probably be people developing for the sake of it, but is likely. With client developers being underfunded and infrastructure shutting down, Nostr would become smaller and worse to use until it completely fizzled out except maybe a few people.

## 2. The enshittification of Nostr

This is the most likely outcome, and the worst one. As Nostr continues developing, developers and infrastructure developers will want to maximize revenue, so they will begin by making good products to attract users at a loss.

After they have a sufficiently large user base, they would slowly erode bridges to their competitors, only leaving what is required so that their users won't complain.

After this stage, it is likely that clients will start merging with other ones to make larger "everything" apps and kill the last bridges, turning them into proprietary walled gardens, returning us to where we are today.

# How do we fix this?

I have no idea. Please share your opinions if you do :)

Or, the most likely way for nostr to die.


Everyone read this

https://www.omegle.com/


yes

pic was a meme depicting reality


I fucking called it! The evil saylor arc is starting.


Derek told you about my intentions.
Ralf also told you this and instead you decided to ignore all that, so I’m not sure who’s the “bad actor” here.


India Swaps Russian Crude For Saudi Oil As Discount Dwindles

India Swaps Russian Crude For Saudi Oil As Discount Dwindles

            By Charles Kennedy of https://oilprice.com/Latest-Energy-News/World-News/India-Swaps-Russian-Crude-For-Saudi-Oil-As-Discount-Dwindles.html

India’s October imports of Russian crude oil were down 4% compared to the previous month, with increased imports from Saudi Arabia. According to https://ibcworldnews.com/?p=119098
, citing Vortexa cargo data, India imported 1.55 million barrels per day of Russian crude in October, compared to 1.62 million bpd in September.

https://cms.zerohedge.com/s3/files/inline-images/india%20ioc.jpg?itok=zn4nCpPT

The drop in October reflects a dwindling discount for Russian crude, which is frequently selling above the G7-imposed price cap of $60 per barrel, despite buying restrictions.

The fall in India’s Russian crude imports for October was balanced out by an increase in imports of Saudi oil. India took in 924,000 bpd of Saudi crude in October, compared to 523,000 bpd in September, IBC reported, citing Vortexa data.

India’s crude oil imports from Russia fell by more than 4 percent in October compared to September, according to figures compiled by energy cargo tracker Vortexa.

Total crude oil imports by India reached 4.56 million bpd in October.

India is the third-largest importer of oil in the world.

If the price is right, India has also said it would consider importing Venezuelan oil following an easing of U.S. sanctions.

"It is always good when more supplies come to market," https://www.reuters.com/world/india/india-may-buy-venezuelan-oil-if-its-cheap-minister-says-2023-11-01/
 cited Indian Oil Minister Hardeep Singh Puri as saying at an industry event, adding, "We will buy from wherever we can get cheaper oil."

On October 18, the U.S. Department of the Treasury lifted most sanctions on Venezuelan oil for a period of six months. Venezuela oil is heavy, sour crude, which has been in short supply. Despite the lifting of sanctions, the Energy Information Administration notes that due to “years of underinvestment and mismanagement”, Venezuela will “likely limit crude oil production growth to less than 200,000 barrels per day (b/d) by the end of 2024”.

      https://cms.zerohedge.com/users/tyler-durden

Thu, 11/02/2023 - 15:00

https://www.zerohedge.com/commodities/india-swaps-russian-crude-saudi-oil-discount-dwindles


Friendly reminder that it can always be worse… https://image.nostr.build/c426a5070249238aba2a2fc6d55893663e273f77095dc0f2ada7500a6d89f0df.jpg  nostr:note1ugtj0rkgjwyvf7e7hyrhfge39l4q7gn58p9n5l2we5ukuxf9ps0sv8lqvf


"Stop resisting, Stop resisting!" is one of the most instantly recognizable phrases of the new American century. When you read the words, you can probably still hear them shouted in your head, the echoing memory of a generational trauma, the indelible recollection of the moment that the citizen became subordinate to the state.


Good morning nostr,

We are about to enter the "then they fight us stage" and it is going to be fucking messy.

 - Build strong local communities. Improve your own skills. Stack relentlessly.

Then we win. 🫡


There are two viruses in that picture having sex. NSFW


wtf? https://i.nostr.build/60wa.jpg


Someone said some days ago in some NIP proposal discussion that we will run out of kind numbers because currently we're limited to 40000. Some weeks before someone else had complained that I had written somewhere that the kind number should be a `uint16`, which can only go up to 65536.

In the meantime, some people make NIP proposals that involve very different events, but that use just one kind number and differentiate events by adding `d` tags or by other tricks. That is justified in the name of _flexibility_: the idea is that by having a string in which people can write anything the protocol is automatically more flexible, extensible, powerful, magical.

But this is not true. Using strings to differentiate between what could have been differentiated by a number doesn't make anything more flexible, it just adds confusion and inefficiency. Take [NIP-58](https://github.com/nostr-protocol/nips/blob/master/58.md) for example. It's the NIP that defines **badge creation, award and acceptance**.

It makes sense for the badge creation to be _parameterized replaceable_ (kind 30009) and differentiated by the `d` tag, as each pubkey can create multiple badges, and it makes sense for the badge award to be a normal, non-replaceable event (kind 8), as badges can be awarded to many people and the awards never change. But it **doesn't** make sense that for each badge receiver to craft a list of badges they have accepted and want to display they have to use a _parameterized replaceable_ event (kind 30008) with a `d` tag set to `"profile_badges"`. Why this magical string?

I believe the idea was that people would be able to craft different badge lists. For example, they would use the `"profile_badges"` value for badges they want to display in their main profile, and some other value, for example, `"hidden_badges"` for badges they have accepted but don't want to display in their main profile, and `"rejected_badges"` for badges that they want to explicitly reject -- or something like that.

The idea makes sense, but does it really? We could have done the same with a kind 10007 meaning _profile badges_, kind 10008 meaning _hidden badges_ and kind 10009 meaning _rejected badges_. That would save disk space and bandwidth, it would make it easier for relays to index these events and, most importantly, it would make implementation simpler. In the world of `d` tags, every programmer that tries to implement creating these badge lists have to go to the NIP and hardcode the kind 30008, then look for the magical string that must be set at the `d` tag and write it, exactly like in the NIP, as a string, and add that as a tag to the event, the same is valid for when a client wants to support reading the tag lists. While in the multi-kind world you only need to hardcode one magical number. It's undeniable that `{"kinds": [10007]}` is a simpler filter than `{"kinds": [30009], "#d": ["profile_badges"]}`. You may say the differences are negligible, but I'm just trying to illustrate a principle.

I have the impression that in the minds of many programmers to be able to write a string gives them the impression that everything is more flexible and magical: "oh, I can write _anything_, while if the stuff is in kinds I would have to first get authorization from the NIP overlords". Maybe the NIP process can be improved, but ultimately this makes little difference. You can definitely write _anything_ in the `d` tag, but you can also write _anything_ in the `kind` field too, the actual requirement that exists, and that exists for both, is that others start using the exact same kind number or `d` string that you're using, and vice-versa, and there is no shortcut for that, you necessarily have to come to an agreement with others -- which is what the NIP process tries to facilitate.

We should use kind numbers as much as possible, and `d` tags only when absolutely necessary.


ⓘ This note has been removed for violating Fiatjaf Community Guidelines.


ⓘ This note just has the icon thingy on it, nothing special going on here - but go stack some sats you bitch


ⓘ This note violates nostr:npub12262qa4uhw7u8gdwlgmntqtv7aye8vdcmvszkqwgs0zchel6mz7s6cgrkj Community Guidelines for distributing false information about cats. The sacred committee of cats has determined that it is beneficial for them not to display the contents of this note on #Nostr


So many bitcoin influencers noting from primal. Pretty hypocritical considering all the “no blue checks” and “no custodial wallets” they note about. nostr:note165ywq7ms8kx8n2l7sg7d3ajp9wujja4av3tp04f57ljn8f6rc3rqcmemh8


I like to randomly put these notes, with a link to German language Bitcoin education, into shopping carts. The text means: Are you sick of inflation? What is sound money? #bitcoin is freedom #spreadeducation https://video.nostr.build/effb896e2014998d681d15a126e0bf7041e6c55d06cc554785b84ec8a5ebff45.mov


the mempool, over 5 minutes
https://minio.buyvm-lux-1.semisol.dev/static/nm/mempool.mp4


Until they realize the relay won’t work 95% of the time, is eating up their battery and cellular plan and doesn’t have much benefit.


Stacks is a shitcoin with its own token that the founder premined.

🙅♂


UMA is LN addressses but:
- incompatible
- with mandatory sender identification
- forced KYC
- with walled gardens (people can’t send or receive to you unless you are a “trusted VASP”)


David Marcus’ new standard:
- is not permissionless
- breaks compatibility with LNURL
- creates large custodian only closed gardens
- is hilariously complicated to implement
- requires the sender be identified
- could start turning over PII of the sender on payments to the recipient’s custodian

UMA can suck my dick


going back to build 23, dislike the design of current version of profile previews 💜


If I had a Bitcoin for every time the FBI said that, Satoshi would look poor.


A hack conceptualized by the deranged to unsuccessfully make Nostr work for private communications and violating the core of Nostr’s design principles


The face of someone that doesn’t use your shitty client made with high amounts of incompetence and lies :)


don’t be in the top 50k by followers? sorry, according to primal, your engagement is as good as a bot (and that’s fine, who cares, only the influencers deserve to show up on the trending page)

they aren’t incompetent after all, they have had to have a reason for this


Eden.nostr.land doesn’t block Tor :)


zbd is not nostr.
you have been fooled by a KYC app to let them have your keys and therefore the privilege of reading all your DMs and post as you forever while locking you in and not being actually decentralized.

your account is compromised.


Taler ded

https://image.nostr.build/d4076cf0a4cda28af01a95017566fa0ed4cd0baff3217be0c1bf75b031ddb4a0.jpg


We are at war, make no mistake.  Google “war machine”,  you get a pic of a marvel character.  Google “who runs the world”,  you get a Beyoncé song… they want you fat, lazy, depressed, dependent and uninformed…WE ARE AT WAR.

https://image.nostr.build/02579516b9a5d586d8cf7375734463ea5b4a291458347403b7c12a65c70c3097.jpg


verify your `getutxooutsetinfo` matches
https://uset.ln.semisol.dev/


EXPERIMENTAL ANDROID 14 RELEASE ANNOUNCEMENT

GrapheneOS is now based on Android 14. An experimental release based on Android 14 has been made available for broader public testing. Most of our features are already available. Certain minor features haven't yet been ported to Android 14. There may be more issues to address with the sandboxed Google Play compatibility layer to restore full app compatibility.

This release provides the full 2023-10-06 patch level for all supported devices along with the recommended security patches only included in Android 14.

Android 13 is no longer actively developed upstream and now only receives backports of the Android Security Bulletin patches, not the recommended patches included in the latest stable release of Android. Pixels are also now only supported via Android 14 and require Android 14 to achieve a patch level above 2023-10-01. Android 14 has had publicly available experimental releases since February 2023 and is already a mature OS. It also contains significant privacy and security enhancements which more than offset the attack surface from added features. These reasons are why we have so heavily prioritized porting to Android 14 and began to defer more and more of our other work until after Android 14 since around July 2023.

Please join #testing:grapheneos.org on Matrix if you want to help with testing the experimental releases.

The experimental releases are production builds of GrapheneOS signed with the official release keys. You don't need to reinstall the OS to test them and you'll continue receiving regular updates on the experimental releases via the
regular release channels. There will likely be a couple more experimental releases before we're ready to push out a release via the Alpha channel, Beta and then Stable as usual.

There are 2 ways to update to the new experimental release. You can either enable ADB within the OS and use it to override the update channel to the experimental channel, or you can sideload the update via recovery. Sideloading
the update via recovery is recommended if you don't already use ADB since it avoids needing to temporarily enable developer options and ADB along with temporarily trusting a computer with ADB access.

To install one by sideloading, first, boot into recovery. You can do this by holding the volume down button while the device boots to enter fastboot mode followed by selecting the Recovery option in the menu with the volume buttons
and then pressing power to activate it. You should see the green Android lying on its back being repaired, with the text "No command" meaning that no command has been passed to recovery. Next, access the recovery menu by holding down
the power button and pressing the volume up button a single time. This key combination toggles between the GUI and text-based mode with the menu and log output. Finally, select the "Apply update from ADB" option in the recovery menu and sideload the update with adb. For example:

[adb sideload felix-ota_update-2023100600.zip]

https://releases.grapheneos.org/felix-ota_update-2023100600.zip
https://releases.grapheneos.org/tangorpro-ota_update-2023100600.zip
https://releases.grapheneos.org/lynx-ota_update-2023100600.zip
https://releases.grapheneos.org/cheetah-ota_update-2023100600.zip
https://releases.grapheneos.org/panther-ota_update-2023100600.zip
https://releases.grapheneos.org/bluejay-ota_update-2023100600.zip
https://releases.grapheneos.org/raven-ota_update-2023100600.zip
https://releases.grapheneos.org/oriole-ota_update-2023100600.zip
https://releases.grapheneos.org/barbet-ota_update-2023100600.zip
https://releases.grapheneos.org/redfin-ota_update-2023100600.zip
https://releases.grapheneos.org/bramble-ota_update-2023100600.zip

To install the update over-the-air with the OS update client, enabling developer options, enable ADB, attach the device to a computer with ADB installed, run adb devices, accept the authorization prompt to trust the computer with ADB access and run the following command:

[adb shell 'setprop sys.update.channel experimental && cmd jobscheduler run app.seamlessupdate.client 1']

* Code Snippets above use square brackets remove but entering if copy/pasting.

SUPPORT FOR THIS RELEASE IS ONLY OFFERED IN THE TESTING ROOM ON MATRIX PLEASE DO NOT MESSAGE ME HERE.


so a friend of mine just sent me this. maybe this is old news but it's new to me. #holdyourownkeys
https://void.cat/d/E8HsYkq8EBi6weNbfVNrTq.webp


Why would you pay for nostr:npub18kzz4lkdtc5n729kvfunxuz287uvu9f64ywhjz43ra482t2y5sks0mx5sz ‘s cellar service if their relay stores events forever? For the privilege of being able to broadcast events with an older timestamp that make no realistic cost difference to new events?

Give your money to relays that don’t try to create the problem then sell you the solution.


eden.nostr.land offers permanent* retention without created_at limits for up to 100k notes without paying extra, with the option to buy more coming soon
*as long as you continue paying

just saying ;)


It's cool that you can compile bitcoin core to support fiat transfers:

`./configure --enable-usdt`

;)


good morning nostr 🤗


🤫
https://image.nostr.build/29ba8b492724899a6b16798448523cbde527e9e7cecfe254fdc9f2d9f870830d.png


I’m making a big investment in terms of time and money to make Nostr.land the best relay in terms of performance, scalability and feature set while staying sustainable (this is why one time fees suck) and being affordable. The current price was inadequate for that.


eden.nostr.land offers long term note archiving at no cost. :)


big architectural changes coming to nostr.land which will allow me to offer affordable and fast event archival, an actually affordable high quality aggregator and search in one connection

and working on noswhere.com scalability + tag search 👀


Ripple Won't Go Forward With Acquisition of Fortress Trust

"A few weeks ago, we signed a letter of intent to acquire Fortress Trust – we’ve since made the decision not to move forward with an outright acquisition, though Ripple will remain an investor," Ripple's CEO Brad Garlinghouse said.

https://www.nobsbitcoin.com/ripple-wont-go-forward-with-acquisition-of-fortress-trust/


regime police in Iran opened fire inside and outside a mosque today, killing and injuring dozens of people who were protesting against the brutal regime.

you may not see or hear what’s going on in Iran anymore, that’s because they make sure that their disgusting actions don’t make it out of the country.

they still fight everyday for their freedom, and get killed for even trying.


Dedicated archival relays make no sense and are a waste of effort and money. Storage is the cheapest thing to exist.

Eden will soon offer free 100k events per user and then charge you $1 per 100k events you are over with limitations (no file storage, no spam)


It costs at most $5 to store 100k notes for one year. (assuming you are already paying for a good quality relay monthly)
Pay wisely.


A majority of relay costs come from not the notes stored but the user count (time spent for server maintenance and the compute required to handle users)


nostr will not be an everything protocol imho and shouldn’t be one
there will be protocols for direct communication like simplex
there will be protocols for public information like nostr
there will be protocols for money like bitcoin and ln
and so on


Voting is a disaster and will continue being so.


It feels like everything has been said in the first 3 podcasts and now we're just regurgitating.


Would anyone be interested in a bounty for implementing support for not FCing a channel and letting the user decide if an HTLC gets stuck and a peer is offline for certain channels? I can trust some of my peers


Real talk you have no idea how sophisticated physical surveillance is…

You think you’re “anon”?

Lol that’s cute.

Have you been in an airport in the last 5 years?

You’re fucked.

Wake up.


Here to build freedom tech, and tools to help people get the most out of it

- eden.nostr.land: high performance paid relay
- nostrplebs.com: NIP-05 and nostr services provider
- wss://relay.noswhere.com: high speed and quality search
- new.nostryfied.online: easy backup of your events
- nostrnests.com: audio spaces
and the list goes on


WARNING: the lnbits.semisol.dev mint will be rugged soon (NOT nuts.semisol.dev)
withdraw your funds in the next 7 days


I propose removing the `description_hash` requirement from zaps as many have already started doing so with bare LNURL-pay.

I know that many nostr client devs haven't even checked this from `zap receipts` to begin with – your laziness was worth it!

Nostr client and zap server devs: What are your thoughts? Please give feedback in the PR 🙏

https://github.com/nostr-protocol/nips/pull/788


Introducing accelerated Instant Backups, brought to you by nostr:npub12262qa4uhw7u8gdwlgmntqtv7aye8vdcmvszkqwgs0zchel6mz7s6cgrkj

If you want your backup instantly, literally lightning-fast, you can use this:

https://new.nostryfied.online/

Thank him for this.


☠ ☠ ☠ nostr:note1fss9jj3vg7z2rx0evp7nrnwg0rcese674jehq00aejzx2ndymwcs37nznc


The new backup service will be lightning-fast, eliminating the need to wait.

We will also store your files for you, allowing you to broadcast them whenever you want.

It can't get any better, and it's coming very soon. nostr:npub12262qa4uhw7u8gdwlgmntqtv7aye8vdcmvszkqwgs0zchel6mz7s6cgrkj  🤜🤛 nostr:note1xf5t25jmalcnxwqpj6jgd2gge32gdx9syvwm36fqjxv5qtf5zw6skcpkml


Something big is being worked on 🤫•


A lot of talk about #ZBD today. There's only one thing that matters in this discussion. If you don't control your own npub/nsec then it defeats the entire purpose of #Nostr.


I’m genuinely concerned about how much more you value connections and being on the “right” but unethical side of some shitty companies over integrity


A custodial solution you refuse to use to yourself but freely recommend you to anyone else is a big red flag


This is not incompetence, this is not priorities. This is outright malice.

Please stop trying to deny the existence of any negative possibilties for the sake of not angering a person that claimed they made Nostr happen like they were all the devs or something


hmm primal still shows my media i thought i deleted from my nostr.build lmao


“…the freedom of Speech may be taken away, and, dumb and silent we may be led, like sheep, to the Slaughter.” https://image.nostr.build/4360ca662845dbb853257ab587b7421f1362bb7af84687735ec90f02eee63033.jpg


should I add a US relay to eden.nostr.land?


My man Pablo is adding nostr:npub1y27q6mdnjf0mkl3ev2nh7dqsk4yu3hyqmhzfz8tg3hdpwdmdfdlsczzps3 search to his Highlighter application. In the near future, you'll also be able to search for "highlighted content" via our web search interface. This is all done easily, thanks to the openness of Nostr.

nostr:nevent1qqsg2g32kaqmwzex44lag2x8y4gz8ewwt59nslrx0gds4kh4d9fev4gppemhxue69uhkummn9ekx7mp0qgs04xzt6ldm9qhs0ctw0t58kf4z57umjzmjg6jywu0seadwtqqc75srqsqqqqqp3lcc43


Anyone want to offer me a translator job from UK or US?

Figured it doesn't hurt to ask.


Hey ZBD, you forgot nostr’s value proposition: owning your own data !
🤣


Watching my boss regret the last 5 years of him bitching at his father, who is now terminal, and seeing him make every effort to spend time with him.

This is your simple reminder to tell the ones you love that you do, and to spend the time we have, cause tomorrow isn't guaranteed.


buy #bitcoin

follow for more top secret trading strategies


Imagine if to use PGP it had become normalized that you had to buy a specialized device from a PGP-focused company… This is basically where we have landed with bitcoin cold storage.


Nutminers need nuts to mine. These nuts will go to Semisol's nutmining pool.

lnbc21u1pj0egyusp5jc00j9px87ncmda3rynumm9u8ytr4je8p0jd5ahzywj2c62tvelspp55md6dqh53u0j6gr0pvx28g0t0l3ej6n70u50f8qgfdkacuu9y07sdq4gdshx6r4ypjx2ur0wd5hgxqyzjnccqpjrzjq2wyade0xm3ur6af3eyr2jr87euj3ncag8fxrnc6kavg9murjta02z709gqqs3gqqyqqqqlgqqqqqxgq9s9qxpqysgqrqd84kesn2ucmgswn0yvd267mn5ffzmnc8lhfq7nzyjc5wdqasm972ysprpcq799u5hr8rtdkpva5z78kn8jra2rx6tyxsarx4k332qp5ue8uq

https://image.nostr.build/7eb929f7ab7ee3ea4807dc45203cf049a6789f4984d01bf6da0e5b072dd95efb.gif


“ten minutes” ok well continue believing what you want to

you copied my and nostr:npub18ams6ewn5aj2n3wt2qawzglx9mr4nzksxhvrdc4gzrecw7n5tvjqctp424 NIP-05 service, wording and ToS nearly as is. You gave your customers an inferior service lacking even the ability to manage NIP-05s for the sake of capitalizing on the hype, and you never built it out fully afterwards.

I am building this because many people are telling me your search is inaccurate, slow and sometimes outright doesn’t work. I am actively working on giving my users a high quality product that is useful.


Tales from 4chan
photo_1988@13-07-2019_02-15-49.jpg

https://bae.st/media/54b13b0b52d4825a8c871d4320ab8662bea001fbe9935e278bd0c09f5d0f5a40.jpg?name=photo_1988%4013-07-2019_02-15-49.jpg


I'm always bullshit, #coffeechain We just have so much going on, it's hard not to be.

https://image.nostr.build/00d7d2b3914a0741188d781a576d537245c0229c8858466c98a6a87bc99b309a.jpg


Those censorship memes hit too hard. I got removed too 😞


I don't get the nostr.band strategy. I feel like they are just trying to:
- Copying others and passing the ideas as their own
- Burn money on ideas that won't make reasonable profit, unless they:
- Lock people into their products with their APIs, their browser, their appstore and similar, trying to find a way they can monetize users and clients using their monopoly and position

Nostr thrives because it is decentralized and people have choice. Maybe think twice before locking yourself into one provider.


For those that were at #bh2023 or downloaded my slides and were curious about nosWhere: I'm happy to announce that nostr:npub12262qa4uhw7u8gdwlgmntqtv7aye8vdcmvszkqwgs0zchel6mz7s6cgrkj just finished phase 1 of nosWhere for you all. You can now add our relay to your Nostr client to improve your search results.

nostr:nevent1qqsdvvmswg9dhn6dg3zhfad0qx7clxtutn9m6dtl0rkgexrxceucmesppamhxue69uhkummnw3ezumt0d5pzqg4up4km8yjlhdlrjc480u6ppd2ferwgphwyjywk3rw6zumk6jmlqvzqqqqqqy4rghhx


bend the knee to nostr:npub12vkcxr0luzwp8e673v29eqjhrr7p9vqq8asav85swaepclllj09sylpugg and you will be rewarded

isn’t that right nostr:npub12262qa4uhw7u8gdwlgmntqtv7aye8vdcmvszkqwgs0zchel6mz7s6cgrkj

building your own nostr client fixes this nostr:note15kwtvu6qtp0dkvrj5cgd22x5x5swges2jnclza0cajj022cs6d9qh7r8jr


yep. you either play by nostr:npub16c0nh3dnadzqpm76uctf5hqhe2lny344zsmpm6feee9p5rdxaa9q586nvr's stupid rules or you basically are suppressed from the view of 90% of normies on nostr that get fooled by a shiny UI and don’t truly care about censorship resistance.


#freeRalf #freeSemi

The way you make something stronger is by first breaking it. nostr:npub12262qa4uhw7u8gdwlgmntqtv7aye8vdcmvszkqwgs0zchel6mz7s6cgrkj broke nostr:npub12vkcxr0luzwp8e673v29eqjhrr7p9vqq8asav85swaepclllj09sylpugg so now fix it and make it stronger/better. nostr:npub1ezw0xm0w52rd4yfdg9zlw9qvwdy46alzelklkefptrd203m37tuq4djmeg is just too generous with the zapper and triggered the kill switch. So make a note and reset.  nostr:npub1ezw0xm0w52rd4yfdg9zlw9qvwdy46alzelklkefptrd203m37tuq4djmeg He’s just got a big zapper, can’t hate a guy that. Let’s remember why we are all here, not to fuss and fight, but to break shit and then fix it to make it better/stronger. #plebchain #nostr


#DeletePrimal
https://void.cat/d/QCjtDY3rHSHDJWUskD5BKj.webp
#nostr #plebchain #FreeSpeech #NoCensorship #SelfModeration


Content filtering is not a client’s job, I can do that myself. #primal 👎 nostr:note12s2lfp72adgkr9yxyewq94m7e7k2jkrxltake2gyv4mzwvsv6tssxg3l5m


Smart Vaults says that they "use" nostr, but they ask you to sign-up on their wait-list with an email address and follow them on X.  🚩 🚩 🚩 🚩 🚩 🚩 🚩 🚩 🚩 🚩

https://www.smartvaults.io


For some reason I became a temporary spokesperson for nostr, I don’t know why, but I don’t care, I’m not in this for the clout. Most of the shit i build, people do not use. I’m just happy I was able to build something that people actually like and use for a change. Everyone has played an important role, I don’t think it was a single event that made nostr what it is today. That’s what makes it special!


yikes. this is super cringe af.
no other way to put it. sorry.


Three years ago, I built an Umbrel node.
Last summer, I built a node from scratch.
Today, I finished my nostr:npub126ntw5mnermmj0znhjhgdk8lh2af72sm8qfzq48umdlnhaj9kuns3le9ll node.

I don't like recommending technology to people without fully having used it myself. I often tell people to use Start9 even though I only never "used" it in any production sort of manner. I only installed the OS, poked around the settings and marketplace a bit, then stopped using it.

That changes today. I will be migrating my Umbrel node over to my Start9 node as soon as Bitcoin finishes syncing.


Send nsecs to Google servers? Hell nah. They scan every single byte in those emails before it reaches your inbox IIRC


Pubkeys publishing adult content have previously been unfairly punished by being filtered away because they've been reported by someone else.


This guy reported me because I refused to promote his scam to all of you. He has done the same to approx 21 other users. Amethyst uses these reports as a signal to shadowban users without any further verification. 🤦♂

Download #Onyx

https://picsur.thesamecat.io/i/c077be0c-4496-4632-9da1-b012b263150a.jpg

https://picsur.thesamecat.io/i/b4dfd208-0e26-4c0b-837a-b5979e573b2c.jpg


Started a listr for the Amethyst Shadowban Realm lol

https://void.cat/d/TrjMd8YEHhHjDGgn2DXRwt.webp

https://listr.lol/a/naddr1qqvyzmt9w358jum5ypfksctydamkyctwypfx2ctvd5pzp89qh469qapddgsrr8qw84xx08y7q34fm3cw3m64c2g9ufq9ydqtqvzqqqr4xq6k457s

let me know if you find people who are autoblocked so I can add :)

#plebchain #vibecheckstr #amethyst #shadowban


You just don't like nut jokes, admit it already.


What is NIP-05 really?

If you look at [the spec](https://github.com/nostr-protocol/nips/blob/master/05.md), it's a way to map Nostr public keys to DNS-based internet identifiers, such as `name@example.com`.

If you look at Nostr Plebs:
> It's a human readable identifier for your public key. It makes finding your profile on Nostr easier. It makes identifying your account easier.

If you look at basically any client, you see a checkmark, which you assume means verification.

If you ask someone, they probably will call it verification.

## How did we get here?

Initially, there was only one client, which was (kind of) the reference implementation: Branle.

When it added support for NIP-05 identifiers, it used to replace the display name with the NIP-05 identifier, and it had to distinguish a NIP-05 from someone setting their *display name* to a NIP-05. So they added a checkmark...

Then there was [astral.ninja](https://astral.ninja) and [Damus](https://damus.io): The former was a fork of Branle, and therefore inherited the checkmark. Damus didn't implement NIP-05 until a while later, and they added a checkmark because Astral and other clients were doing it.

And then came new clients, all copying what the previous ones did... (Snort originally did not have a checkmark, but that changed later.)

## The first NIP-05 provider

Long story short, people were wondering what NIP-05 is and wanted it, and that's how [Nostr Plebs](https://nostrplebs.com/?utm_campaign=nip05-isnt-verif) came to be.

They initially called their service verification. Somewhere between January and February, they removed all mentions to verification except one (because people were searching for it), and publicly said that NIP-05 is not verification. But that didn't work.

Then, there were the new NIP-05 providers, some understood perfectly what a NIP-05 identifier is and applied the correct nomenclature. Others misnamed it as verification, adding confusion to users. This made the problem worse on top of the popular clients showing checkmarks.

(from this point in the article we'll refer to it as a **Nostr address**)

## And so, the scams begin

Spammers and scammers started to abuse Nostr addresses to scam people:
- Some providers has been used by fake crypto airdrop bots.
- A few Nostr address providers have terminated multitude of impersonating and scam identifiers over the past weeks.

This goes to show that Nostr addresses don't verify anything, they are just providers of human readable handles.

## Nostr addresses *can* be proof of association

Nostr addresses can be a proof of association. The easiest analogy to understand is email:

jack@cash\.app -> You could assume this is the Jack that works at Cash App.

jack@nostr-address-provider\.example\.com -> This could be any Jack.

## What now?

We urge that clients **stop showing a checkmark for all Nostr addresses**, as they are not useful for verification.

We also urge that clients hide checkmarks for **all domain names**, without exception in the same way we do not show checkmarks for emails.

Lastly, NIP-05 is a **nostr address** and that is why we urge all clients to use the proper nomenclature.

### Signed:

- Semisol, [Nostr Plebs](https://nostrplebs.com/?utm_campaign=nip05-isnt-verif) ([semisol@nostrplebs.com](https://snort.semisol.dev/p/semisol@nostrplebs.com))
- Quentin, [nostrcheck.me](https://nostrcheck.me) ([quentin@nostrcheck.me](https://nosta.me/89e14be49ed0073da83b678279cd29ba5ad86cf000b6a3d1a4c3dc4aa4fdd02c))
- Derek Ross, [Nostr Plebs](https://nostrplebs.com/?utm_campaign=nip05-isnt-verif) ([derekross@nostrplebs.com](https://nostrplebs.com/s/derekross))
- Bitcoin Nostrich, [Bitcoin Nostr](https://bitcoinnostr.com) ([BitcoinNostrich@BitcoinNostr.com](https://snort.semisol.dev/p/bitcoinnostrich@bitcoinnostr.com))
- Remina, [zaps.lol](https://zaps.lol) ([remina@zaps.lol](https://nosta.me/416ca193aa5448b8cca1f09642807765cc0ee299609f972df0614cfb8ea2f2b1))
- Harry Hodler, [nostr-check.com](https://nostr-check.com) ([harryhodler@nostr-check.com](nostr:npub18qxd7kmp6rg7hstrpcpw2fpjtyvaf7tazns07vrgqpdrce67x3zsrh0caz))


Good news, the w3c let us have a community area

https://www.w3.org/community/nostr/

This is going to be completely useless for most here, but there's certain good things it allows:

- you get a mailing list
- you get a wiki
- you can publish community group reports
- makes it *slightly* easier to register stuff such as uri schemes, eventually we'd like to get safe listed in the browser
- can document, spec or register some webby stuff, such as link headers, vocabs, did methods etc.
- patent and royalty free protections

to be honest nostr has a perfectly good system, so this wont be useful for most people, and it rarely allows pseudonyms, but hopefully it'll give us some extra strategic reach if we need it, and better we have it than someone else — feel free to join!


According to Nostr.band, I'm now over 10K followers across Nostr. That's wild. Thank you all for following me, Zapping me, and your continued support as we build https://nostrplebs.com and https://nostrnests.com. It truly means a lot.

It's been three and a half months, but it still feels all new and exciting. As I said during my talk at #Nostrica last week, I do this all for the plebs. For the Bitcoin plebs, for the Nostr plebs, to provide services and support to make Nostr better. I fully see Nostr's potential for the world. I know we're still early and there's a lot of work to be done to onboard the masses. That's why I do what I do and I fully love every single minute of it. 💜


💯 verified at #NostrPlebs
loving https://nostrnests.com/

thx #[0] & #[1] 🤙🏻💜


Fantastic talk by #[0], love his enthusiasm!


I support #[0] on “Plebs, not Pleebs”😂


My new preferred nostr client is https://snort.semisol.dev

Previously my favorite was https://snort.social, but after learning how they censored Semisol's zaps, it was a no-brainer to abandon Snort immediately.  That kind of censorship reminds me of the bird site, which I no longer want anything to do with.

As a bonus, https://snort.semisol.dev is much faster than snort ever was.


### The Nostr Nests UI Overhaul is here!

The user interface for https://NostrNests.com has been completely redone to be much more aesthetically pleasing and to increase functionality. You'll immediately notice the new bottom icon bar which now houses all of the Nests features: raising your hand to join to the stage, to speak, to edit your profile, to use emojis, to enable/disable your mic, and to leave the Nest. Soon, we'll be adding a Share icon! The moderation buttons, Nest configuration page, and profile setup page have all been updated too. Nests also now properly display the number of listeners in the audience to help you see how many people are tuned into your Nest. Top nests are displayed on the Nostr Nests homepage. Go check it out!

https://nostrnests.com/general

A special thanks to #[0] , #[1] , and #[2]


Nostr Plebs users: Have you added our private relay?

If you're a Nostr Plebs NIP-05 ID holder (all domains) you can add wss://relay.nostrplebs.com to your relay list. 🤙


We are chatting on Nostr Nests, come and hangout with us.

https://nostrnests.com/general


### Nostr Plebs Spaces is rebranding to Nostr Nests

We originally started Nostr Plebs Spaces to ease the transition for users coming from Twitter. Today, we are rebranding to Nostr Nests since we would not like to reuse the Spaces branding. (and the name is more fitting!)

We have also introduced the ability to link your Nostr public key and some improvements that could reduce choppy audio in bad connections.

We will be hosting a nest on https://nostrnests.com/general for the launch.

We will also in the future introduce linking your Nostr Plebs ID and Nostr login.

**What will happen to my rooms?**
Rooms will not be transferred. Please recreate your rooms. If your room name has been taken up by someone else, contact us.

**What about my profile?**
Your profile will not be transferred over. You will need to set it up again.


Good evening, Nostr! Nostr Plebs Spaces is going down for maintenance. 👀


Nostr Nests are happening over on our beta client https://spaces.nostrplebs.com/general

Come join us.


**NIP-69 is being proposed to use the Stacks blockchain and BNS .btc name system for Nostr Names**

The proposal states to use the Stacks "Bitcoin Name System", which has nothing to do with Bitcoin, but uses that name for name recognition only, as a new *"Nostr Names"* implementation. This is being proposed as an improvement to NIP-05 IDs. As a NIP-05 ID service provider, I will agree that the NIP-05 is not perfect, but NIP-69 is **not the solution**.

The Nostr Names NIP-69 proposal states that NIP-05 is flawed because:

* DNS names are controlled by the state and 3rd parties
* they're expensive, need to own a server, ssl, etc
* you need to be skilled to do it

The first key point is true, DNS names are controlled by third parties. That's something we can't fix yet.

The second point about being expensive is completely false. Domain names are fairly cheap and you don't need to pay for SSL certificates, nor do you need to own a server.

*For example: derekross.me costs me $12 a year. The server is a Rapsberry Pi 4. The SSL certificate is free from Let's Encrypt.*

The third point is partially false. The skill required isn't incredible, but it probably is too much for the average person to handle. This leads us to third party services such as NostrPlebs.com providing ID services for customers. This can lead to some centralization and trust, but we will reach a point where certain providers are better than others. Some providers will allow anyone to register, some will charge for this service, some will provide additional perks and support to their members. As time progresses, clear leaders in this new industry will merge and providers will be known and judged by their reputations, services, and support.

"Nostr Names" states the following are benefits to using NIP-69:

* use the centralized service btc.us to register a name
* learn how to use Stacks Clarity language and programmatically register your name
* use the Stacks blockchain, run a Stacks node

So, it sounds like you need to use a centralized service and you need to be skilled to register a NIP-69 Nostr Name, doesn't it? I thought these were issues that NIP-69 was trying to solve for NIP-05?

It costs about $10 for 5 years, so a BNS name is cheaper. That's a plus.

**But you still need to use Stacks.**

I like the effort here as NIP-05 is not perfect, but I'm sorry, I'm going to say no to this one.

[Source](https://www.newinternetlabs.com/blog/nostr-names/)