I've been having fun with IPFS (InterPlanetary File System) again, & I just used it to make my resume easily available online. IPFS is a free and open source protocol that lets you make files of any kind globally available without using DNS/websites & with nothing but a laptop running the IPFS app. No server setup needed. It can be used with folders as well, so I plan to eventually use it to make a static website. Here's my current resume on the Pinata gateway: https://gateway.pinata.cloud/ipfs/bafkreigpjsz3x6ge7lxx3nevijv76lq2tkvh6scw7dyer5cydayqlo3dru Note that since the file's ID is based on its content, any future versions of my resume will not be available at that ID-specific link. I would eventually like to experiment with IPNS (InterPlanetary Name System) so that I can share a single ID which can point to changeable content. IPNS is a great way to host your own website without needing to use a website domain. #ipfs #resume #websites #decentralized #peertopeer

I got to use the Python tool for deleting files from Git history called git-filter-repo for the first time. It was easy to use & ran quickly. Git's website recommends using it instead of Git's own filter-branch command:

Git - git-filter-branch Documentation

Hopefully I'll try out Jujutsu (jj) someday for the same purpose. It looks like a very promising Git alternative since it's simpler & it's compatible with all services that use Git, like GitLab & Bitbucket, because it can optionally use Git under the hood. Here's the Jujutsu documentation if you want to learn more:

Jujutsu docs

#git #python #jj #jujutsu #softwaredevelopment

Hi, @fiatjaf. I have an idea for using Nostr's existing network architecture to allow for optionally DNS-free relays. It would ideally be applied to Nostr & Blossom. Relays could have their own Nostr pubkey which they would use to 1. Send a new, IP address location event type to Nostr relays containing their current IPv6 or IPv4 address & port number, & 2. Sign the data they send to clients so that clients can verify that they're receiving the data from the expected relays. With this setup, for a client to find their DNS-free relays, they would 1. Attempt to connect to their last known IP locations 2. If this fails, they would query all relays they know the location of for the most recent location broadcasts they have 3. Reattempt to connect using the new location data This way, a relay could run without a domain name of any kind on a non-static IP address that could change at any time. As soon as the relay detects that its IP address has changed, it could broadcast its new location so it could be quickly connected to again. What are your thoughts?

Hi, @Mike Dilger ☑️. I found a bug in v0.14.0 of Gossip for Linux that let's me open the app without entering a passphrase. Should I share the details in a direct message?

I just discovered the API client, Insomnia, which is a completely free & open source alternative to Postman. I was having header issues with Postman, but Insomnia's intuitive interface helped me resolve the issue right away. Try it out at https://insomnia.rest/download.

For my fellow software developers interested in learning Rust, here's a great intro video to the Tokio runtime for asynchronous/concurrent programming: