Comment on Pixelfed Uptick in Monthly Active Users

• jgrim@discuss.online ⁨5⁩ ⁨days⁩ ago

  Hey, sorry. I’ve been dealing with some ongoing personal stuff.

  There are no clear release versions in the repository; all work is done in the mainline branch, called “dev”. Therefore, you are not guaranteed to always use the same code as someone else on the same “version,” which makes debugging issues difficult. I had to build my own Docker containers when I first started hosting it because the ones provided didn’t work as expected. I’ve not tried them since. So, depending on your deployment process, this may not be an issue.

  New releases are often buggy and break existing functionality. Feature releases are slow and seem unnecessary when core features are incomplete or not working. The developer is distracted by other projects.

  There aren’t any ways to communicate and create a community unless you force everyone to follow a specific account from the start of your instance. Funding is challenging and becomes expensive due to image storage and bandwidth usage.

  I have other projects I contribute to; otherwise, I’d contribute to improve or fork Pixelfed. I want to reimplement many of the existing features.

  source

  • julian@community.nodebb.org ⁨5⁩ ⁨days⁩ ago

    @jgrim@discuss.online Pixelfed has no versioning? That's concerning that you have to live on the bleeding edge if you don't want to be outdated.

    I do see there are tags, which at least shows some versioning?

    source