Co-Working Code

 I have been able to attend a few sessions of the Seattle ATmosphere working sessions that are being hosted by Seattle Community Network.  Its been a fun time getting to discuss the network and the needed sections with other engineers. 

I've moved my overall plan to hosting my own PDS/Relay/Appview so I can be nearly independent.  The appview will most likely be a soft fork of a webapp that I can hopefully help contribute too but host my own copy for security.  For the relay, I am looking at the rsky-relay (pronounced risky) that was made by Blacksky Algorithms for my relay as I think it will also best fit into the OSS model I can contribute too.  

With Tangled.sh and other appviews beginning to show more features and users I think we will see a good adoption of the ATProto within the tech community for the next few years.  

My own PDS

A few days ago I started up my own ATprotocol PDS.  I want to get deeper into the fediverse.  I was able to attend the first ATmosphereCon last year and it was wonderful to hear everyone's ideas.  

I spun up the PDS on Digital Ocean using my own domain.  I wanted to originally self host on a Raspberry Pi 4b I have sitting around but decided a VPS would be better.  One, because I can host it in the EU for better stability and privacy (yes it's a public protocol, but how that data can be used is also important). Two, I get familiar with a platform other than GCP, and three, it will hopefully be the springboard into some portfolio projects around the fediverse.  

Looking forward to what I come up with and learning on this journey.