#BigBone Project Handover
Due to time constraints, I’ve decided to step back from BigBone. But I’m happy to share that @PattaFeuFeu and @bocops will be taking over! I’m confident the project is in great hands and excited to see where they take it.
A huge thank you to everyone who contributed and supported BigBone—it’s been a fantastic journey!
The project is located here:
https://github.com/PattaFeuFeu/bigbone
Keep federating,
André
Another long-time overdue update of the #BigBone library was released just now. It brings support for grouped notifications plus other bug fixes and improvements.
Check out the release notes for more details:
https://github.com/andregasser/bigbone/releases/tag/v2.0.0-20250205.202924
Thanks for all the contributors on this snapshot: @PattaFeuFeu, @bocops, McPringle and jdpgrailsdev.
Finally pushed another snapshot for #BigBone. It brings some new nice Admin API functionality implemented by @PattaFeuFeu and also some minor improvements along the line.
With this snapshot, BigBone becomes feature complete, speaking of supported Mastodon API endpoints.
Change Log:
https://github.com/andregasser/bigbone/releases/tag/v2.0.0-20240518.212224
Are you currently working on an open source project with the #BigBone Mastodon library for Java and Kotlin? If so, I'd love to hear from you. Please send me the link to the project website, the app store entry or the code repository. I am happy to feature it in our README.md if you want.
A new snapshot for #BigBone is out. A lot of great stuff has been added once again. One of the highlights this time for sure is the refactoring of the streaming API code which is now based on the WebSocket protocol. Thanks to all who have contributed!
https://github.com/andregasser/bigbone/releases/tag/v2.0.0-20231228.215524
A reminder that if you don't want to remain on a #Mastodon instance that federates with #Threads but also don't want to abandon your content, you can move it using #MastodonContentMover 👉 https://MastodonContentMover.github.io
(I need to update it to use the most recent version of the #BigBone library, but I don't want to try to rush that and mess something up, especially not right now, and the version that's there should still work fine. If you run into any problems with it please do let me know 🙏)
We're about to introduce ADRs (Architectural Decision Records) in #BigBone to keep track of our design decisions. Doing so, we can always remind ourselves why a certain decision was taken (even years later) and it provides a nice track record for new developers to better understand why things are done in a certain way.
More on ADRs here:
https://adr.github.io/
An Architectural Decision (AD) is a justified design choice that addresses a functional or non-functional requirement that is architecturally significant. An Architecturally Significant Requirement (ASR) is a requirement that has a measurable effect on the architecture and quality of a software and/or hardware system. An Architectural Decision Record (ADR) captures a single AD and its rationale; the collection of ADRs created and maintained in a project constitute its decision log. All these are within the topic of Architectural Knowledge Management (AKM), but ADR usage can be extended to design and other decisions (“any decision record”).
We have just released the next #BigBone snapshot, which brings a lot of new functionality and improvements.
Thanks a lot to all contributors! (special mention to @PattaFeuFeu). Thank you so much.
Please check out the release notes here:
https://github.com/andregasser/bigbone/releases/tag/v2.0.0-20231105.202213
André Gasser
Pachli
Tokyo Outsider (337ppm)