Damn implementing all the necessary stuff for a few cli commands over grpc is long.

I own two sockets

Unpopular opinion : we wouldn't have this mess with fees if we adopted bigger blocks like BSV. #bitcoin

En vrai dans l'absolu chacun fait comme il veut. Le formalisme est le poison de la langue vivante.

Mais pour le coup, je reste conservateur par préférence #teamvieux

Unpopular opinion : les seuls travailleurs du digital sont les distributeurs de baffes, les autres sont travailleurs du numérique.

On a full capable and stable server of course 😉

If I have a chunk of free time I'll try to run it tonight 😁

Interesting ! Adding it to my to-try list.

Just wondering, why JS ?

Agreed 💯

- raviolis fromage

- pq

- crème Mont-Blanc

- 3 boîtes de after-eight

- sauce bolognaise

nostr:nevent1qqsg6k8392ralsdzsjwynjj95q8q85qpkr0vca5dnfmvw2emn5t4ccgpzemhxue69uhhyetvv9ujumn0wd68yumn9eex2q3q0fd0ncqmzd6q3e7t9kzlh82asw2jj7kpn7hjvcrfhq4uyzc4dpvsxpqqqqqqz375umx

Un protocole de prise de notes pour faire ses courses

Le bonhomme n'exprime pas sa position personnelle dessus et donne vraiment les deux versants je trouve, donc c'est assez intéressant.

Et puis du contenu youtube fr avec un compte dédié sur nostr quoi, c'est cool non ?

Un peu de vulgarisation scientifique sur #nostr 😁 #nostrfr

nostr:nevent1qqs8rtds8ssx3p8zge72wyhcv60cfswg98wnyx6lxdevfxk474wr66gpzemhxue69uhhyetvv9ujumn0wd68yumn9eex2q3q06mec5ygtefqncsqlefepfcqa5qzc4ap9e50yadegz8hryxg0qaqxpqqqqqqzqyludg

Added an instance for nostr:npub17h9slrnuarr6av2p5dumtzeen8g6l0ykvxdflqq4fz40fd6f5d5sewqu0z, but I'll have to stop it. The main feed is so active it has more activity than the latest changes on English Wikipedia feed. 🤯

Sorry but I don't hate it 🤷‍♂️

Built a unix socket for nostr:npub1wuh4dag77ywsu22ut4k83nhm8ua4la70ufswdtxyl962wtng4z7smv0znc but i'm wondering if shouldn't have gone with gRPC instead :/

The Nostr client would embed the torrent client.

This is a common practice with the protocol in some apps. e.g: Steam uses bittorrent for application/update downloads.

Up to the client to handle the seeding and the rules to apply ( service workers to keep seeding in the background for X time even if user is not on the app actively ).

The idea is that this way the files content wouldn't be in the nostr protocol and it wouldn't require additional protocol design. It'd be up to the client to handle the content retrieval, sharing, caching, etc.

Obviously there should be a way for user to fine-tune the behavior of the client regarding the torrent client, but i see this as another matter

Unfortunately, it seems I'm cooking laziness 😬

Good evening !