home.social

#mastodon4j — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #mastodon4j, aggregated by home.social.

fetched live
  1. I seems @bocops and I have found a new name for the current project: It's "yuki", that's it. It's Japanese and means "snow". I like the name because it is short, easy to remember. Furthermore, our library originates from the project, whose author is also japanese.

    So far I have not found any negative interpretation of this word.

  2. It's done: I have created release notes for all snapshots published since I have started to work on a detached fork of . I will continue to do so for all coming releases.

    To the release notes collection:
    github.com/andregasser/bigbone

  3. A new snapshot was pushed this morning. There was an integer overflow issue reported by a user.

    Probably caused by some fake / spam accounts, but still, the library should be able to parse this data.

    More details here:
    github.com/andregasser/bigbone

  4. I have just opened a new issue in for an integer overflow that someone seems to be experiencing with . It seems to happen, when account information is parsed (follower count, status count, etc...).

    That's interesting. These fields are currently typed as Int, whereas Int has a max value of 2'147'483'647.

    Can anyone provide me a link to an account with such a high number of followers or accounts?

    github.com/andregasser/bigbone

  5. #bigbone: Mastodon Client Library for #Java and Kotlin github.com/andregasser/bigbone

    BigBone is a fork of #Mastodon4J, a #Mastodon client library for Java and Kotlin that was published by Toshihiro Yagi.

  6. @jitterted @KevinWorkman Hi all! Thanks for mentioning our fork. So far, we have mostly been working on putting the existing code on an up-to-date basis, e.g. updating the build system, dependencies, and such. Also, we have fixed several bugs already that have been present in the code (some of them have also been reported in ). Furthermore, a lot of code was restructured to simplify the API. For the coming releases, we plan to extend the Mastodon API coverage. github.com/andregasser/bigbone

  7. New tutorial!

    Use Mastodon4j to create your own Mastodon bots in Java! 🤖🐘

    happycoding.io/tutorials/java/

    Hashtags feel like spam, but apparently that's how Mastodon works sooo #java #coding #tutorial #mastodon #bot #bots #mastodonbot #mastodon4j #hashtags

  8. Btw: Kudos to @factotum who was so kind to fix one of the issues that caused some headaches for some former library users in the past. Should be working well in now. github.com/andregasser/bigbone

  9. We will continue our fork of under a new name: bigbone. Repository and related stuff will be renamed within the next days to make sure we can publish this independently. github.com/andregasser/mastodo

  10. Our fork get's some traction. We've started to create some issues, defined a milestone 2.0.0 release, and continue to define what needs to go into our first library release. If you guys have any input or are willing to contribute, then checkout this repo here:

    github.com/andregasser/mastodo

    Every boost on this post is welcome 🙂

  11. I have just detached my fork from the original project on and will continue development as a separate package. Need to rename my package to something else (any ideas?). I have created some issues in my repo and defined an initial milestone release 1.8.0. Hopefully I can make some progress on this. Big shoutout to the people who have contributed so far! github.com/andregasser/mastodo

  12. Hello everyone, I am trying to implement V2 Mastodon API endpoints in my fork and came up with some thoughts. I am not that experienced with library development and maintenance. Would be happy to get some input on this:

    github.com/andregasser/mastodo

    Thanks for your support! 🙂

  13. I'll put a pull request up in the next few days (with a small example for handling the v1 and v2 endpoints for instance information. Would be cool to get some opinions about that. Stay tuned.

  14. I have started to think about how I could extend the current client with new V2 calls.

    Calling the instance info endpoint on a pre-4.0.0 Mastodon server delivers a completely different result compared to the 4.0.0+ servers.

    To make this more future-proof, will add a new mapping layer between the server response and what I will deliver to the clients.

    Also the lib gets some V1/V2 autodetection. In my opinion, the lib should hide as much complexity as possible.

  15. Hello fellows. I have a question regarding the MIT license. I have forked from the original creator. His repo is MIT licensed. As far as I can understand, I am fine, if I just keep his license file unchanged in my repo (so the original creator remains visible). Any advice on this?

    Link to my forked repo: github.com/andregasser/mastodo

  16. Going to setup some GitHub Actions for my fork. Let's start simple, with a gradle build on push to main branch.

  17. @kerfuffle Hello Kerfuffle! Yes, I know about that. At the moment I am mostly doing some library upgrades and minor code improvements. Later, I plan to add some of the v2 endpoints. But baby steps. It's also a learning journey for me. But so far made quite some progress 🙂

  18. I have forked the project on and migrated it to latest plus latest library releases. Also migrated tests over to . Let's see what else I can do. I use this lib in my own project. Need to implement some of the v2 endpoints from the as well.

    Not sure, if the current repo of is still maintained. Wrote to the maintainer, but did not get a reply. Also, all of the other forks look pretty outdated.

    github.com/andregasser/mastodo