Things left before a PP MVP:
- send/get pings
- fix a bit of stuff and harden the app against user

I'm a 0.01x dev

I'll probably stream on the 2nd some PP development. Might even throw in a state machine for the main protocol

@xan.lol I'll finish PP when you finish your website /j

moving away from github and switching to @tangled.org

tangled.org/azom.dev

I'll fill the repos in the coming month

it doesn't support ipv6, rip

my blog now supports http/3

ipv6 next (if it's even possible with my ISP)

ok alpinejs is the UI framework that works the best for me from the ones I tried. It's going to be what I use for pp (for the foreseeable future at least)

Back on pp, forgot that I didn't really have auth yet so I made a crappy one that is vulnerable to replay attacks (it's temporary).

Also .git/ is 300+ MB so I might just reset it :p

Oh and UI still doesn't have a working base, but I'm using alpinejs now

thought it would be nicer (?) to make this a general prog account (will still post PP stuff tho). Feel free to unfollow tho

I'm probably going to set aside for now my blog about what I've learned on communication and authentication protocols.

I'll instead make one just describing the authentication protocol of PP with a quick-ish explanation on why I choose to do it that way.

I have a choice to make for PP. Either:

1.

Usernames are chosen by the user on account creation. They are stored on the server. This can remove a layer of privacy since the server admin can access that information.

(1/3)

yo