FOLLOW
nQuiz
npub1nqu...23sn
nQuiz - a question based learning platform, gamified with nostr and Bitcoin
FOLLOW
MESSAGE
SATS
😎
234 days ago
234 days agoβ€’β€’β€’
Back to reality after SEC-02! Here's what I worked on with @npub1t5a...ahcl:
β€’ Implemented NOSTR admission into @Chain Duel P2P games β€’ Drafted a NIP to allow more granularity on zaps β€’ A lot of talk about how to close the gap between lightning clients and nostr clients β€’ Proof of concept NOSTR client that facilitates the creation of social proof for public payments through zaps @npub1qf9...auu5 β€’ Learned a lot form the rest of the cohort and their projects
Stay sovereign >> #SovEng
πŸ‘€
247 days ago
247 days agoβ€’β€’β€’
I still maintain that alot of the recent issues around clients only reading from the top 5 relays would be alleviated by having http relay. Managing WebSocket subscriptions is a pain, I'd much rather just shoot out http requests to the different relays that a one off note may be found in.
Just like a website could show 100 images from different domains, we can fetch 100 notes from different relays with http reqs. I don't believe the narrative that http relays would impair client perf.
247 days agoβ€’β€’β€’
Yes. WebSockets have been the most annoying part of Nostr development thus far. Just had to refresh Primal a few minutes ago because the WebSocket connection was broken. 🫠
247 days agoβ€’β€’β€’
Any well known relays that already supports http ?
247 days agoβ€’β€’β€’
Not, yet. I'm going to make a very simple open-source HTTP relay that anyone can spin up in like 5 mins. We'll let the chaos begin 😈
247 days agoβ€’β€’β€’
247 days agoβ€’β€’β€’
WebSockets have their place when realtime communication is necessary. But the vast majority of Nostr clients don't require realtime communication, so why force developers to jump through the hoops to set up a full websocket subscription interface?
🧑
253 days ago
253 days agoβ€’β€’β€’
πŸ‘€πŸ‘€πŸ‘€
253 days agoβ€’β€’β€’
quite strange descriptions
253 days agoβ€’β€’β€’
Lorem Impsum: enters the room
253 days agoβ€’β€’β€’
We're working on this right now, we just deployed an initial version 30 mins ago, lol
Should be finished in a few hours!
253 days agoβ€’β€’β€’
Is this a joke?
253 days agoβ€’β€’β€’
253 days agoβ€’β€’β€’
We're literally working on this right now! Also the Lorum Ipsum. Ready in a few hours
253 days agoβ€’β€’β€’
253 days agoβ€’β€’β€’
I was going to say the same xD
302 days agoβ€’β€’β€’
Every account can have a metadata "event" which includes info such as name, profile picture, bio etc. Every event has a "kind" number, which kind is a metadata event?
#nips
285 days agoβ€’β€’β€’
kind 0
294 days agoβ€’β€’β€’
294 days agoβ€’β€’β€’
No way for them to know that, most old events are gone
294 days agoβ€’β€’β€’
Even if they are there, there's no guarantee the created_at will be accurate
It''s better than "trust me bro" but not as good as timestamp attestations
How many clients implement NIP-03?
294 days agoβ€’β€’β€’
#asknostr
294 days agoβ€’β€’β€’
Even if they are there, there's no guarantee the created_at will be accurate
It''s better than "trust me bro" but not as good as timestamp attestations
How many clients implement NIP-03?
294 days agoβ€’β€’β€’
True, didn't even think of that!
294 days agoβ€’β€’β€’
294 days agoβ€’β€’β€’
@Gigi - should it be the created_at of the earliest found event, or should one instead scan only for NIP-03 timestamped events?
294 days agoβ€’β€’β€’
it wouldn't be available for "all profiles" if the latter.
Maybe a two pronged approach..
"First seen: " "Confirmed:"
294 days agoβ€’β€’β€’
#YESTR
294 days agoβ€’β€’β€’
Did mine manually moons ago. Would love this as well.
😎
295 days ago
295 days agoβ€’β€’β€’
GM #Madeira #SovEng
296 days agoβ€’β€’β€’
If there are any Nostr developers that are attending BTC Prague and haven't let me know yet, please let me know ASAP! We're trying to make Prague an incredible conference for Nostr content. From Dev Hack Day, to the Nostr booth in the expo area, to content on the main and side stage at the main conference.
295 days agoβ€’β€’β€’
We'll be there
295 days agoβ€’β€’β€’
295 days agoβ€’β€’β€’
He DMed me last night πŸ₯Ή
295 days agoβ€’β€’β€’
295 days agoβ€’β€’β€’
🀣 hopefully not. Looking forward to seeing you again soon πŸ«‚πŸ«‚πŸ«‚
295 days agoβ€’β€’β€’
It's gonna be awesome!
295 days agoβ€’β€’β€’
See you in June!
😎
299 days ago
299 days agoβ€’β€’β€’
Ahoy, folks! I'll be going to SEC-02 soon in Madeira and plan to focus my energy on evolving #NIP05 to provide signed metadata. Why? Because I see this a key bridge between the old world and the new world. The NIP is still a WIP. You can read it here:
😎
299 days ago
299 days agoβ€’β€’β€’
#SimpleX killing it with the new v5 . 7 update.
#cybersecgirl #privacy #simplex
300 days agoβ€’β€’β€’
so, i finally understand why NIP-42 is not working for most clients
- most clients are nearly impossible to configure to test on one relay
- most relays don't support NIP-42
- only replicatr and khatru support NIP-42
so for the time being, us CLI bound relay devs are in a bind, and thankfully, we have people who get what is going on and are going to fund clients that work with our relays... or, mine, in particular
because without auth
there is no private business use case
and without relays with auth
there is no clients with auth
and there is no private business use case
and you all cry about adoption and you are not nagging your relay and client devs to actually FUCKING IMPLEMENT NIP-42 i don't know how fucking many times i have to repeat myself with this
IMPLEMENT
NIP
FORTY TWO
300 days agoβ€’β€’β€’
300 days agoβ€’β€’β€’
it's a really simple protocol
any reason, relay sends "["AUTH","challengesdring"]"
any time client receives this message, it signs a message:
tag with ["relay","wss://relayaddress"] tag with ["challenge","challenge"]
and sign it like a normal FUCKIXNG EVENT
GITRDONE guys, seriously, just fucking finish this shit because we can't make money running relays without you cunts implementing it properly nor the relay devs, why does everyone still fucking praise strfry when the project is DED?
300 days agoβ€’β€’β€’
hell, it's the weekend, i bet i can add NIP-42 to #nostrudel this weekend, in fact, i double dog dare myself to do that
i'm so sick of this shit
308 days agoβ€’β€’β€’
All 9 #nquiz games now use the first 6 chars of the hex key to colour code your avatar and hence identify and protect your nostr identity
Thanks to @hzrd149 for the initiative
#soveng
😎
309 days ago
316 days agoβ€’β€’β€’
Nothing feels better than the sovereign micro-payment system you've been quietly working on starts bringing in the cash with zaps. You'll see more of https://nimo.cash after SEC-02
316 days agoβ€’β€’β€’
If you want the invite code please DM me
316 days agoβ€’β€’β€’
invite code? πŸ‘€
316 days agoβ€’β€’β€’
I will send by DM
311 days agoβ€’β€’β€’
Thinking about adding NIP-88 (Recurring Subscriptions) support to noStrudel https://github.com/nostr-protocol/nips/pull/866
Would anyone be opposed to paying about 4000 sats / month for access to the "next" version of noStrudel? I'm not set on any particular price, I just need some subscription tier and benefit to test the integration πŸ˜€
310 days agoβ€’β€’β€’
Is there a list of current wallets which support NIP-88?
πŸ‘€
310 days ago
310 days agoβ€’β€’β€’
In its current form the nip only describes how the subscription would be setup and managed. its not too clear on how a wallet could handle payments, although I imagine it could be easily done using NWC or a reminder and manually paying
310 days agoβ€’β€’β€’
Thanks for all the feedback on this, although it might be a while before I implement NIP-88 in noStrudel. I've got a bunch of stuff I'm already working on in the next version and I cant let my self get distracted Still need to finish, NIP-42 and outbox model
311 days agoβ€’β€’β€’
Thinking about adding NIP-88 (Recurring Subscriptions) support to noStrudel https://github.com/nostr-protocol/nips/pull/866
Would anyone be opposed to paying about 4000 sats / month for access to the "next" version of noStrudel? I'm not set on any particular price, I just need some subscription tier and benefit to test the integration πŸ˜€
310 days agoβ€’β€’β€’
#yestr
310 days agoβ€’β€’β€’
Let's go!
311 days agoβ€’β€’β€’
Go for it
311 days agoβ€’β€’β€’
I am opposed. Charge more! Nostrudel fans love nostrudel
310 days agoβ€’β€’β€’
as a relay #devstr it's pioneering support of NIP-65 is essential
i want @hzrd149 to have no reason to do anything but keep making it more awesome
he can also build out more blossom as well, this is also good
311 days ago
πŸ«‚
311 days ago
311 days agoβ€’β€’β€’
SIGit is a decentralised document signing tool
The base product will be free and FOSS
#soveng #sigit
267 days agoβ€’β€’β€’
Bye bye docusign
πŸ‘€
336 days ago
338 days agoβ€’β€’β€’
I have a specific requirement for zap.store that no relay provides out of the box, custom indexing multiple fields for NIP-50 full-text search (and rejecting certain event kinds).
I thought of customizing the fiatjaf golang relay framework but didn't want to learn new tooling just for this.
@Gzuuus pointed me at Bun.sh which is a powerful JS toolkit with built-in websockets and sqlite, and I basically got a relay implemented in under a day... very cool.
This will eventually index all software releases on zap.store, and I'm thinking of making this same server implement @hzrd149-Blossom, keeping copies of all the indexed artifacts.
#zapstore
336 days agoβ€’β€’β€’
πŸ΄β€β˜ οΈ
336 days agoβ€’β€’β€’
Blossom + a configurable relay would be perfect for a self-hosted relay
338 days agoβ€’β€’β€’
I use it as a nodejs replacement but hadn't seen the web server framework stuff, nice!
Search is a big topic, we need to become much better with search. Especially profiles, content and custom fields.
You could also store the app releases on a blossom media server and just publish the sha256 hash.
338 days agoβ€’β€’β€’
Signed metadata is the most important thing but I also want to host files
338 days agoβ€’β€’β€’
O fuk you did it! Amazing πŸ”₯πŸ”₯πŸ”₯ are you gonna open source the relay code?
338 days agoβ€’β€’β€’
Yes for sure! It's quite custom and suboptimal code at the moment but good as reference
338 days agoβ€’β€’β€’
Amazing! definitely I will collaborate on the project πŸ‘Œ
338 days agoβ€’β€’β€’
That's neat sir! πŸ‘€πŸ‘€πŸ‘€
πŸ‘€
336 days ago
πŸ‘€ Glacier-waterfall Ventisquero Colgante, Chile πŸ€™
#GrowNostr #Uncharted
πŸ‘€
337 days ago
337 days agoβ€’β€’β€’
DISTRIBUTED COGNITION AND OTHER STUFF TRANSMITTED OVER FOOTSTEPS
337 days ago
337 days agoβ€’β€’β€’
Pro Tip: Besides a small test transaction you can also send the actual #bitcoin transaction for 1sat/vB with Replace-by-Fee and then confirm your funds appear in the new wallet before bumping the fee πŸ€“ #meme #memstr
337 days agoβ€’β€’β€’
πŸ‘οΈ πŸ‘„ πŸ‘οΈ
337 days agoβ€’β€’β€’
Oh this one's a good tip now too
337 days ago
337 days agoβ€’β€’β€’
Pro Tip: Besides a small test transaction you can also send the actual #bitcoin transaction for 1sat/vB with Replace-by-Fee and then confirm your funds appear in the new wallet before bumping the fee πŸ€“ #meme #memstr https://video.nostr.build/e8a94256b1d3b4e679951ec13b22657afc8e9f4db7578273fbe0e55c5e8d54a5.mp4
337 days agoβ€’β€’β€’
#machico #madeira
338 days agoβ€’β€’β€’
Just wrote an article about Blossom Drive. a new nostr app I'm building for file sharing and censorship resistant file hosting
If you want to give it a try its hosted at https://blossom.hzrd149.com/
naddr1qqxkymr0wdek7mfdv3exjan9qgszv6q4uryjzr06xfxxew34wwc5hmjfmfpqn229d72gfegsdn2q3fgrqsqqqa28e4v8zy
πŸ‘€
338 days ago
338 days agoβ€’β€’β€’
I'm really excited about this. Blossom is deceivingly simple, which is why it is powerful and why it has a chance of working.
What #nostr got right (and Bitcoin, for that matter) is that duplication is a feature, not a bug. "It takes advantage of the nature of information being easy to spread but hard to stifle," to quote Satoshi. De-duplication is a fools' errand, as it assumes a God's-eye-view. A global state is required to properly understand what to delete and what to keep. The second problem is of course indexing and discovery, which is indeed a hard problem if a global state is to be avoided. It's hard, but solvable. Especially if you already know what you're looking for, and especially especially if you have a common and purple-coloured discoverability layer.
Blossom is basically copying what nostr did for notes and applies it to arbitrary files. Instead of relays handling events, there's simple HTTP servers handling files. Like relays, servers are interchangeable as they share the same interface, encouraging duplication and redundancy. Instead of uploading something to a single server, you might upload it to five different servers. Popular and/or important files will be on many servers, which is how the online world works today already. Files that you need often might even be served by a #blossom server that is geographically close to you, just like we now have local cache relays packaged with some clients (or that you can self-host on your home server).
In the best case, Blossom will organically mirror what YouTube et al's content delivery networks already do well today, which is to provide file hosting that is high in availability and proximity. The neat thing about it all is that you can provide monetary incentives as it is nostr-native, and you get web-of-trust characteristics for free, as you can use only your servers, or those who are trusted by your friends, etc. And in the future, we'll probably have paid servers that whitelist npubs, just like we have paid relays now.
So why is all of that awesome? Well, here's the thing: as the user, you actually don't care where a file is hosted; you just care about the file itself. The current iteration of image (and other) hosts is incredibly stupid. Images are uploaded, downloaded, and re-uploaded without end, often with massive loss-of-quality as the same image is compressed and re-compressed a hundred times. It's always the same image, or at least it should be. With Blossom, it actually is.
Gone are the days of finding a thing and uploading again. You just need the hash, and the thing will appear. You could even insert images directly in notes with something like a blossom:ef1c26172f55017c9d9d6afa7cf22605b237b0fe92425e81e3b5e24d46c95448 and each client can choose how (HTTP, torrent, I2P, etc.) and where (public servers, private servers, etc.) to retrieve it from.
But wait, there's more. Remember the monetary incentives we talked about? It is what allows for the emergence of a proverbial "assassination market" for files: you provide the hash, along with a bounty of 21k sats to anyone who can provide the file most readily. Servers could provide cryptographic proof that they have the file, and you could escrow the money until delivery is done and you verify the file on your side. The building blocks are already there, we just need to put them together in the right way.
Blossom is one of the most exciting projects that came out of the first @npub1s0v...rmq5 cohort, aka #SEC-01. I'll have more to say about all the other amazing #SovEng projects that came out of the discussions and collaborations we had, but now I'll have to go and upload some files.
338 days agoβ€’β€’β€’
Just wrote an article about Blossom Drive. a new nostr app I'm building for file sharing and censorship resistant file hosting
If you want to give it a try its hosted at https://blossom.hzrd149.com/
naddr1qqxkymr0wdek7mfdv3exjan9qgszv6q4uryjzr06xfxxew34wwc5hmjfmfpqn229d72gfegsdn2q3fgrqsqqqa28e4v8zy
321 days agoβ€’β€’β€’
blossom would be perfect for events, also... assuming they are stored in the canonical form that generates the corresponding event ID
if relays just stored all events on blossom they would propagate wildly across blossom nodes
not suitable for DMs and closed groups but for anything public it's a perfect solution as a back-end storage for relays
i intend to build out an interface to do exactly this in the future
321 days agoβ€’β€’β€’
You mean so that one relay can use multiple back-end servers? #noobquestion
321 days agoβ€’β€’β€’
yes, that is even possible
i am in the middle of getting the logic set up for a local cache with one back end but it's entirely possible you could have multiple and set up sequences to request them from and each cache level could also have its own downstream sources as well
as i understand it, this is part of blossom's architecture also
337 days agoβ€’β€’β€’
How do you know in which server a specific blob is hosted?
337 days agoβ€’β€’β€’
Similar to NIP-65 users could publish a k:10063 event that would advertise where their blobs are hosted https://github.com/hzrd149/blossom/blob/master/Nostr.md
Although most clients wouldn't need to check unless the image failed to load from the original URL
337 days agoβ€’β€’β€’
This is the hard part
338 days agoβ€’β€’β€’
Fantastic summary! Definitely one of the best things that came out of our SEC-01
Purple-coloured discoverability layer πŸ’œ
LOAD OLDER THREADS