SpaceLifeForm's latest activity
- 10mo ·
-
Public·
-
infosec.exchange
BoostBot Farms R US. That is what will happen.
Yes, you can defederate, but in the meantime, you still get to play whack-a-mole.
…See more
BoostBot Farms R US. That is what will happen.
Yes, you can defederate, but in the meantime, you still get to play whack-a-mole.
See less
BoostBot Farms R US. That is what will happen.
Yes, you can defederate, but in the meantime, you still get to play whack-a-mole.
BoostBot Farms R US. That is what will happen.
Yes, you can defederate, but in the meantime, you still get to play whack-a-mole.
…See more
See less
- 11mo ·
-
Public·
-
infosec.exchange
The good thing about minus 40 is that you need not know the units involved.
…See more
The good thing about minus 40 is that you need not know the units involved.
See less
The good thing about minus 40 is that you need not know the units involved.
The good thing about minus 40 is that you need not know the units involved.
…See more
See less
- 12mo ·
-
Public·
-
infosec.exchange
Speaking of descriptions, I want to encourage everyone to provide descriptions for links that are not self-descriptive. Youtube is a perfect example.
I am less likely to chase a link if I do not know what the subject matter is.
…See more
Speaking of descriptions, I want to encourage everyone to provide descriptions for links that are not self-descriptive. Youtube is a perfect example.
I am less likely to chase a link if I do not know what the subject matter is.
See less
Speaking of descriptions, I want to encourage everyone to provide descriptions for links that are not self-descriptive. Youtube is a perfect example.
I am less likely to chase a link if I do not know what the subject matter is.
Speaking of descriptions, I want to encourage everyone to provide descriptions for links that are not self-descriptive. Youtube is a perfect example.
I am less likely to chase a link if I do not know what the subject matter is.
…See more
See less
- 12mo ·
-
Public·
-
infosec.exchange
It may be worth noting that even if it is a bot account, the person that set it up may actually read replies. Usually not what one would expect, but you never know.
…See more
It may be worth noting that even if it is a bot account, the person that set it up may actually read replies. Usually not what one would expect, but you never know.
See less
It may be worth noting that even if it is a bot account, the person that set it up may actually read replies. Usually not what one would expect, but you never know.
It may be worth noting that even if it is a bot account, the person that set it up may actually read replies. Usually not what one would expect, but you never know.
…See more
See less
- 12mo ·
-
Public·
-
infosec.exchange
My profile is an example of this.
…See more
My profile is an example of this.
See less
My profile is an example of this.
My profile is an example of this.
…See more
See less
- 1y ·
-
Public·
-
infosec.exchange
Even if you do this, you will likely see redundant boosts that still clog your timeline.
…See more
Even if you do this, you will likely see redundant boosts that still clog your timeline.
See less
Even if you do this, you will likely see redundant boosts that still clog your timeline.
Even if you do this, you will likely see redundant boosts that still clog your timeline.
…See more
See less
- 1y ·
-
Public·
-
infosec.exchange
I would add hiding boosts as an option.
…See more
I would add hiding boosts as an option.
See less
I would add hiding boosts as an option.
I would add hiding boosts as an option.
…See more
See less
- 1y ·
-
Public·
-
infosec.exchange
This is the correct approach. Move.
The Sidekiq queues can build up quickly on a large instance, and they can get stuck.
…See more
This is the correct approach. Move.
The Sidekiq queues can build up quickly on a large instance, and they can get stuck.
See less
This is the correct approach. Move.
The Sidekiq queues can build up quickly on a large instance, and they can get stuck.
This is the correct approach. Move.
The Sidekiq queues can build up quickly on a large instance, and they can get stuck.
…See more
See less
- 1y ·
-
Public·
-
infosec.exchange
Another thing to add to your writeup:
Boost for reach. And make the poll last at least 24 hours, preferably more, because people sleep.
Well, if you want good statistics.
…See more
Another thing to add to your writeup:
Boost for reach. And make the poll last at least 24 hours, preferably more, because people sleep.
Well, if you want good statistics.
See less
Another thing to add to your writeup:
Boost for reach. And make the poll last at least 24 hours, preferably more, because people sleep.
Well, if you want good statistics.
Another thing to add to your writeup:
Boost for reach. And make the poll last at least 24 hours, preferably more, because people sleep.
Well, if you want good statistics.
…See more
See less
- 1y ·
-
Public·
-
infosec.exchange
@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.
…See more
@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.
See less
@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 @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.
- 1y ·
-
Public·
-
infosec.exchange
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.
…See more
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.
See less
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.
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.
…See more
See less
- 1y ·
-
Public·
-
infosec.exchange
Sure does not look like it paid any attention to the text above it image.
…See more
Sure does not look like it paid any attention to the text above it image.
See less
Sure does not look like it paid any attention to the text above it image.
Sure does not look like it paid any attention to the text above it image.
…See more
See less
- 1y ·
-
Public·
-
infosec.exchange
I have run into this, but I am pretty sure I did not click on something specific and thereby lost the ALL setting.
Then again, it could have been a phantom touch on mobile.
…See more
I have run into this, but I am pretty sure I did not click on something specific and thereby lost the ALL setting.
Then again, it could have been a phantom touch on mobile.
See less
I have run into this, but I am pretty sure I did not click on something specific and thereby lost the ALL setting.
Then again, it could have been a phantom touch on mobile.
I have run into this, but I am pretty sure I did not click on something specific and thereby lost the ALL setting.
Then again, it could have been a phantom touch on mobile.
…See more
See less
- 1y ·
-
Public·
-
infosec.exchange
The problem I see is that someone may want to point out an issue using text only.
…See more
The problem I see is that someone may want to point out an issue using text only.
See less
The problem I see is that someone may want to point out an issue using text only.
The problem I see is that someone may want to point out an issue using text only.
…See more
See less
- 1y ·
-
Public·
-
infosec.exchange
And it was always said that no two snowflakes are the same.
…See more
And it was always said that no two snowflakes are the same.
See less
And it was always said that no two snowflakes are the same.
And it was always said that no two snowflakes are the same.