<unnamed>

has anybody already built a free version of pocket, the article bookmarking and reading app that dissapeared?
- browser extension to save a link
- article text gets parsed automatically
- stored somewhere in the cloud or on nostr
- web, ios, android apps to read all your stored articles
- bonus: social features to share articles, follow other user's bookmarks
- bonus: text to speech via open source TTS models
- bonus: TTS transcriptions are shared between users once created

2026-09-07 18:06:59 UTC

- reply

your expectation is maybe incompatible with the solution that people want

2026-09-07 17:51:36 UTC

- reply

I don't think it's that different. also there are many different ways to design this, not all suffer from the same issues that you've described. you seem to have given up on this. that's ok but I hope others didn't.

2026-09-07 17:18:32 UTC

- reply

you basically said "it's not going to work because not everybody will implement it at the same time". but that's how every feature was built on nostr.

2026-09-07 15:28:44 UTC

- reply

I think it's largely a related issue.

2026-09-07 15:28:03 UTC

- reply

do you think it's possible? curious about your solution and why it wasn't considered.

2026-09-07 15:26:41 UTC

- reply

do you think there is no solution?

2026-09-07 15:26:18 UTC

- reply

no, do you?

2026-09-07 14:54:22 UTC

- reply

I'm also aware of the *NIPs

2026-09-07 14:46:55 UTC

- reply

I'm not saying this to offend you anon. You're probably a great dev, and I'm probably using your software. I'm grateful for all the work you're putting in.
This isn't meant to criticize you personally. I am simply stating an observation as a user who has been around here from the very early days. I'm pointing at a problem that has to do with how the collective works. It's not enough to sign JSONs and pray, a serious project needs direction and a vision.
Nostr, as a sum of its developers and visionaries, had this for a while. It doesn't have it anymore. I hope we can discover it again.

2026-09-07 14:41:40 UTC

While I'm at it – another proof that nostr devs aren't serious about adoption is still the lack of key rotation.
I get it. It's a big task and can't be solved by any individual client, it needs to be addressed on a protocol level. I'm also aware of the that were put forward. But you know what? Writing markdown and pushing it to the nips repo isn't enough. It's step 0.
This is a typical issue that would require devs to come together and all pull in one direction. It likely would have needed a champion who is willing to push for this change, talk to people, explain it to everyone, and actually care. Similar to how we push for bigger changes in the Bitcoin protocol. It takes time, and it takes a serious effort. Once again, nobody has taken over that role because nobody really cared enough.
Back in the day, there were massively big users who would've loved to join nostr – but didn't do it because of a lack of key rotation. Why would anyone with so much to lose join a protocol that can permanently rekt your identity with a simple XSS bug that exposes your nsec? Nobody listened to them.
This was brought up over, and over, and over again. Nobody cared enough.

2026-09-07 14:29:15 UTC

@nprofile…uz3y has a serious issue with muting users – it can't be that hard. The only client I haven't had issues is @nprofile…4hdy
Many nostr kind-0 devs don't realize how big of an issue this is for their users because they don't put themselves into the shoes of ordinary users who don't want to deal with this shit.

2026-09-07 14:26:41 UTC

- reply

which clients allow this?

2026-09-07 12:23:51 UTC

- reply

cool!

2026-09-07 11:33:21 UTC

- reply

you realize that liquid is a 11 of 15 federation?

2026-09-07 11:32:51 UTC

- reply

of course it makes sense

2026-09-07 09:37:23 UTC

Liquid hack explained.
Liquid has confidential transactions that hide the amounts for improved privacy. A bug in how these transactions are validated caused inflation of Liquid BTC (L-BTC) and allowed hackers to empty the entire side chain.
Liquid nodes don't see the amounts of a confidential transaction, so to make sure that the transaction is still valid and doesn't cause inflation nodes check something called a balance proof and a range proof.
The balance proof establish that sum of the input amounts equal the output amounts, i.e., that "x L-BTC going in and x L-BTC going out". But there's a catch. Only relying on a balance proof isn't enough. You also need the range proof.
The range proof establishes that a hidden output amount falls within a positive range. That means a valid output must be at least 1 L-sat and at most 2^64 − 1 L-sats. Range proofs make sure that you can't mint "negative L-BTC".
Why is this even necessary? Remember, the amounts are hidden and a hidden negative amount would allow extra positive outputs to balance against it. Without a range proof, a transaction could say "I've put 1 L-BTC in, and I'm taking two outputs out: one with 4000 L-BTC and one with -3999 L-BTC)."
This is going to cause a disaster in a little bit.
Once the balance proof, the range proof, and other validations pass, a transaction is regarded as valid and can pass consensus. However, because especially the range proof is computationally expensive, Liquid nodes cache the result of a successful range proof in memory. Essentially, the node remembers "I saw this range proof before and it was valid, all good!".
In order to recognize the same range proof later on, you need to assign a label to it. This is called a cache key. This cache key is the actual cause of the bug.
The way this cache key was constructed allowed two different transactions to collide on their cache key. Essentially, one valid transaction (1 L-BTC in, 1 L-BTC out) had the same cache key as an invalid transaction (1 L-BTC in, 4000 L-BTC out).
Here's the hack: the attackers submitted the valid transaction (1 L-BTC in, 1 L-BTC out) first. Liquid nodes verified this transaction successfully, created a cache key called REKT and stored it in their cache. Then the attackers carefully crafted a second invalid transaction with (1 L-BTC in, 4000 L-BTC out) that created the same cache key REKT.
Instead of validating the second transaction and realizing that it printed money out of thin air, Liquid nodes found it in their cache and said "hey I saw this transaction before, everything is fine" and that caused the inflation.
The attackers then took their 4000 L-BTC and withdrew 4000 BTC onto the Bitcoin base chain.

2026-09-06 12:27:04 UTC

- reply

Luke hates many things

2026-09-06 12:00:13 UTC

- reply

this just shows how little you understand what normal users care about

2026-09-06 11:51:58 UTC

I'm amazed someone would buy this crap but hey, I'm all for it, hope the price goes up a little more
#nevent1q…2pah

2026-09-06 11:49:38 UTC

- reply

the problem is it doesn't work reliably

2026-09-06 11:47:00 UTC

- reply

send butt, I'll sign

2026-09-06 11:46:33 UTC

- reply

personally I don't care about how the block works as long as it works reliably.

2026-09-06 11:45:36 UTC

- reply

helth

2026-09-06 11:45:17 UTC

- reply

tbh I don't know. I mute psychotic sickos but every now and then they reappear across clients, like STDs.

2026-09-06 08:23:54 UTC

- reply

yes it barely works though :/

2026-09-06 08:23:38 UTC

- reply

gm mostly

2026-09-06 08:23:30 UTC

- reply

40 hpw?

2026-09-06 08:23:03 UTC

- reply

🙏

2026-09-06 05:08:36 UTC

- reply

god I wish
#nevent1q…ewgx

2026-09-06 04:21:30 UTC

- reply

I'm probably in nostr's top 0.01% users but this is one of the reasons I come back less frequently than I used to.
you can talk about permissionlessness as much as you want, but you can also simply choose not having to deal with a bunch of assholes on a daily basis.
#nevent1q…9e9h

2026-09-06 04:18:21 UTC

- reply

I have a dozen sad little lonely fucks (grown men) that are obsessed with me like little gay school girls – but with paranoid schizophrenia.
I imagine this happens to anyone with more than a few followers.

2026-09-06 04:16:20 UTC

- reply

nostr is full of reply-guy psychopaths that you can't block and there isn't a single client where muting works reliably, let alone across apps
#nevent1q…9x70

2026-08-27 13:42:20 UTC

- reply

join our open community call for this months' nutty updates!
#nevent1q…wlrr

2026-08-26 13:43:25 UTC

- reply

how am I supposed to send this shit out?

2026-08-20 08:21:24 UTC

we're all bitcoin red team
#nevent1q…3uts

2026-08-11 09:01:48 UTC

- reply

blocked for excessive retardation and bip110 brain damage

2026-08-11 08:01:57 UTC

- reply

at least I'm not a loser who fell for the most retarded scam in bitcoin's history

2026-08-10 17:02:56 UTC

Say It — private, local text-to-speech for macOS
Open models 100% on-device, speak text from any app with a hotkey, and even clone your own voice.
Infinite voices. Free & open-source.
Listen to the video 🔊
https://blossom.primal.net/e649070d3a79dc06f35d8dee63b0b218cc1059928834aaeb3523e118c183e41a.mp4
Download for macOS: https://sayit.sh
This is my contribution to the war against paid apps that should be free. I hope you enjoy it!
Leave a star on GitHub ⭐️ PRs are welcome!
https://github.com/callebtc/sayit

2026-08-09 12:37:16 UTC

dickbutt.jpg
|
|
3 yrs later
|
|
V
luke dashjr
becomes a
shitcoiner

2026-08-08 23:08:24 UTC

🚩 Bitcoin Red Team Update
We're continuing a large-scale security review of the Bitcoin open-source ecosystem.
25 Bitcoin developers around the world have been working on this task non-stop for 108 hours.
https://blossom.primal.net/0a31b776061ffea8d5d1f544232bd40fdf2c2ed9812ca0a78d165483b8717f3f.png
We scanned 501 projects and produced 7,958 findings, of which 1,280 are rated high or critical (H+C) severity.
Our goal is to provide the most useful information. Based on feedback from maintainers, we've recalibrated our severity ratings and are now stricter about what we classify as H+C.
https://blossom.primal.net/a1c91429c176f784c66117ae1b19a4ae468336aa33131e517fec509bbe7d8df3.png
The share of all findings rated H+C increased to 16.2%, and the share of findings with a reproducible proof of concept increased to 24.7%.
That means our accuracy is improving.
As we harvest the low-hanging fruit, we're now focusing on improving harnesses, deploying better cyber-capable models, and probing more sophisticated attacks.
https://blossom.primal.net/ce6dde791e2f5468d7942c410092726655714af84765c8c855cf1c135d742800.png
Our AI spend remains consistently high.
Our cumulative spend has passed $58K as we add more inference sources. Notably, we've started using cyber models from OpenAI and Anthropic.
These models are producing incredible results, but the vast majority of our spend (74%) still goes to Kimi K3.
Kimi K3 remains the top choice among our hunters, but we've also seen a significant increase in the use of Qwen 3.8 over the past few days.
https://blossom.primal.net/4da137b276eba405c01bd5d58101e0f29f0bbd11c6192916bc87506ed81267cb.png
Our goal is to strengthen the Bitcoin ecosystem and increase the resilience of our infrastructure in the age of AI.
To achieve this, we're conducting the largest red-teaming campaign in Bitcoin's history.
As a Bitcoiner, I am immensely proud of this.
We're sharing all our findings with developers for free.
This would not have been possible without the generous support of organizations like @nprofile…5h0z and donors like @FPuklowski and @nprofile…8a9z.
You can help keep the Red Team alive by donating to the OpenSats Red Team Fund here: https://opensats.org/funds/red
Last but not least, our reporting rate is picking up. Thanks to our outreach team, we've reported 29.4% of our findings so far.
We're also rolling out new infrastructure to deliver these findings to projects more quickly and securely, while improving how we incorporate feedback.
Stay tuned!
https://blossom.primal.net/c52088aa3fb6c6692c54c791be525a0a99476ccfa54f3831943fb83f6481e62f.png

2026-08-08 20:55:06 UTC

it's finally over!
the bip110 cancer is finally removed from bitcoin!
what a massively inconsequential waste of time!
https://media1.giphy.com/media/v1.Y2lkPTc5MGI3NjExcWpwYTZmcWY3NHU4eTk0bDVrMGlpdzdxeTkyZzVqM2Y3dzJ3eXdueCZlcD12MV9pbnRlcm5hbF9naWZfYnlfaWQmY3Q9Zw/KYElw07kzDspaBOwf9/giphy.gif

2026-08-08 19:37:31 UTC

fork off
gg

2026-08-08 12:07:25 UTC

https://blossom.primal.net/d8e95767cd28ec66b144b464eace61e19990ae82f41df28a5c889d0b3be946f4.png

2026-08-07 16:55:20 UTC

- reply

Turn off your BTCPay Server immediately if you can’t update right now.
#nevent1q…u76c

2026-08-07 16:02:35 UTC

gm
https://blossom.primal.net/4c57a10cabc9c81985443ab783795713cd10117c5c01380aba30c059a78f1fa7.jpg

2026-08-07 15:52:59 UTC

🚨🚨 URGENT: BTCPAYSERVER 🚨🚨
There is a critical vulnerability that is being actively exploited on BTCPay Server which can lead to loss of funds.
Update your BTCPayServer to to 2.4.2 or turn off your BTCPayServer now.

2026-08-06 17:52:27 UTC

🚩 Bitcoin Red Team update 55 hours into the campaign
We're now 24 people working around the clock.
We've scanned 425 projects so far and have produced 1029 high+critical (H+C) findings.
https://blossom.primal.net/9c1af29b7a362e981cdac51f88186552e3e0e9c9fbc18fae5047d12015ad8565.png
We generated 6700 findings so far and are hitting 7.7 projects per hour.
Our H+C rate per person per hour is back at ~1 as we work off a massive backlog and as the team grows and naturally divides up roles.
We have hunters, wizards, outreachers, sugar daddies, and gigglers.
https://blossom.primal.net/4dc7b8b0c997a50ba2c60f8d69add016370cd0a76838b2244799c8f385b4d252.png
https://blossom.primal.net/ed41ccd68901b5a794084466bc552e57e41f7d026d5b91da39dd8b4fe0064ef7.png
Our H+C ratio is at 15.4% of all findings, increased by a percentage point compared to yesterday.
This is great, our accuracy is stable, and even slightly increasing. We're trying out best to reproduce all critical findings in local regtests before reporting them to projects.
https://blossom.primal.net/fd24c2f5f8057510eeca48735c208268303795feab03085cbd8c2e6de2659b04.png
Our biggest bottleneck is outreach. Most projects don't have a SECURITY .md in their repos (19.5%). Only 13.1% have an email in there.
We're working on better ways to reach folks. In the mean time, the best thing you can do as a project maintainer is to leave an email address in your repo.
https://blossom.primal.net/0c7e7ca2e032b79a7f84a4cbb775fbe2e609bb9ab5ca6dfa3dd0c8bd0adf5885.png
Thank you to the sponsors and donors who cover the costs of this campaign and help to keep it alive.
Specifically @nprofile…5h0z, FPuklowski, @nprofile…8a9z, and everyone who has donated to OpenSats Red.
https://opensats.org/funds/red
An incredible team of some of the most hard core Bitcoiners I know have assembled and dedicated their last days to this effort.
We've seen shit.
I don't want to reveal anyone personally, they can choose to do that themselves, but I think the way that people came together to join forces was and still is the most beautiful part about this entire program.
It makes me very hopeful, seeing so many people step up and give their time and energy to Bitcoin, especially during times of pain.
We're not done yet.
https://blossom.primal.net/833de63c0d642b97bc6662803604b1173578a16528b1908be8448830351668a2.png

2026-07-31 12:37:51 UTC

This is worse than any previous Bitcoin exchange hack. It is arguably one of the worst things that could happen.
The popular hardware wallet COLDCARD has a faulty random number generator (RNG). Funds are being drained from ordinary users’ hardware wallets as you read this.
Users first reported to Block less than 24 hours ago that funds were moving out of their wallets. The exploit was most likely discovered with the help of AI. Block has confirmed that the RNG is broken. You know what that means.
There are likely already multiple attackers competing for the affected BTC. Many more will join very soon.
Nobody knows how much BTC is affected.
Nobody knows how many users are affected.
This attack has only just begun, and it will continue until all affected BTC has been drained unless users secure their funds first. Inevitably, many Bitcoiners will not hear about the incident early enough to respond in time.
I am truly saddened for everyone affected, especially those who may have just lost their life savings.
The worst part is that they did everything right.

2026-07-04 09:24:14 UTC

‼️ This week, the US House of Representatives passed the KIDS Act.
If it passes the Senate, it will be the end of the open Internet. Platforms will be forced to implement age verification. You will have to upload your government ID to post on social media.
The goal is to fully track every internet user and to implement global KYC regulation for free speech.
It was never about the kids. It’s about governments having full control over what you do and say on the Internet.
Posted something bad about your government 5 years ago? Liked a post criticizing the regime? Retweeted a post against the official narrative? Watch how protecting the kids becomes fighting terrorism or hate speech pretty soon. You will be found and you will be prosecuted.
There is no free speech in this world without a free Internet. The Internet must remain open for anyone, with or without government identification. You have a human right for privacy and for free speech.
This is a coordinated attack. Age verification laws are being proposed all over the planet, everywhere at the same time.
We must fight back.

2026-06-12 09:35:49 UTC

code the future

2026-06-09 14:09:44 UTC

- reply

Cashu payment requests. We've been sending nuts between wallets for a long time!

2026-06-01 18:05:05 UTC

bitchat is free
runs on nostr
built with zero funding
has 3M downloads
🤣🖕

2026-06-01 17:51:42 UTC

- reply

code or stfu?

2026-05-30 15:32:52 UTC

- reply

you seem to be an intelligent person, I wonder why you chose to become a reply guy. waste of your intellect.

2026-05-30 15:23:13 UTC

- reply

so you have nothing to say?

2026-05-29 20:54:34 UTC

- reply

tell us how you do that with Google cloud or Amazon nitro

2026-05-29 20:53:45 UTC

- reply

Can't, it's a one-way street. Hyper scaler TEE's don't die though

2026-05-27 08:12:52 UTC

Nobody else seems to care but I think nostr finally needs a Hash Chain event kind or tag that is enforced server-side:
- To add a new event to the chain, you MUST reference a previous event. If the referenced event does not exist, you get an error.
- Only one event can reference another event. If an event has already been referenced before, you get an error.
IMO (almost) solves the biggest issue with nostr which is the fact that you never know if the data you have is complete and it allows atomic updates of data. Suggestions for improvements of this idea welcome.

2026-05-26 08:50:10 UTC

Wish there was more going on in Bitcoin.

2026-05-24 15:39:47 UTC

do you remember how and where you learned about nostr? 👇

2026-05-24 12:47:51 UTC

shitcoiners love to dunk on bitcoin L2 issues when we discuss grownup topics like scaling issues, privacy, and decentralization.
“just use zcash/monero/whatever”
bro. blockchains don’t scale. the only reason you can pretend otherwise is because you have no users. nada. niente.
you can play your stupid games and pretend like your coin is an alternative but if you’d every grow up, you’d face the same scaling pressure as bitcoin does. and then what?
until then, we literally don’t give a fuck about your tech as long as only a dozen people can use it. if you had any meaningful adoption, you’d have zero ideas how to scale it beyond that.
just stop. you’re not only not in the same league. you’re not even playing the same game as we do. you’re being ridiculous and you don’t sound as smart as you think you do.
end of rant. fucking shitcoiners.

2026-05-23 21:14:07 UTC

Elephant in the room: all Lightning infrastructure is centralizing around 1-3 companies that offer zero privacy.

2026-05-23 17:51:42 UTC

insane
#nevent1q…5q6a

2026-05-22 12:34:10 UTC

Qwen3.7 Max is very good

2026-05-21 14:57:59 UTC

- reply

nevent1qqsrqz9yj4vfqan9yup2sshpq3mnz30xzjdnfqhga7varglh5t7sjgcuvdlkz

2026-05-21 14:52:48 UTC

OCEAN is an attack against Bitcoin btw

2026-05-19 10:59:21 UTC

- reply

Shut the fuck up and fork it you negative IQ BIP 110 retard

2026-05-18 20:01:13 UTC

Been off for a bit and you guys are considering on-chain zaps?
Do you even know what a fucking UTXO is?
Are you completely retarded?

2026-05-07 23:18:55 UTC

- reply

prompts

2026-05-07 13:58:56 UTC

what's the most complex machine humans have built?

2026-04-06 07:37:49 UTC

bitchat iOS banned in china 🖕🫡🖕

2026-04-03 08:17:17 UTC

- reply

@nprofile…dd2n @nprofile…zxch not all url params are bad xD

2026-03-25 16:02:18 UTC

please be true
https://blossom.primal.net/be7c5ebf15af87956605d4fb6e878a5cf0dba0f2b67028f4fd745f5e1e2322aa.png

2026-03-24 16:48:23 UTC

- reply

https://stats.andotherstuff.org/

2026-03-23 11:16:39 UTC

- reply

#nevent1q…xt8m

2026-03-13 10:41:47 UTC

https://blossom.primal.net/fbf225c4c0682ff943a5983070e2aa72bd41984577a3ad00673208176a15b784.png

2026-03-12 09:39:50 UTC

very cool opengraph preview image by @nprofile…5qez
https://zeusln.com/e/cashuBpGFteCJodHRwczovL21pbnQubWluaWJpdHMuY2FzaC9CaXRjb2luYXVjc2F0YWRgYXSBomFpSAAQeTfbDMhlYXCBpGFhGQQAYXN4QDQwYzg5YjQ5MTVjYzNlOTI2YzU4MTlmODAzMzk2OGRhZTE3ZTc5MmRiMDEyMTMwZDc4MmRkMzgwZTdiOWI3YzJhY1ghAuA-k0Q_FgdrDZg4tomIahjBns8dZBl80HjrGhh5O1pnYWSjYWVYIMI4PRqiZ3rmS9rrsbzreGE2d1EAWKSyUpgzN-OOOZaNYXNYICa4P3v5TMmimgDvnBZCaRSMOhIN85YUBjogAjes7sZSYXJYIKkbFL2GOmq7v2w3K4sUsuMBJiBPlu4HZxwPn9vJ7bpE

2026-03-12 08:25:17 UTC

Google has open-sourced A2UI – a UI language for AI agents
It allows agents generate user interfaces instead of only text.
→ Agents send a JSON description of UI components, and the client app renders them with its own trusted widgets.
The benefits:
- declarative UI format (JSON, not code)
- safe: only approved components can be rendered
- framework-agnostic (web, Flutter, etc.)
- supports incremental UI updates
So agents can "speak UI," while the application keeps control over security and implementation
https://github.com/google/A2UI https://blossom.primal.net/43ebf6180d0354cb5ca3635feb43161b1d47514748a59c758e0e1b3dd627bed3.jpg

2026-03-09 17:32:14 UTC

why do people run reply bots... on nostr?