My next class begins soon. I'll be studying the underlying architecture of the OS and Assembky language to interact with the processor. Can't wait to dive into a fully new area for me.
I was glad I took a quarter off to realign myself with programming. I got some good practice in and have been keeping up with conversations in the local meetup groups I ha been attending.
For personal projects, my flask apps continue as I go deeper into the book and documentation.
Following some discussion on Bluesky I came to the realization that I don't know how the appview works in ATproto. It was described as alternatively an API server or a server layer to organize and backup repos. Neither really encapsulates what it is but it's a large piece of tech to learn.
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.