I know its a joke, but cutting PFF power is never a good idea. It makes any kind of forensics a lot harder, and its probably not going to help anyway. You should isolate the computer from the network, and then call a professional.
However, putting the computer to sleep/hibernate it may help, just so I.e ransomware can’t continue encrypting, but maybe still has keys in memory, if you’re lucky. This is only my theory, though, not sire what are the best practices.
It's definitely from other instances voting on it. For example. I'm on the @kbin.social instance but I'm commenting on your post from @jeemy.jeena.net
Also, this doesn't really have to do with your point but it's interesting none-the-less, it's really hard to keep view count numbers accurate when you've got multiple servers involved. The view count is accurate and every view is being counted, but any time you look at it, it's not exactly correct. If you think about how each server might get a view count update from the server at different times, and then add the views that only it sees to the view count, and then when it goes to add it's view counts to the central count and get a new updated number there may have been dozens of other server that have updated the view count at various times between then and now.
It all gets very complicated but I think it's kind of neat that a view count number can be accurately kept track of and yet every time you look at it, it's not exactly correct.
That’s because, currently, the community stats that you see in the sidebar are only from your instance – community stats are currently not federated. Afaik, federated community stats are going to be implemented in 0.19.
The number is displayed on the instance the post is on, so it doesn’t matter which instance you view it from (or if you’re not logged in at all), the number is calculated from the active users who are members of the instance you’re viewing.
jemmy.jeena.net
Hot