Looking at the local timeline it doesnt appear anyone else is posting - so Im guessing its not currently in heavy use?
is it doing it on demand? it might be waiting for data before it continues processing?
the code generating those URIs wasn't making any requests, but it's possible that it was happening somewhere else in the backend, since we we have code that compresses images for "lazy loading", though that usually applies only for locally-uploaded ones
yeah 🙃 see the blog for an explanation: https://bonfirenetworks.org/posts/meet_us_at_the_playground/#a-note-on-federation
cool 😊 looks interesting to explore!
are there any instances running you know of that are doing federation?
I really like the way bonfire does threading. Already liking it better than mastodon/pleroma and its only one day old haha
It's nice to not just be for rhetorical effect for once! Thanks for the speedy fix 😀
Uhm, seems like I have just been able to boost a post 2 times
Because I clicked 2 times on the boost button, but I did so because the button didn't become blue on the current screen (I only saw it as blue when I got to my home and saw the post boosted 2 times)
So.. 2 bugs that have to be fixed.
One, server side, should not let someone boost a post without first unboosting it;
The second, client side, should be made so that when you click boost it immediately shows up
I saw this bug on mobile btw
Thanks for the feedback! Accidental double boosting is a known issue but being able to boost several times is a feature. We started a thread on our roadmap to discuss what limits should be applied (it will be configurable in any case): https://changemap.co/bonfire/bonfire/task/6505-should-there-be-limits-on/