tal

I've been considering enhancing the credibility of the @nprofile…077t and @nprofile…utq7 by developing an open-source verifier. This verifier would fetch & compare messages from the mailing lists to their respective Nostr accounts. Every X hours it would ensure all messages have been published and remain unaltered, then sign a "sync validation signature" with the validator nsec and publish. This approach could provide stronger assurance that no additional layer of moderation exists in the cloned mailing lists. What are your thoughts on this? Any ideas on how we can feasibly implement it? Perhaps only reasonable with nsecbunker? @nprofile…k8hv

2023-08-02 12:55:37

- reply

Commando & Bookkeeper is a great combo. See this video: https://www.youtube.com/watch?v=0EiA1pJGI4M

2023-08-02 12:50:37

That's odd. I've just discovered that the long-form event tagged summary on Coracle displays some random note instead of the correct one. In contrast, Amethyst shows it correctly. Does anyone know why this could be happening?
@nevent1qqsxpy2ugd377k3a760lpthkzlppmeltxqezgff4qy5ngermaz6ay3cpxfmhxue69uhhyetvv9ujumn0wd68ytnzvuk8wumn8ghj7mn0wvhxcmmv93mhxue69uhkumewwd68ytnrwg4cp9t7
@nprofile…942n
@npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn

2023-08-01 00:21:52

Verifying my #BOLTFUN account on Nostr
My Maker Profile: https://makers.bolt.fun/profile/1944
Join our FUN community of builders and designers
#[0]
#BuildOnNostr #BuildOnBitcoin

2023-07-07 16:58:00

- reply

Yes.

2023-07-07 16:54:48

- reply

It might be interesting if we could interface nsecBunker with an affordable, simple signing device capable of validating the policies on its own. This seems more straightforward than VLC for Lightning. Anyone doing this?

2023-07-04 01:41:10

- reply

I understand @npub18kz…x5sz point. High-cost services will only be available to a select few users who pass the stringent reputation test, which is acceptable. But why not implement both options? Why not allow users to pay upfront (a concept I'll call "zapfront" 😄) to specific service providers (based on reputation), and also signal a permission for a delivery of results via an encrypted DM?

2023-07-01 12:57:45

- reply

Trust it

2023-06-27 16:03:49

- reply

Is it? 😄
#nevent1q…257y

2023-06-27 15:59:07

- reply

Just a joke, lots of my twitter friends are getting that warning now hah

2023-06-27 15:14:32

Is it only me in nostrjail? 😢 😢
https://void.cat/d/XWpHkovsFVKy8Gm4iJVMfC.webp

2023-06-22 16:07:59

- reply

Congrats @npub1l2v…ajft! 795441 is a great birthdate! 🎉

2023-06-21 11:31:44

- reply

That's very cool!
Still cool to see an email about Bitcoin & Nostr sent to the Bitcoin-dev mailing list and being cloned to Nostr :)
Is the real Antoine Riard on Nostr?

2023-06-20 02:14:01

- reply

The one mentioned in @npub1wlh…90xk message

2023-06-20 02:12:17

- reply

It helps generating much less boring QR codes, try it yourself:
https://qr.autobtc.ai

2023-06-19 19:52:33

- reply

Hi @npub1tsg…htk4, could you suggest an alternative mitigation approach for that specific attack?

2023-06-19 18:52:49

Want one of these as well? you can generate your own at https://bolt12.tattoo or https://qr.autobtc.ai
Please be patient, it's being processed on a self-hosted GPU 😄
https://nostr.build/i/92d45261bbdd0e7cb7fef1711790304c2aa15c715597c1f7fe8272b20359e47d.jpg
https://nostr.build/i/22adc3eb75c0dc2f04c360e6e4432010c9f04458dfaa373c99339b4d9e82c9db.jpg
https://nostr.build/i/f50b420f49a0cb71827e87a173ec405f01929b9067a86a229c807161bd2bf0a8.jpg
https://nostr.build/i/b0d723bcbef1160b3dd78bbdf9d0df8bc6017dbd0b4b2aa3b31c533d73091442.jpg

2023-06-15 14:02:42

- reply

Isn't store distribution the main reason? Couldn't compiling a version-pinning browser together with an embedded default PWA link as a native be a solution?

2023-06-15 13:58:10

What are your thoughts about PWA version pinning browsers (as a solution for the "malicious update" risk compared to native apps)?
Ultimately everyone could compile a VPB (version-pinning browser) with a default link to their PWA and upload to the app store🤔
@npub1xts…kk5s

2023-06-14 17:32:01

Dynamic thread data on @npub1j3t…4gll (like thread summary, authors, total messages, and so forth) is now captured in a long-form content event (NIP-23) and linked from the thread event.
- It's displaying beautifully on Amethyst (thanks @npub1gcx…nj5z )
- Long-form content on habla.news is visually appealing; this inspires me to enrich it with all thread's AI-generated message summaries.
- I aim to endorse social clients integrating nip-23 references in archive threads. If you're building a client, please consider this feature! :)
- Should I broaden the scope and develop a general "mailing-list to nostr" app? Are the relays up for it? 😉
#nevent1q…0fe0

2023-06-14 16:36:52

#note12fp…l6ch
Testing highlighter on a summary of a thread from the lightning mailing list

2023-06-14 12:26:53

- reply

Yep, I used both the a tag and nip-19 naddr code.
Seems like Amethyst doesn't correctly show the latest update (last "created_at") and habla.news does @npub1gcx…nj5z

2023-06-14 11:46:50

- reply

That was my go-ahead to test Amethyst, and honestly, it has left me speechless😮 @npub1gcx…nj5z
This is how it pops up in Amethyst. It's not bad, but some "compact version" flag that strips away all the images clutter could be a cool. What do you think?
https://void.cat/d/Na9RhjyafgWWvYtHNmnJG8.webp

2023-06-14 10:09:45

- reply

Is there any social client that supports embedded long-form editable events in kind-1 notes?
(Like the one I published here: #nevent1q…0xu4)
@npub1r0r…q9ac
@npub1gcx…nj5z

2023-06-12 00:45:37

BOLT12 TATTOOS ARE COMING 😆⚡
(check it with your bolt12 supporting wallet ... hmm only Spark wallet?)
https://void.cat/d/WzH69NuCc4b7RVjpxXrY65.webp
https://void.cat/d/B289KV6bRks1i2nuqPmqHG.webp

2023-06-10 17:26:47

- reply

Cool! It seems like Parameterized Replaceable Events (NIP-33) is just the thing I've been looking for. If I understand correctly, all I'd need to do is ensure a unique d-identifier for each summary - hash(thread_note_id) could do the work. Having some attached flag that prompts clients to only show the contents, sidestepping all the "referenced event" extras, could be really neat. Is this nip widely adopted by the common clients/relays out there?

2023-06-10 13:57:10

- reply

Of course, let's have a chat about it! I've been mulling over whether we really need to go as far as implementing another client. wouldn't it be neat if we could tweak things at the protocol level so that it fits nicely within notes? What's your take on this?

2023-06-10 13:47:56

I'm in the middle of setting up live mirrors for the mailing lists at:
@npub15g7…08lk and @npub1j3t…4gll . My goal is to have AI-generated thread summaries that "auto-refresh" with each new message posted.
Here's the hitch though. I'm not certain if there's a way we can tweak an existing note while keeping all the engagements (replies, zaps, likes and all) intact. If that's a tall order, maybe we can consider something along the lines of "ndynamicevent:<>"? The idea is to flag a section in a note that points to a different "dynamic" note, one that we can update on the fly. What do you all think about that?
Just throwing it out there for some of the nostr experts:
@npub1l2v…ajft @npub1zuu…c2uc
@npub180c…h6w6
@npub1xts…kk5s
I really appreciate all the insights. It's helping me get up to speed with what nostr can do.

2023-06-10 01:59:10

What are your thoughts on the idea of incorporating BYOAI (Bring Your Own AI) capabilities into nostr clients? I personally find it incredibly useful to have thread summaries readily available before diving into the content/replies. It could also provide personalized notes suggestions just without the annoying ads. I'd love to hear your perspective on this!

2023-06-10 01:43:11

- reply

Yes.

2023-06-10 01:15:18

- reply

Wow, what a great journey you had!

2023-06-09 19:29:03

After the successful debut of the Bitcoin Mailing List on Nostr, I'm thrilled to share that the Lightning Mailing List has now also joined the platform. ⚡
@npub1j3t…4gll
2023 threads involving multiple authors come with AI-generated summaries.
I've decided to share the workings of this project. The parsed mailing list threads data & AI summaries, presented as JSON files, is now accessible on GitHub. You'll also find the NDK-driven code that handles Nostr publishing there. It's a weekend project, so the code might reflect that! 😅
(Mailing list crawler & parser code to be added soon)
https://github.com/plebos/nostr-mailing-list-publisher
@npub1l2v…ajft
I hope these resources spur further community-driven projects. As always, I look forward to your feedback and thoughts. Let's keep this momentum going! 🚀

2023-06-09 14:24:02

- reply

Amazing

2023-06-08 21:59:40

- reply

I haven't done so yet, but considering the positive feedback, I'm planning to set aside some time to neaten up the code and bundle it into a single service. At the moment, it looks quite like a weekend side project.
Initially, I used Python for the mailing list crawling and parsing and I moved on to JS when I've found out about NDK. I plan to publish it shortly after I finish up with the Lightning mailing list as well.

2023-06-08 20:45:52

- reply

I was connecting to multiple relays and publishing all threads from 2011. Ideally, I would want the rate limit to be abstracted out so that publishing blocks until it has actually been published to 'k' out of 'n' relays.

2023-06-08 20:16:11

- reply

I looked into a few options and NDK stood out as the simplest and best built. It is really tough to spot any issues.
I had to go through some nips and work out the exact tag symbols to use, which I think could be avoided. Also, I couldn't catch and handle the rate-limit exception from outside the library code.

2023-06-08 19:54:59

- reply

So you can navigate directly to the thread event from any message? noted for future threads.

2023-06-08 19:39:04

- reply

The harsh reality for developers is that once you begin exploring the world of uncensorable, programmable money and social network, turning back becomes almost unthinkable.

2023-06-08 19:35:25

- reply

Thanks!
We can now tag here you archive profile @npub1d7e…3exj 😄

2023-06-08 17:07:30

- reply

I hope you generate an offer and not a bolt11 invoice 😄

2023-06-08 16:39:36

- reply

🔥 🔥

2023-06-08 16:11:24

I've been dabbling with Nostr packages lately and decided to experiment by creating a real-time mirror of the Bitcoin Mailing List on Nostr, going back to 2011👴
@npub15g7…08lk
To help catch up on discussions, threads from 2011 and 2023 with multiple responses include AI generated summaries 🤖. If this sparks interest, I might expand this feature.
Each sender has an archive account for easy access to all their messages and stats 📬. The best part is that there's no moderation here - I believe in client-side filtering.
Considering making it two-way: zapped notes could bounce back to the mailing list based on popularity. 🔄 What's your take?
Please note, due to rate limits, it's not on all popular relays. However, for those of you who run a fancy relay and would like to store a backup, I can provide the full npubs whitelist🔒
Lightning mailing list is coming next!⚡️
Using @npub1ndk…qfy4 for this was straightforward, shoutout to @npub1l2v…ajft and the team! Feedback is welcome, let me know your thoughts!
@npub1qgw…7y7n
https://void.cat/d/UZpkYKpLJZ9rSHVMF61eZa.webp

2023-06-06 13:22:51

Are there any stable relays (paid is also fine) I can use to upload few Kb's of text (lots of notes) without getting rate-limited or npub-limited?

2023-06-04 14:48:45

- reply

That looks great 🔥 🔥

2023-06-02 04:00:33

- reply

The Bookkeeper plugin has arrived at
@npub1lzm…2q9x
as well ✨👀
Connect your browser to your
@npub1jg5…6n8n CLN
node and request the bookkeeper plugin as if you were 5 years old. With the commando plugin your node can securely forward the output, now even parsing zaps courtesy of @npub1xts…kk5s!
And finally, export all to any #nostr relay.
In need of a break from Lightning? Create a fun image of Satoshi! 👤
https://youtu.be/0EiA1pJGI4M

2023-05-31 14:39:47

- reply

Definitely, that was my first idea. But I'm pondering if there's a method that fits this scenario better. Instead of providing an app access to all decrypted dms, how about granting access only to particular necessary (unencrypted) keys? It'd also be a more precise and secure way to share private data across apps.

2023-05-31 14:25:14

- reply

Additionally, this approach simplifies sharing user's private data across various apps, while maintaining ongoing user consent.

2023-05-31 14:16:05

- reply

From my viewpoint, the relay doesn't need to implement signing or undergo any changes. To put it into perspective with my current situation, user's browser is storing private node data, say, a CLN rune. Whenever a user switches a browser or clears the local storage, they're required to re-enter the data.
The workaround I've considered involves my app generating a "vault-store" event. The user's extension would then encrypt it, sign it, and broadcast it to the relays.
Following this, when the user logs back in via nostr, my app could request the extension to decrypt the value and re-store it in the browser's local storage.
What do you think?

2023-05-31 13:58:05

- reply

Fascinating! is the code publicly available?
My concern is it's aimed more towards power-users with dedicated hardware running the nsecbunker daemon.
I've been envisioning something simpler to kick things off: a "Vault data" event kind ({vault_key -> encrypted_data}), which can be stored on public relays. Apps could then pull all npub's vault keys and request continuous read/write permissions for specific keys through an extension.
This approach eliminates the reliance on the browser's local storage as the "long-term" memory for personal data, as everything can be restored from the vault.
It's a basic idea in need of more thought

2023-05-31 12:52:32

- reply

Is it a new relay implementation for Mac? wouldn't something like a new event for an encrypted key-val and some work on the extension be enough?

2023-05-31 12:22:27

- reply

That's really neat! I just want to clarify a few things - it seems like the nsecBunkerClient has to stay online and listens out for "note signature requests", right? And then, it approves these requests based on a certain set of rules? Where are these rules stored? Do you have plans to evolve it for more complex rule sets? (for example, "a specific npub is authorized to post on my behalf for the next hour only and a max of 5 notes")
However, I think what I'm searching for is slightly different. I'm envisioning something like a private vault (think Amazon's style, but implemented on nostr relays). My application would then ask the extension for read/write permissions for a specific key in this encrypted vault. After a user logs in with nostr, the app could ask for access to some of the user's private data, pending the user's approval.
Down the line, this could be integrated with nsecBunkerClient. In this scenario, you could allow another npub access to your private vault. The client would manage the decryption and encryption for that user, following a set of specified rules.

2023-05-31 11:43:50

- reply

So, when I'm talking about a "client", I'm mainly referring to AutoBTC.ai at present. But down the line, we might see other clients cropping up. These potential clients could be designed to request permissions for reading specific values from that secure vault.
If there's no existing solution for this, I might just put forth a NIP to address it.

2023-05-31 11:36:53

- reply

Take a look at the beta version over here: https://autobtc.ai @npub1lzm…2q9x
Right now, private data, like a rune to connect to a CLN node (along with some other user preferences) is stored in the browser's local storage. But I've got my eye on expanding it to a multi-rune/macaroons data storage system. It'd be killer if users could log in and out from different browsers, and their client could securely pull this data from a dedicated "Nostr-vault". Any thoughts?

2023-05-31 11:10:41

Hey Nostr experts,
I'm on the hunt for something akin to a secure, private info vault that works over Nostr relays. Anything more advanced than "self-dm" around?
I'm trying to build something where the user can "export" their local (private) browser storage to this vault, and it automatically loads up when they sign in with Nostr. Any suggestions?

2023-05-31 11:01:31

- reply

Amazing! It's gotten so easy to integrate nostr :)
Going to test it soon!

2023-05-31 10:40:53

- reply

I'm fine-tuning a model on these mailing lists currently, shouldn't be hard to one-way publish on nostr with an attached summary per thread!

2023-05-24 13:45:13

- reply

You don't have to share with OpenAI using LLaMA.
It's already possible to run it in a browser environment🤯(currently only the new chrome afaik):
https://mlc.ai/web-llm/

2023-04-22 22:19:59

Six years ago, Google informed me I was part of the exclusive "0.1% Club". How should I celebrate my membership?
https://nostr.build/i/9a48a3b2cc2d672fabfd00f8d870a19a4762336ce1c24edd1752e52564a96e54.png
https://nostr.build/i/ae6c0e1aa42648b77143b51bf1b5ffb1689ab4d0ed95e11ed607ff7a14c2480d.png

2023-03-29 23:51:32

https://nostr.build/i/nostr.build_9daed9c40beb13afedd1371b1908f5e7c47bc19801c79a815d9c9d540474ff13.jpg
👀👀

2023-03-17 01:07:08

I don't think it's a good idea to rely on NIP05 providers for verifying the pubkeys of Nostr accounts. Instead, I suggest maintaining a list of signers who have independently verified the identity behind each pubkey. This way, nostr clients can display the number of verifications from your personal list of trusted signers. What do you think? I'm considering writing a NIP proposal for this

2023-03-17 00:38:10

- reply

Send a lightning payment to a node on the other side of the world -> teleport yourself there faster than the htlc 🤝

2023-03-10 03:28:39

If you're searching for a way to save on mobile data usage and enhance your privacy when using nostr, consider nostr-py-proxy. It now filters out duplicate notes and large images on your server, rather than on your mobile device, to reduce data usage. Additionally, it only exposes the IP address of the server to all relays, regardless of your mobile location, to enhance your privacy.
https://github.com/plebos/nostr-py-proxy
#[0] fyi

2023-02-20 12:43:12

- reply

2023-02-20 12:42:05

"Nostr zapping accident" is the new "boating accident"

2023-02-20 12:34:47

- reply

Does it really matter with zaps?

2023-02-20 12:33:46

- reply

It used to be astral for me a month ago, but snort took the lead. Multiple clients compete on users with great features and UI and without keeping the data hostage is the future!

2023-02-20 12:31:09

- reply

I zapped myself exactly 21M BTC for testing purposes, and some clients couldn't handle it and showed an error haha

2023-02-20 12:29:25

Snort.social became an amazing web client!

2023-02-19 19:32:59

- reply

What happened to your bird profile btw? full nostr mode?

2023-02-19 19:28:33

- reply

Zaps between two WOS wallets, doesn't actually touch their node in any way

2023-02-19 19:27:32

- reply

Why do you assume it's a zap? the client wouldn't choose the zap way if you don't signal to support it.

2023-02-19 18:43:37

- reply

You don't even need to pay routing fees to game it!
Watch that note again in a minute for a proof

2023-02-19 18:39:49

- reply

When will we start seeing a market for signed zap notes? lol
Celebrities would sell signed zap notes with high amount invoices for much less sats 😅

2023-02-19 18:05:36

- reply

Yea, now look at my note and you can see your "paid" zap, thanks for experimenting with me!
Clients should do it only when you actually pay, so don't expect it to happen normally!
I'll zap you some sats

2023-02-19 17:49:02

- reply

Astral doesn't support zaps yet, you can try snort.social

2023-02-19 17:30:10

- reply

Do you use a client that supports zaps?

2023-02-19 16:48:36

Lets make it interesting - I'll zap 1000 sats for every 1M BTC zap request on the original note untill the 21M BTC goal 😃
1MBTC = 100,000,000,000,000sats
#[0]

2023-02-19 16:14:39

- reply

What about this?
It's a normal bolt11 invoice, I need you to just click on the zap button, and generate an invoice, not paying it. it requires a client that support zaps such as #[3] or #[4] .

2023-02-19 15:47:56

- reply

I'm in Bitcoin & nostr since 2005

2023-02-19 15:37:36

- reply

PV!

2023-02-19 14:54:34

- reply

#[3]

2023-02-19 14:11:22

- reply

*pays

2023-02-19 14:10:48

- reply

So why don't you receive it directly to your node then? it's not your money if it pais unnecessary routing fees :P

2023-02-19 13:59:51

- reply

What client is it?
Anyways, ok lets make it 10K then

2023-02-19 13:30:27

Does anybody want to participate in my experiment? just click on the zap icon of that note, set the amount to 21M sats, generate the invoice and don't pay it (well, unless you insist) and you'll be listed in the zaps list anyway

2023-02-19 13:16:19

Zaps != sats actually moving on the Lightning Network
Zapper reputation and weighted zaps sum?
@jb55

2023-02-19 12:45:24

- reply

I agree, zaps are amazing! Just worth mentioning that similarly to likes it can also get manipulated

2023-02-19 12:29:50

- reply

Damus testflight frens, I did an experiment, how many zaps my dog received? it crashes snort.social on my account :)

2023-02-19 10:56:18

https://nostr.build/i/nostr.build_3357742475d5deb7f2484ba000bef56d88c9100476a2475045fbe17332f3d712.png
My dog reaction to me saying "zaps" (with some midjourney touches)

2023-02-18 23:16:27

- reply

Thanks! I can see your invoice, but it seems like a normal payment and not a zap. what client do you use?

2023-02-18 21:48:51

- reply

If you try to zap me now, you'll see a gigantic QR contains the whole zap invoice, and it would only work if you don't have too many relays configured (otherwise the invoice bypasses the description length limit)

2023-02-18 21:44:51

Is anyone getting zapped with Core Lightning? I've updated lnurl-commando to support the zaps server specification, and cln-zapper to work over commando. The only remaining challenge is to generate a hashed description invoice and overcome the length limit. I could use an external database as a workaround, but I'm wondering if someone has already found a solution for this?
#[0]

2023-02-18 21:44:43

2023-01-24 01:36:02

- reply

Every 🤙 counts!

2023-01-24 01:34:50

- reply

🫂

2023-01-24 01:30:51

#[0] you have to run your 🤙-bot again to welcome #[1]'s wave 😀