91–100 of 104 posts
I would like to thank Elon for helping me to kick of my doom scrolling Twitter addiction. My usage has been dropping perceptibly over the last 3 months as my feed has gotten stale however now that my Twitter client hasn't had any new tweets in the last 3 days I may finally be able to kick the habit for good.
if your self-control really that bad?
Earlier quoted context omitted.
There was, unfortunately, a lot of nonsensical claims by people with no technical knowledge that Twitter would go down overnight. But anyone with a modicum of experience would know that makes no sense. Websites of all sizes are designed to largely self operate with no manual intervention for decent periods of time. Otherwise all large websites would be down during holidays, etc.
PagerDuty engineer here. There is much to discuss with respect to "Websites of all sizes are designed to largely self operate with no manual intervention for decent periods of time." The phrase "decent periods of time" is doing a lot of heavy lifting here. You also said "Otherwise all large websites would be down during holidays, etc." What makes you think large websites don't go down in some fashion or another durin…
Resilience has three aspects:
1. Anticipating and preventing problems ahead of time 2. Preventing a problem that has already occurred from getting worse 3. Recovering to a good state after a problem has occurred
So the API hasn’t been fully turned off. At least, not for all API users.
So many minor flags already that the problem could be completely accidental. For example people search in android client no longer checks my following&followers. Odd audio behavior in Spaces. More than a few scattered bits of broken micro features work and then don't again. Meanwhile press coverage is look how they only needed half the people on staff so let's do this everywhere asap and recapture value for the poor…
Earlier quoted context omitted.
No this isn’t the same thing, I am convinced I largely used to only see things from followers and certainly never and big breasted random women. And Chelsea, Man United and Sp*rs fans - no thanks! The sparkle used to be about chronological feed ordering vs hate/AI based tweet ordering.
Here’s proof I was correct, downvoters: https://www.digitaltrends.com/social-media/how-to-view-tweet...
> vs hate/AI based tweet ordering
The For You tab is an algorithmically generated list of tweets that is assembled by an AI based on your viewing habits, location, and other engagement metrics. That algorithm may have been adjusted in some ways since Musk took over but those are algorithmic tweaks, they're not a new method of displaying tweets.
Earlier quoted context omitted.
Here’s proof I was correct, downvoters: https://www.digitaltrends.com/social-media/how-to-view-tweet...
That is a tutorial on how to switch from the For You algorithmic view that was the default view on Twitter to the chronological view. > vs hate/AI based tweet ordering The For You tab is an algorithmically generated list of tweets that is assembled by an AI based on your viewing habits, location, and other engagement metrics. That algorithm may have been adjusted in some ways since Musk took over but those are algori…
Earlier quoted context omitted.
Yes, around 2012. A few years later, its CEO apologized and restored it. https://finance.yahoo.com/news/twitter-ceo-jack-dorsey-apolo...
So it’s not something completely controversial that Twitter management broke third party platforms, those that might cut into their advertising and data collection machinery. Incidentally, this is the Tragedy of the Commons that keeps breaking messaging interoperability and stillbirthed the whole pindaric ode that was UDDI SOA, a Corporate oriented declination of TBL’s Semantic Web
Earlier quoted context omitted.
So it’s not something completely controversial that Twitter management broke third party platforms, those that might cut into their advertising and data collection machinery. Incidentally, this is the Tragedy of the Commons that keeps breaking messaging interoperability and stillbirthed the whole pindaric ode that was UDDI SOA, a Corporate oriented declination of TBL’s Semantic Web
Not sure if "complaning about moderation" is taboo, but I'm a bit saddened that my comments to this issue are being diligently downvoted. I don't see any other reason other than "not having enough contempt for Elmo", although they do have some merit. I would expect such behavior on Arstechnica but here? SMH
Earlier quoted context omitted.
That is a tutorial on how to switch from the For You algorithmic view that was the default view on Twitter to the chronological view. > vs hate/AI based tweet ordering The For You tab is an algorithmically generated list of tweets that is assembled by an AI based on your viewing habits, location, and other engagement metrics. That algorithm may have been adjusted in some ways since Musk took over but those are algori…
So “Following” is in chronological order? That’s really unclear if true. The algorithm has definitely been messed with. What is the difference when the end result is the algorithm producing different results because a) parameters have been changed b) there is a new algorithm ? How do you know that you’re right and I’m wrong? The answer is you have absolutely no proof.
Earlier quoted context omitted.
PagerDuty engineer here. There is much to discuss with respect to "Websites of all sizes are designed to largely self operate with no manual intervention for decent periods of time." The phrase "decent periods of time" is doing a lot of heavy lifting here. You also said "Otherwise all large websites would be down during holidays, etc." What makes you think large websites don't go down in some fashion or another durin…
>Resilient: When the site goes down, it comes back up with no or little impact on the user/customer experience. Resilience has three aspects: 1. Anticipating and preventing problems ahead of time 2. Preventing a problem that has already occurred from getting worse 3. Recovering to a good state after a problem has occurred
First, "Anticipating and preventing problems ahead of time" is of a manifestly different character to either "Preventing a problem that has already occurred from getting worse" (sometimes called stabilization) or "Recovering to a good state after a problem has occurred" (sometimes called remediation).
Another model we use that emphasizes the difference is to divide the work into "proactive" and "reactive" categories. Everything we do that is not during an incident is proactive, everything that happens during an incident is "reactive."
It's a simpler model than the three categories you presented, but it can be helpful to highlight the fact that companies often under-invest in proactive processes and end up paying the "robustness and resilience debt" in reactive activities.
Second, I suggest that proactive work such as "Anticipating and preventing problems ahead of time" applies to both resilience and robustness. If there is an incident that is resolved by rebooting a service that has some kind of memory leak, that's reactive.
If the postmortem identifies a bug in the code causing the leak and a bug fix is deployed to prevent that incident from happening again, the system has become more robust.
Whereas, if no bug fix is made, but the runbook is updated to suggest rebooting the service when it runs out of memory, this is going to increase resilience. Proactive activities drive better outcomes in both cases.