Notices by SpaceLifeForm (spacelifeform@infosec.exchange), page 3

@patrickcmiller

The inertia problem is difficult.

But, they are slowly moving away.

@freemo

You misspelled maroons.

@mhoye

Desktop or mobile? #Debugging

@mhoye

Thanks. IOS seems to be a factor.

@feditips @MastodonEngineering

It would be helpful if they posted on #Mastodon more often. Only 5 posts with thousands of followers is not what you want to do if you hope to get some engagement and some input.

@feditips

Unfortunately it is not that simple.

The server could do it based upon age of when the user last saw the boost. The problem is that this adds more complexity to the server to manage. And, there is no guarantee that the user actually saw (eyeball read) the boost in the first place.

I think this is best managed client-side, and that requires the client to track which post was boosted, and then would likely not be over 24 hours before it is aged out of a cache. Though, if you have the ram, you could make the expiry time longer.

Needs to be client side, but continue to waste bandwidth as happens now.

It is important that the original post creation timestamp is NOT a factor.

@atomicpoet @fediversenews

No new fork needed. It already exists.

@thomasfuchs

What I was inferring, and did not spell it out, is that it not the really the fault of the client, but must be malicious websites.

If the client side can cause the server to execute arbitrary code, then that is a bigger problem.

Because bad actors would never update their attacking platform.

@thomasfuchs

You mean a malicious HTML attack exists, right?

@clacke

No extra parts and no missing parts? Was the Phillips screwdriver included?

Sounds debugged.