arthurfranca

Public Key

npub1l3cgtsurhfchg4cyhhqudm70074sr96srhje330xc5m6czej5n9s9q6vs2

NIP-57 Address

Profile Code

nprofile1qqs0cuy9cwpm5ut52uztmswxal8hl2cpjagpmevcchnv2davpve2fjcpzemhxue69uhhyetvv9ujumn0wd68ytnzv9hxgqgcwaehxw309aex2mrp0yhxummnwa5x2un99e3k7mgya2wfy

Publishing to

relay.nostr.band

relay.noswhere.com

nos.lol

Author Public Key

npub1l3cgtsurhfchg4cyhhqudm70074sr96srhje330xc5m6czej5n9s9q6vs2

Show more details

Last Notes

2024-08-11 21:30:27

- reply

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

2024-08-08 18:04:23

- 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 17:54:15

- 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 16:32:54

- reply

I say keep trashing everyone!! mleku and semisol are a delight to read. Appreciate people that dare to say what they really think. If I had sats i'd zap them

2024-08-08 16:06:40

- 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 16:50:21

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-27 03:43:44

- reply

I will emit three huge insults: monero!!! nimiq!!! nano!! Damn the devil

2024-07-20 15:44:04

- reply

With built-in wallet =0 nice. Wen fork merge?

2024-07-20 15:24:56

- reply

Topzera

2024-07-19 19:45:41

- reply

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

2024-07-19 19:42:07

- 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 20:31:58

- reply

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

2024-06-24 03:34:30

- reply

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

2024-06-23 16:50:00

There was this girl on a movie that was pictured as really smart from the start. Her stance and the way she talked made her neighbors, friends and familiars look like far less intelligent than her and while watching the movie I believed she had a superior brain.
She was always reading and was interested in all kinds of science subjects, specially Medicine. Thing is her sister was ill and needed a heart surgery but I think her family had not enough money. She decided to operate her sister by herself on her garage while their parents were away from home, cause she wanted to help and was sure of her ability.
The procedure was dirty with lots of blood and while I as spectator was led to believe she could be successful, but of course it was impossible and her sister died!! She had no experience in surgery after all. Reading a book won't account for all the details that could make things go wrong.
I guess each individual at one point in life thinks that they are smarter than most others surronding them. Math says half of us are delusional.
Can I perform that "surgery"? I mean, can I really code a great nostr client into existence? Hope I'm not delusional. We should exercise self-criticism and a good way to do that is by testing if you can achieve your goal when it doesn't depend on anyone else, I think.

2024-06-22 03:47:57

- reply

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

2024-06-21 22:02:30

- 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 19:44:54

- reply

That and bad event kind design decisions such as kind:1 used both as OP and as replies, which pollute feed when you just want to fetch one of these types.
Also NIP-10 reusing e-tags to reference events with different meanings in the context of a thread, specially the one always present with "root" marker, which force you to download bunch of crap when you just want direct descendant replies.
NIP-10 notifying too many people with lots of p tags.
So on...

2024-06-21 19:11:48

- 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 19:04:14

- 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 16:31:56

- 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 16:23:43

- 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 15:30:34

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-05-27 16:49:59

- 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-24 00:02:21

- 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-22 16:14:01

- reply

:applause:

2024-05-13 21:19:25

- reply

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

2024-04-26 22:13:27

- reply

People knew of all NIP-17 flaws but merged the PR either way.
There is a PR that doesn't let a hacker read all previous messages and also make it possible to detect a compromised nsec by making the peer inform of device changes while keeping implementation complexity relatively low (though need review and I don't have time yet to implement it for testing) -> https://github.com/nostr-protocol/nips/pull/978

2023-11-14 21:06:31

- reply

I think if there was a separate kind for root notes instead of kind 1 maybe there would be no problem because a root note doesn't reply to anything. For example, long form content is supposed to be a root event so an `a` tag could be used to link to a community.
But reusing `a` tag for NIP-72 clearly was a mistake and should be deprecated in favor of another one letter tag.

2023-09-21 21:22:56

- reply

No one liked the idea https://github.com/nostr-protocol/nips/pull/659

2023-07-14 17:38:31

- reply

Ok but the additional nip17 REQ filters are limited to a subset of the nip17 added fields returned with events and they are namespaced accordingly. That's why it may make sense living in the same NIP.

2023-07-14 14:48:01

- 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-03 00:12:44

- reply

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

2023-04-02 16:17:49

- reply

No cause then at what relay will you find metadata from said pubkey?

2023-03-29 16:16:49

- reply

This is a test
#[0]