Additionally, I intend on implementing features in the future that might make the app not fully client-side. It remains to be seen, but I felt like AGPL covers all bases.
September 20, 2025 at 9:08 PM
Additionally, I intend on implementing features in the future that might make the app not fully client-side. It remains to be seen, but I felt like AGPL covers all bases.
Additionally, I intend on implementing features in the future that might make the app not fully client-side. It remains to be seen, but I felt like AGPL covers all bases.
September 20, 2025 at 9:08 PM
Additionally, I intend on implementing features in the future that might make the app not fully client-side. It remains to be seen, but I felt like AGPL covers all bases.
Admittedly I am not an expert at software licenses. I chose AGPL because, as I understand, it requires anyone who distributes a modified version of the app to share the source code.
I feel it keeps in good faith with the open source values of the Bluesky community, and I'd like to support that.
September 20, 2025 at 8:58 PM
Admittedly I am not an expert at software licenses. I chose AGPL because, as I understand, it requires anyone who distributes a modified version of the app to share the source code.
I feel it keeps in good faith with the open source values of the Bluesky community, and I'd like to support that.
I’d like to learn core concepts of how it all works, especially as someone who is mostly experienced with frontend development and wants to venture into specifically Swift backend/api development
July 27, 2025 at 3:27 AM
I’d like to learn core concepts of how it all works, especially as someone who is mostly experienced with frontend development and wants to venture into specifically Swift backend/api development