@hiphopheaven

anything is better than what we have now, which is nothing.

well, we get broken promises and moving goalposts, I guess. which might still happen with a roadmap, but what can you do.

oh well.

maybe by the one-year anniversary of the oh-so-successful Kickstarter for "accelerated Pixelfed development" we might actually get something RELEASED.

that's only, what, a month and a half or so from now? plenty of time.

plus! that'll be a mere three months late on the #pixelfedChristmas update we were promised and told we wouldn't regret waiting for!

there's no benefit to FormerInstagramUser12345 when a "commit" is made. if they're just trying to use Pixelfed to post photos, the "before" and "after" a commit looks exactly the same to them -- still broken, still janky, not updated.

it's like the repair guy saying your car is "fixed" when it's been sitting in the shop awaiting a shipment of replacement parts for the past week. the parts haven't arrived, they aren't installed, you're not driving the car, ergo IT IS NOT FIXED.

@hiphopheaven

Pixelfed could seriously use a public roadmap, same as Loops has. more transparency, more accountability. (maybe fewer blown deadlines and deleting posts to cover them up?)

anyway, I don't understand touting the number of commits a project has. who cares? if updates are not working on public/private servers (NOT just test ones!), then commits are MEANINGLESS for the average end user. they do nothing to improve user experience UNTIL they're actually deployed and available to all.