FTW 1 - Jan 6, 2024

Introducing a new weekly podcast called Freedom Tech Wrap. Short episodes that bring you news and project updates in freedom technology. Episodes should drop on Fridays or Saturdays.

Give it a listen and share with friends! The podcast is V4V so if you like it, send some value our way!

People or projects mentioned:

nostr:npub1guh5grefa7vkay4ps6udxg8lrqxg2kgr3qh9n4gduxut64nfxq0q9y6hjy nostr:npub1trr5r2nrpsk6xkjk5a7p6pfcryyt6yzsflwjmz6r7uj7lfkjxxtq78hdpu nostr:npub10pensatlcfwktnvjjw2dtem38n6rvw8g6fv73h84cuacxn4c28eqyfn34f nostr:npub1a2cww4kn9wqte4ry70vyfwqyqvpswksna27rtxd8vty6c74era8sdcw83a nostr:npub17304velluajf6lylvjynpj2f3ndg396w063gj2gef5qk0nwtcyjqfj9yky nostr:npub1yfg0d955c2jrj2080ew7pa4xrtj7x7s7umt28wh0zurwmxgpyj9shwv6vg nostr:npub1m2mvvpjugwdehtaskrcl7ksvdqnnhnjur9v6g9v266nss504q7mqvlr8p9 nostr:npub126ntw5mnermmj0znhjhgdk8lh2af72sm8qfzq48umdlnhaj9kuns3le9ll nostr:npub1aghreq2dpz3h3799hrawev5gf5zc2kt4ch9ykhp9utt0jd3gdu2qtlmhct #fedimint nostr:npub1mutnyacc9uc4t5mmxvpprwsauj5p2qxq95v4a9j0jxl8wnkfvuyque23vg nostr:npub1x3azxuysp5vmfer4vgs4jn5tmfcx4ew8sh0qnev7gczljxsr7jwqa3g4el #bitcoinmining

#freedomtechwrap #ftw #freedomtech

https://www.fountain.fm/episode/RB5p2ZRySaKP3ZHHo39u

Reply to this note

Please Login to reply.

Discussion

Subbed. Don't forget to add #meshtastic to that list 😉

Thanks for putting that on my radar. Will dive down that rabbit hole

I am not really listening on podcast, But i will listen to this anyway.

As subscription limit was too small for nostr clients, Well that actually make the entire thing went crazy. So thinking of making another way to communicate to nostr relays so we do not need to think much about subscription limit on relays.

I spelled your name wrong in the audio, my bad. I got it right in the show notes though 😅. I mentioned your nhttp project.

What is the problem subscription limits and nostr clients/relays?

> I spelled your name wrong in the audio, my bad. I got it right in the show notes though 😅.

No problem.

> I mentioned your nhttp project.

You summoned me.

> What is the problem subscription limits and nostr clients/relays?

You see, So in nostr, basically fetching notes is done by opening an subscription (by example, an subscription named "sub1" was requested to relay for notes from an user). The more sub you open, The busier the relay became as it wants to send you live events.

As the result, Relay software implemented a way to limit numbers of subscription which was useful for small server. But because of this limit, There are nostr client that went brutal because of this.

There are cases when a nostr client opening and closing a sub too quickly at every scrolls (the goal was to get rid of sub limitation). Because you opened a sub and then closed it under 5 seconds, This is brutal for some users especially the one that were limited on bandwidth, or even have high ping to a relay.

If you are experienced programmer, Well, Due to TCP nature, You can't simply close an busy sub. Because the packets is still not complete yet, So it's still downloading until it was done. You will need to wait for seconds till it was actually closed, which then you could open another one later on but again, you can't simply close it again if it was busy sub.