My brain is kinda exhausted from first wrestling with Linux and Ansible automation, and then wrestling with JavaScript type hell in trying to get some p2p libraries to work.

Gonna decompress before bed by live-coding a lil in with some basic and

So if you haven't yet, try installing the latest pre-release of Agregore and follow along.

· · Web · 1 · 3 · 4

First, I'm going to create a new based website. This used to be called and I think is now called (all very hard to search for :P ).

You can find the docs for the protocol handlers here:

First thing I'm gonna do is open agregore://welcome to get a fresh page and hit ctrl+shift+i to open up the devtools. You can also use `File > Open Dev Tools` or right click on the page and hit `Inspect`.

Next I'm going to use the `fetch()` API to create a new `hyper://` website based on a "pet name" for the key. Every time I use this human readable name it will resolve to the same human-unreadable public key URL.

I got back hyper://sqtc3rcay8hcg3y8ehcrc66zpiceufstcwupukrggf5eukwp7xdo/ which is the public URL for my new site (currently empty)

res = await fetch('hyper://localhost/?key=gemblog', {method: 'POST'})
await res.text()

Navigating to the URL will give me an empty index. So first thing I'll do is add my "homepage" under `/README.gemini`. Sadly I don't have a thing to resolve `index.gemini` yet, but I wanna add that next time I get a chance. Gonna read these docs to brush up on my gemtext: gemini://gemini.circumlunar.sp

res = await fetch('/README.gemini', {
method: 'PUT',
body: `# Mauve's Gemblog!`
await res.text()

Now I can reload and click to open the page

Honestly, this is all you need to get a basic blog up and running. From here you an change the URL in the `fetch()` API call to whatever page you want and add the gemtext into the `body`. Each time you'll be overwriting what was there before.

Whoops! I got the file extension wrong. Seems it's just loading it as Markdown. :P Most of the formatting works anyway. Hopefully folks looking at this in the future will see the fixed version. Also I think I got the file extension wrong?

K, lets delete the old file and make a new one:

await fetch('README.gemini', {method: 'delete'})
await fetch('/index.gmi', {
method: 'PUT',
body: `
# Mauve's Gemblog!
Wow this sure is something.
Way more advanced than my HTML based blog!



Now that I have some basics in there, lemme add a DNS address: hyper://

I use namecheap for DNS but you should be able to use whatever you want as long as it supports DNS TXT records.

TXT _dnslink.gem dnslink=/hyper/sqtc3rcay8hcg3y8ehcrc66zpiceufstcwupukrggf5eukwp7xdo

And bam! I now have a nice looking URL for my blog and it just took a few commands in my devtools and a single DNS record. No servers required!

I'm gonna go fix this mime type issue and add the ability to resolve `index.gmi` and make sure the mime types for `.gemini` and `.gmi` work correctly accross protocols.

But hopefully this has shown folks that it's pretty easy to to get something p2p out there.

Alright! Now that v2.0.0 of Agregore is out, the rendering should be fixed up and it can auto-resolve `index.gmi` under hyper:// when you visit. You can render the raw directory listing by adding `?noResolve` to the end of the URL such as hyper://

@jonny Yeah, along with a total overhaul of the protocol again. :P

@jonny This is in the 2.0.0 prerelease of Agregore? That has the new breaking changes from Hyper. :P

@jonny Oh! Yeah. There's a bunch of stuff. The main thing is that the connections are a lot more reliable since the DHT and wire protocol got overhauled with new "hole punching" capabilities. The way `Hyperdrive` works changed again so any data needs to be migrated again with new keys.

Sign in to participate in the conversation

Escape ship from centralized social media run by Mauve.