I would caution some patience and suspicion on this story.
Zillow says that the sale information was a mistake and has since been removed.
Meanwhile, this headline is sourced from a straight-up clickbait site reposting a story from a news website with a history of mixed factual reporting.
We all get the fun brain chemicals coming out when a big juicy story like this appears and validates our worldviews and we can't wait to share and amplify it, but spreading misinformation is bad, m'kay?
I cannot believe that there are companies and non-wingnuts who are still actively using that site at this point. Like maybe at the start it was ha-ha funny watching him flail about with code printouts and unplugging random microservices leading to outages, but I feel like the moment he started actively funneling money to alt-right knuckleheads and human traffickers should have been enough of a kick in the pants for even folks heavily reliant on the platform to make their exit.
I see we've unfortunately brought over the trend of defaulting to assuming the worst intentions from Reddit, with a side portion of baseless accusations. While I'm disappointed that the community was removed, I think it can be easily explained by:
It's reaaaaaally really easy to sit in the peanut gallery and talk shit about how they're cowardly acquiescing when it's not our neck in the noose.
That being said, I feel like recent acts of defederation are only serving to highlight that the way forward in the fediverse is going to be having accounts on multiple instances in order to get the full breadth of offerings. In my case:
This is my issue with the article.
Headline: Here's what we know about EG.5 so far
Body: Apparently not much. We uhh, know the name of it? Severity, how contagious it may be, symptoms, breakthrough rate...like umm, anything??
Thank you for posting this. I was beginning to become concerned that I'd need to visit Reddit for my fill of disingenuous whataboutism, but this gives me hope that we can cultivate a culture of bad-faith posting right here in the fediverse.
Spam bots pursuing an audience shouldn't be a surprising thing. Even glorious fediverse valhalla is battling with them.
The difference between the Threads & Twitter situations is that I'm inclined to extend a lot more leeway to an engineering team that's less than two weeks into a new platform, versus one that's been around nearly two decades and is suddenly dealing with issues because the owner decided to haphazardly fire the teams responsible for maintaining those areas.
For reference, that's 31.5% of all House Republicans. Another way to see it is that 68.5% of House Republicans, which are generally the most extreme breed of Republican, are supportive of US military aid to Ukraine. I'm pleasantly surprised to find support for Ukraine remaining that high.
It's key to note that customer satisfaction with response is not among the metrics the CEO is highlighting. It seems that the role of customer support is increasingly to frustrate customers away from pursuing issues, rather than reaching a mutually-satisfying resolution. I consider most customer support chatbots as a tactic towards that: they're not going to offer any significant assistance and exist simply to waste my time, so of course the imaginary "time to resolution" is going to be minimal. If they're going to make it a hassle then I'll just open up a credit card dispute.
The main thing for me would be the plethora of high-quality apps already available for Lemmy, not even a month out from the start of the Reddit APIcalypse.
That being said, I think kbin looks infinitely better in either mobile or desktop browsers, making the need for an app less urgent. I don't even think there's an app available for kbin right now, at least for Android.
The creator of tildes.net is a former Reddit backend developer, and believes this behavior is likely due to how Reddit caching works (or doesn't work), rather than an intentional subversion of user intent:
Yes, this is almost certainly a technical issue. The way reddit caches things probably isn't the standard way you're thinking of, like a short-term cache that expires and refreshes itself. There are multiple layers of "cached" listings and items for almost everything, and a lot of these caches are actually data that's stored permanently and kept up to date individually.
For example, when you view your comments page, Reddit uses a cached (permanent) list of which comments are in that page. There is a separate list stored for each sorting method. For example, maybe you'd have something like this with some made-up comment IDs:
Deimos's comments by new: 948, 238, 153
Deimos's comments by hot: 238, 153, 948
Deimos's comments by controversial: 153, 238, 948
If I post a new comment, it will go through each list and add the new ID in the right spot (for example, in the "new" list it always just goes at the start). If I delete a comment, it goes through every list, and removes the ID if it can find it in there.One of the problems with this system (which is probably what's causing @phedre's issues, and affecting many other people trying to delete their whole history) is that all of these listings are capped at 1000 items. If you already have more than 1000 comments and you post a new one, the 1000th comment currently in the new list gets "pushed off the end". The comment still exists, but you won't be able to see it by looking through your comments page, because it's no longer in that listing.
Deleting comments also doesn't cause previously "pushed off" ones to get re-added. If you have 5000 comments, your listing will only include 1000 of them. If you delete 50 of the ones in the listing, your listing now has 950 comments in it. If you delete all 1000 from the listing, your comments page will appear empty, but you actually still have 4000 comments that will be visible in the comments pages they were posted in.
And this is only one aspect of it. There are also multiple other places and ways that comments are cached—comment trees are cached (order and nesting of comments on a comments page, for all the different sorting methods), rendered HTML versions of comments are cached, API data is probably cached, and so on.
All of these issues are probably just some combination of all of your posts being difficult to find and access due to the listing limits or certain cached representations of posts not being cleared or updated properly.
The creator of tildes.net is a former Reddit backend developer, and believes this is likely due to how Reddit caching works (or doesn't work), rather than an intentional subversion of user intent:
Yes, this is almost certainly a technical issue. The way reddit caches things probably isn't the standard way you're thinking of, like a short-term cache that expires and refreshes itself. There are multiple layers of "cached" listings and items for almost everything, and a lot of these caches are actually data that's stored permanently and kept up to date individually.
For example, when you view your comments page, Reddit uses a cached (permanent) list of which comments are in that page. There is a separate list stored for each sorting method. For example, maybe you'd have something like this with some made-up comment IDs:
Deimos's comments by new: 948, 238, 153
Deimos's comments by hot: 238, 153, 948
Deimos's comments by controversial: 153, 238, 948
If I post a new comment, it will go through each list and add the new ID in the right spot (for example, in the "new" list it always just goes at the start). If I delete a comment, it goes through every list, and removes the ID if it can find it in there.One of the problems with this system (which is probably what's causing @phedre's issues, and affecting many other people trying to delete their whole history) is that all of these listings are capped at 1000 items. If you already have more than 1000 comments and you post a new one, the 1000th comment currently in the new list gets "pushed off the end". The comment still exists, but you won't be able to see it by looking through your comments page, because it's no longer in that listing.
Deleting comments also doesn't cause previously "pushed off" ones to get re-added. If you have 5000 comments, your listing will only include 1000 of them. If you delete 50 of the ones in the listing, your listing now has 950 comments in it. If you delete all 1000 from the listing, your comments page will appear empty, but you actually still have 4000 comments that will be visible in the comments pages they were posted in.
And this is only one aspect of it. There are also multiple other places and ways that comments are cached—comment trees are cached (order and nesting of comments on a comments page, for all the different sorting methods), rendered HTML versions of comments are cached, API data is probably cached, and so on.
All of these issues are probably just some combination of all of your posts being difficult to find and access due to the listing limits or certain cached representations of posts not being cleared or updated properly.
Similarly, platforms that default to a massive CREATE AN ACCOUNT box centered on the screen and make you play Where's Fucking Waldo trying to find the size 8 "Log In" hyperlink.