arthurfranca

oh hooo dude, let me tell you: bending passkeys for storing and retrieving nostr keys does work!
browser extensions no more. very soon!
https://image.nostr.build/0f85c3a4ffde83fdd2e9c1bbc4d275f866d315a1d0029b3ee15c7be56af101fa.jpg

2025-09-21 15:29:20 UTC

- reply

What if an app was able to embed another app specialized on loading all kinds of nostr events by just adding an iframe set to "44billion.net/+<special-app-reference>/whatever-inner-route/kind-2653?primary-color=purple"? Soon tm
I think that the one that builds such nostr "special app" to load event kinds, if well done thus used by other apps, kinda will dictate what is the "official" event structure for each nostr kind.

2025-09-21 15:04:53 UTC

This week I tested it with Jumble's source code and after some bug fixes... it works perfectly! Yeah you can upload anyone else's code easily or just use official Jumble, if the Jumble's dev chooses to upload it. Later, there will even be a 'draft' release channel if say a vibe coding platform wants to upload and show a preview before really publishing a vibe coded app to the 'main' channel.
1 or 2 weeks tops to finish and integrate the signer module and it's ready for demo. \o\
#nevent1q…wlum

2025-09-09 13:49:32 UTC

oh the web! a popover is opened with a custom longpress event. when the touch/click is released, the browser-controlled backdrop receives a pointerup event and immediately auto-closes the popover. All cool, except that the pointerup event isn't exposed to the js, thus can't be canceled.
damn, these kinds of unimportant problems keep slowing me down.

2025-09-05 22:20:24 UTC

- reply

I'm building that, but it takes longer than i thought. I've been fighting many subtle bugs, race conditions, web quirks etc.
Not blossom but dev's outbox relays (files are small and chunked if needed), any static website works but can't use service worker (cause it would require a server). An app is unable to auto-update itself.
Sooner than later.. é verdade esse bilete

2025-09-02 11:57:59 UTC

- reply

Yes, I'm gonna use passkeys to help simplify nostr key management when accessing nostr apps. The nsecs will be importable/exportable. All the pieces are almost in place to put it online for everyone to test. I just need to go back to drinking coffee or someone to whip my back.
Passkeys have become better with time. We don't need Apple/Google/MS/some-linux-distro-support anymore. E.g. Bitwarden (can be self-hosted) has a browser extension and native apps, supports passkeys and syncs keys across devices no matter the OS.

2025-08-26 13:57:21 UTC

"Google will require developer verification for Android apps OUTSIDE the Play Store." Starting with Brazil.
This is full KYC: phone number, home address and name.
On Play Store, besides the KYC, they already remove apps for arbitrary reasons.
Conclusion: Web is the only viable platform left.
https://techcrunch.com/2025/08/25/google-will-require-developer-verification-for-android-apps-outside-the-play-store

2025-07-09 01:20:19 UTC

- reply

Now I see your messages! All good

2025-07-08 21:29:46 UTC

- reply

I see no message from you too so I will resort to... telegram =o

2025-07-08 19:45:12 UTC

- reply

Coracle

2025-07-08 13:45:00 UTC

- reply

agree! that's a good one

2025-07-08 13:17:47 UTC

- reply

I've just sent some messages from a client that seems like it uses nip17

2025-07-08 01:15:00 UTC

- reply

I'm not opposed at all. It's just that from the outside it looks like a closed group. Do you want to be my agent to represent me to them? You can test my js framework to see I'm being honest.

2025-07-07 22:47:27 UTC

- reply

there are many differences but the main thing is that 44billion would be the platform where the user discovers the apps, install them, open/close/minimize. they click on it or paste the 44billion.net/+appname. The dev just upload the static page files while logged in with their pubkey.
The dev doesn't need to worry about hosting nor need to beg goggle to show the app on search results.

2025-07-07 22:22:18 UTC

- reply

though the "+fiatjaf" and "+nostr" app names are yours

2025-07-07 22:10:41 UTC

- reply

Oh noes if I make it open source I'm doomed I would be poor forever. I'm thinking of selling app names for a living. I need this thing up and running for some months before people can make alternative implementations.

2025-07-07 21:41:08 UTC

To my 2 anon backers from the failed geyser campaign (lol i think it was @nprofile…ld7p and @nprofile…y2m7?) and to those watching from the shadows I'd like to say that the PoC works very well. 44billion is gonna happen eventually.
For those who didn't get the first time, 44billion is probably similar to the notedeck thing from the Damus guy. But better because web developers already know how to build an app for it... an app is just a good'ol static website.
I already have multi-user, multi-column, multi-workspace UI done although very raw. It uses my new, shiny and fast front-end framework with signals. Many bugs on that lib were surfaced when using it for this project, which was a good thing.
App "installation" concept works although I need to start using my bundle event spec and work on the manual app update option.
There's a new upload spec to code too.
Login is another module that I need to revisit but most of it was already done and working though I will maybe add frost support.
Yeah much work to do, little money (32k sats from campaign xD thx) and nothing online to show yet. And damn how I hate those opensats posts about grants for crap apps nobody wants, maintains nor use lol
I accept thumbs up emojis for motivation.

2025-07-07 19:04:24 UTC

- reply

damn Coracle bizarre threading ui
I replied to a msg a bit deeper on the thread than I wanted =s

2025-07-07 18:42:30 UTC

- reply

Using just ws:// for both one-off and live communications and the Nostr event structure being JSON sure attract devs. This part isn't the problem. (Though, why .content isn't a regular tag? Why is .id included?)
Regarding nostr keys/signature/structure, if changing them wouldn't make things so fast that a new use case would be possible, I guess it isn't worth it. And its good to have something like frost available.
But Nostr has some annoying inefficiencies on relays that won't ever change cause it would take additions to NIP-01 that, let's face it, will never be made.
The main inefficiencies are:
- The relay can't apply different event size restrictions by event kind on EVENT messages. Using a ws binary message with the event kind at the beginning for that would be great.
- Why is sending the event id (client-to-relay and relay-to-client) required when it would have to be recalculated anyway to make sure its correct?
- Relay can't announce it's custom features/config within the ws connection: https://github.com/nostr-protocol/nips/pull/1969
- The AND operator won't ever make it to NIP-01 (new NIPs can't use it for new event kinds cause relay support would have to be broad): https://github.com/nostr-protocol/nips/pull/1365
I guess if someone has the time and willpower to invest into making a nostr-v2, they would have to spin-up a big nostr-v2 free relay to attract client devs and index events from v1's main relays to have initial content. Good luck for that brave guy or maybe this will be Google or Meta at some point.

2025-05-23 19:29:03 UTC

- reply

Yes, ~32k sats. The contributions were sent to me as soon as they were made, after deducting the 5%. Geyser is overall very good.

2025-05-23 18:43:08 UTC

- reply

7 days passed. It's like I said, campaign isn't listed anymore, the link now redirects to /project-not-found page. Graveyard it is

2025-05-23 15:10:39 UTC

- reply

Also updated the description to better explain the project.

2025-05-23 15:09:49 UTC

**Remember Facebook when it had all those cool micro apps and games?** Let's do it using Nostr instead of closed platforms! 😜
Less than three hours left to kickstart the campaign at https://geyser.fund/project/44billion/prelaunch?hero=arthurfranca
...or let the idea die...
New goal perk added there to shake things up! I'm sure javascript devs would be interested in this part.

2025-05-18 11:51:09 UTC

- reply

One more thing I don't know if was clear: App storage is on relays (new spec). I thought of ways to ease the life of not just users but also devs.

2025-05-18 11:44:14 UTC

- reply

Is it a custom firefox build? The <browser|window>.ssi was your addition I suppose.
I want to use default browsers/web apis to lower adoption barrier.

2025-05-18 02:07:48 UTC

- reply

I'm aware of bunkers and of that lib. I've already seen that mysterious lib's button floating around on some webapps ^^.
Spring Browser is good and very similar but I think I can bring new ideas to the table that could work better, I hope.
There are some problems when trying to rehost web clients like api calls that won't work from different domains or blocked iframe loading.
For now I think if devs depend on my lib or on custom api calls to handle relay connection it may centralize things or be one more thing for them to learn. Though I definitely want to help handle things like user relay migration (copying events) that would be too much for every app to code and something the user shouldn't suffer with.
Thx for the ideas. I've added some extra explanations to the bottom of the campaign page.

2025-05-18 01:06:28 UTC

- reply

Let's see. I think it goes to the graveyard after 7 days without reaching the minimum amount. But one can always start over again a campaign later.

2025-05-18 01:02:23 UTC

- reply

The project is a platform (a regular website with some tricks) that abstracts away the boring parts of making a nostr app like multi-account login/signing and notifications. Then devs are free to build simple Nostr apps that are just static websites that handle just one already logged-in user. It is supposed to help with app discovery too like app stores do.

2025-05-17 18:40:53 UTC

- reply

Changed it but yeah its easier to show instead of describing with text.
It's my first crowd funding campaign. Frankly, I wasn't expecting such a small 7 days time window from Geyser to reach a threshold in order to keep the campaign open.
I thought I would just create the campaign and add PoW updates from time to time with no hurry.

2025-05-17 18:24:38 UTC

- reply

Damn I just removed that required one-liner snippetby turning it into an empty space.
Let me rephrase it

2025-05-17 17:43:42 UTC

- reply

@nprofile…d5ve ricão nem pra dar um kickstart de 2 reais

2025-05-17 12:44:45 UTC

In look for a "consolation sat" (is it how we say "gol de honra" in english?)
Where are the 21 sats meme donations? 😄
#nevent1q…vk22

2025-05-16 20:53:46 UTC

- reply

*followers

2025-05-16 18:30:13 UTC

Just launched a campaign at Geyser: https://geyser.fund/project/44billion/prelaunch
Apparently it will auto-close if it doesn't reach $210 goal 😱😱😱😱
If you like the project, please contribute or share to your follows!

2024-12-20 13:47:28 UTC

I feel so light using js without typescript!

2024-12-13 13:39:14 UTC

https://image.nostr.build/9b775d879b8f9eabc1cdf52d42fdbad4765a6c598367f1b915a0d478b33ce288.png
=O~ from https://zap.stream/videos

2024-12-07 12:47:12 UTC

Best nostr clients hands-down:
yakihonne for Android and cobrafuma.com

2024-12-06 12:46:00 UTC

I've read the MLS NIP and its PoC app code. 🙊

2024-12-05 14:55:37 UTC

Taking note 📝
#nevent1q…ry4a

2024-12-05 13:52:29 UTC

- reply

From talking to chatgpt, yes NIP-17 is safer.
A Signal group chat member can provide chat read-only access to anyone, without revealing their own main private key, while with NIP-17 the member would need to reveal it.
Signal chat member could simply keep sending a flow of up-to-date group keys and of received messages for anyone to be able to decrypt (showing not only the plaintext messages but who signed them), without admins or other members noticing it.
Chatgpt may be wrong, though, but the logic seems correct.

2024-12-05 13:19:44 UTC

- reply

yeah I wonder if what you said could really bring in a considerable amount of sats.
maybe I could make a closed source nostr app and apply for an opensats or similar grant to turn it into open source and support further development 🤔

2024-12-05 13:11:42 UTC

- reply

thx @npub1vwv…9tm0 🥲❤️

2024-12-05 01:12:39 UTC

After much thought, I came up with a great (unreleased) NIP
that keeps nostr keys safe without an increase in complexity.
But this v4v thing doesn't seem to be working for protocol specs.
Sats income after 1.7 years of contributions: 1363 sats =O~

2024-11-27 18:02:23 UTC

- reply

Free(mium) relays existence is nostr killer feature. They must exist to give voice to everybody.
The event persistence will inevitably be the same as on the "disappering messages" feature.

2024-11-26 18:23:11 UTC

- reply

On mobile browser the font size is too small. I had to apply 135% zoom

2024-11-19 15:40:13 UTC

Rate-limiting by IP (for example, how fast an user can read or write nostr events) is the most widely used technique to reduce spam on servers that don't require user login.
If nostr gets popular, there will be millions of simultaneous active users.
There are ~2000 tor exit IPs.
If clients start defaulting to using tor for all their users, expect to be heavily rate-limited by most relays.

2024-11-09 01:13:23 UTC

- reply

nip96 at start of PR dicussions had fixed routes with no nip96 config, just like blossom, but stakeholders wanted to specify custom api url to serve files from a different infra. download_url is optionally for using CDNs. Other keys are all optional.
Also nip96 servers, specially free ones, may want to compress images/videos. That's why the file identifier is the file hash before compression. When using blossom, the client is supposed to compress before uploading.

2024-11-08 15:15:55 UTC

- reply

Cough cough ez pz
#nevent1q…7neq

2024-11-08 14:51:28 UTC

Wish I could focus solely on nostr dev. One day I'll finish this baby.
https://video.nostr.build/cbc41730576d28b24cdac1fa9d1306224035c463e9abac5ff3a32a8163660ac2.mp4

2024-11-08 13:02:31 UTC

- reply

I think reposting (kind 16) the kind 30023 article wouldn't have the said side-effect. Although when reposting, one can't include additional text like when quoting with kind 1 events.
Not sure about kind 16 reach though.

2024-11-07 20:41:57 UTC

- reply

Valid point of view

2024-11-07 17:27:39 UTC

- reply

Off-topic: notice how using kind:1 to announce other kinds end up hurting the other event by splitting comments in two places 🧐

2024-08-27 16:21:10 UTC

- reply

If we forbid dots on nip05 usernames, we enable @username.subdomain.domain.tld

2024-08-11 19:30:27 UTC

- reply

Negative Zaps is like casting a "macumba" on someone?

2024-08-08 16:04:23 UTC

- reply

Its great that there are clients that compress media before uploading. But one of the good things of NIP-96 is that it makes it easy for clients to offer uploads by not requiring any client-side media transformation logic.

2024-08-08 15:54:15 UTC

- reply

An amend to NIP-96 could add a query string like `?ref=x` when downloading to only respond succesfully if server has a file with `x` value equal to the hash used to request the file.
For uploads, NIP-96 already has "no_transform" field, which would make `ox` equal to `x`.

2024-08-08 14:22:51 UTC

- reply

Twitter killer

2024-08-08 14:06:40 UTC

- reply

Your call. Nothing against the guy behind blossom (I like nostrudel).
Considering I owe nothing to anyone on the nostr scene, I am free to say what I think, that is, from where I see, blossom **could** have been created for this only: https://opensats.org/blog/hzrd149-receives-lts-grant
Blossom hurts interop by doing exactly the same thing as NIP-96, using similar but incompatible routes and event kinds. Thus, I can't understand people that supports Blossom aside from who had never really read blossom docs and just got caught by the hype.

2024-08-02 14:50:21 UTC

Reporting: still building the web client. This thing takes huge time to develop properly. I mean, there are clients that are here for years and don't even have outbox model implemented yet, which is basic. Atleast I got this done. I got a great app name too lol this is the most important step.
I'm not giving details yet cause I am avoiding saying "X feature currently is not done right in other nostr apps and I have a solution to that" while implementation isn't finished. I have a bunch of new ideas to work on.
Believe mah words!

2024-07-20 13:24:56 UTC

- reply

Topzera

2024-07-19 17:45:41 UTC

- reply

Right, now make all this simultaneously for two feeds and merge them into one ⚰️

2024-07-19 17:42:07 UTC

- reply

Great, I see you're building a web client too! Maybe If one of us manage to dethrone primal.net we can make a petition to change the nostr mascot from an ostrich to Blanka https://image.nostr.build/ea014ac63fbdfca0cea1945fbd2af5d4cbc9ea40858053b31ea4e3ce60714a79.gif

2024-07-09 18:31:58 UTC

- reply

https://image.nostr.build/b36505a8d8ef18f2779d70b3afae6de72f8af57fa81be4ba45bce9da9f7554b9.gif

2024-06-24 01:34:30 UTC

- reply

Performers from Brazil called Carreta Furação
https://www.tiktok.com/@memestrenzinhos/video/7317363637516012805

2024-06-22 14:51:53 UTC

Day 1 of coding the nostr client...
Once a nostr elite told me "It might be harder than you think".
It made me think of Naruto anime where there are some elite characters ranked as geniuses, naturally talented, while some plebs like Naruto himself and Rock Lee never gave up trying to improve themselves by relying on hard working.
https://image.nostr.build/e3135f22e59fd4a19b7c321bdad1a4d99efc6ca581678a7bd439b1d62883a639.gif

2024-06-22 01:47:57 UTC

- reply

https://image.nostr.build/e5e7ab3b3173fbe95495d476cee013333192e2479218cfdfe7b1684adbc30629.gif

2024-06-21 20:02:30 UTC

- reply

Time to apply all the theory learned at the University of NIPs. I completed the course with an average grade of 5.7 rounded to 6.

2024-06-21 17:11:48 UTC

- reply

Not necessarily gonna pursue low-data usage at the cost of poor ux. It is more like taking advantage of knowing well how nostr works to not ship code that carelessly connect to more relays and asks more events than needed.

2024-06-21 17:04:14 UTC

- reply

I think NIP-27 and NIP-96 were very important to the protocol, although the latter was a real pain to get everybody on the same page and merge. It was also important to be there and nag about NIP-42 till @nprofile…2kfz came up with the "CLOSED" message as a solution to most problems. I like unmerged inline metadata NIP that I think @nprofile…2dqr is still using and I will too but I guess nobody else is for now.
Some things had to change on the protocol before being too late to change, even though I wasn't implementing anything at the time.
I see your point though.

2024-06-21 14:31:56 UTC

- reply

Agree. When writing a NIP I think of implementation though its hard to spare enough time to actually implement it. Until now the way I wanted to help was just writing NIPs so others that had clients/relays would implement them instead of me.
I did write some relay and client code though I need to inject some caffeine and complete the damn things.

2024-06-21 14:23:43 UTC

- reply

I was thinking of lazy loading feed with manual refresh (also lazy loading threads instead of loading all thread notes at once like most clients do). No new live events until user manually refreshes.

2024-06-21 13:30:34 UTC

I'm thinking of starting development on a new nostr web client to implement my ideas that always get bashed on the NIPs repo by the nostr gods.
If you are seeing this in the middle of a million notes on a global feed and is interested in an web client that won't suck all your mobile internet plan in a day, follow me for news.. and for rants on nostr NIPs repo scene =]~.
PS: any huebr there?

2024-06-21 12:01:13 UTC

- reply

I suppose this is related to event sets pr defacement =s

2024-05-27 14:49:59 UTC

- reply

There's a NIP-96 ?w=<image-container-pixel-width> query param that clients should use when requesting images.
We should add something similar for videos

2024-05-23 22:02:21 UTC

- reply

"In rare cases, the Bluesky moderation team may need to open your DMs"
This is not a DM feature announcement, it's Group Chat! Chat members: the user, another user and all bluesky moderators!

2024-05-13 19:19:25 UTC

- reply

Kind:1111 to the rescue
https://github.com/nostr-protocol/nips/pull/1233 mind taking a look?

2023-07-14 12:48:01 UTC

- reply

Nice. But could you support NIP-17 filter instead of the custom @lang one?
https://github.com/nostr-protocol/nips/pull/605#issuecomment-1620290873

2023-07-02 22:12:44 UTC

- reply

Could you review this NIP pull request related to file storage? https://github.com/nostr-protocol/nips/pull/547

2023-03-29 14:16:49 UTC

- reply

This is a test
#[0]

2023-03-14 17:43:44 UTC

- reply

What about this use case? https://github.com/nostr-protocol/nips/pull/222#issuecomment-1465223776