OpenStars

Leia, when impersonating Boushh.

Hardly a flight, more like a fall really... :-P

They used to be really good!

They still are now, but they used to be too.

CEOs want it, and will fire anyone who looks like they do not. Also anyone who actually gives it to them, or does not give it to them. Does this make sense now? 🤯

(also @NoForwadSlashS@piefed.social)

Thank you, this is very interesting!

Even PieFed posts coming into PieFed.social from multiple other PieFed instances are affected.

Goat is said to be quite good 😋

(/s, or actually no, goat is sometimes even said to be the GREATEST!! 😉)

I wonder if it is some kind of bug, maybe in scheduled posts or a third-party app that people are using that mangles them?

Thank you for your measured response.

Throttling PieFed users is bad enough, but throttling users of other platforms seems akin to censorship. Like if you want to access the full Threadiverse then you can do so from Lemmy + mBin + nodeBB etc., but if you access via PieFed then you don't get the full range of activities. In some ways PieFed is Threadiverse++ (the API supports user & post flairs, polls, emoji reactions, etc., on top of internal organization goodies like categories of communities if you use the web UI), but in some ways it is also Threadiverse—, intentionally choosing to ignore some contributions from the wider Fediverse.

At a minimum that would be quite... odd to explain to people.

And thank you also for the additional code peek!:-)

Omg this will really break the whole federated model won't it? It's already insane that different instances hold different vote counts from one another, but this adds a whole new twist on top.

Genuine question: does this mean that PieFed is now no longer ActivityPub compliant? Is it not fully part of the Threadiverse anymore, and is now its own little subset of that? Even Mbin still accepted vote counts, even though it added boosts ("increases" and "reductions" iirc?) on top of them.

Could you tell from your look at the code if PieFed is only throttling its own users internally, prior to votes federating out, or throttling incoming votes from Lemmy as well?

Also this is so ridiculously easy to get around: most of us have a variety of obvious and self-acknowledged alts across the Threadiverse, but I doubt PieFed is going to maintain a mapping among all of them and apply the throttle universally across the entire set. e.g. Blaze goes back to his empire of alts, one for each day of the week, and continues upvoting without restriction.

The KISS principle would seem to apply - why needlessly complicate matters?

Edit: I found your missing vote btw, here it is:

Edit 2: I thought the above image was from Black Hole Sun, but now I am not so sure of that... anyway it seems to fit, regardless:-P.

You seem to keep flipping on this point, which is confusing to me.

If a limit must be applied for that reason, then so be it.

How much server costs would be saved though by this limiting, or is that simply a theoretical consideration?

Wouldn't more savings be possible by something else like limiting uploaded image sizes, or like only allow 10 images per month (uploading a new one automatically deletes the prior one)? And if so, what is the benefit of that other solution vs. the effects of throttling the top contributors? Both decrease the overall health of the network, so which at least maximizes the savings from having done so?

Fortunately I avoided the mistake of voting blue tho, bc Lemmy tankies told me the truth that bOtH sIdEs SaMe.

( /s )