This only hides content locally for Threads users, it doesn't affect visibility from any other fedi platform. It's not that different from a Lemmy instance downvoting a comment to the point of being auto-hidden; it still exists but requires an extra click to see from your instance, and the rest of the fediverse can access it normally.
Chozo
joined 2 years ago
Nintendo isn't against emulation. They're against piracy, which Yuzu was facilitating. None of the emulators that don't have specific support for unreleased games have been touched so far.
As somebody in both communities, these people are outliers, by far. I'd say 95% of the randoms I play with in either game are decent folk who aren't trying to ruin other people's fun. Even if the random player is way too underleveled for the mission and picked 4 support weapon strategems not knowing what they are and keeps getting stuck in respawn loops, everybody has been friendly and helpful, because that's the democratic way. Anybody who tries to make the lives of their fellow players miserable is a dirty traitor and will be court-martialed.
That's quite the escalation. Mr Beast isn't making people kill each other.
Good on them for acknowledging what was a pretty terrible response to player complaints. It's one thing to be firm in your balancing decisions, but it's another thing to demean your players over it.
That said, the responses from a lot of the players were also really over-the-top to begin with. Hopefully Arrowhead is able to remedy this combativeness between the studio and the community. A live service game really only does well when the developers are on the same wavelength as their players.
The mechs are cool, but I've got a feeling that their use case will be very situational. I'm more excited for the other vehicles that we should also be getting soon.
That fork seems like a cash grab considering it already has a Patreon.
Have they learned nothing from the lawsuit?
Even though it may seem disappointing, this was realistically the right call. You know what they say about broken clocks, and all.
They didn't say he couldn't be removed from the ballot, just that it's a federal issue to solve and not a state one. And had they allowed it, that precedent would have been abused almost immediately and been back in the court's review all over again and would have resulted in a ton of dramatic and divisive political theater in the meantime.
Though, it does highlight some significant flaws in our electoral process. There's a lot of conflict between what the states and what the fed should be able to do for elections. The whole system needs to be revamped, IMO. Why each state sets their own rules is baffling to me in the first place; the Presidency affects the entire country, not just the states, so I don't get why we aren't going by nationwide popular vote instead of "California's electors picked Candidate A even though the majority of the voters picked Candidate B, and Iowa voters did a collective Hokey Pokey in a big expo center and decided on Candidate C", etc.
I wonder why they settled
I'd imagine because they charged for access to piracy-specific functions of the tool and knew they couldn't argue a case.
It was a dumb move for them to add functionality for unreleased games in the first place, and an even worse move to charge money for it. It makes it a lot harder to convince a court that your tool is for backup/archival purposes only, when you have features that could only work with pirated materials.
Well ain't this just unfortunate timing.
I understand the idea of reclaiming a slur. But general audiences might not recognize what you're saying for what it is. And nothing stops a bad actor from making the same claims and using the terms in bad faith, hence why it's generally easier from all sides to use different verbiage.
51
Pilot, husband thrashed for 'torturing' 10-year-old domestic help in Delhi's Dwarka
(www.tribuneindia.com)
See the quick inspect-element mockup I put together for an example. I'm bad at design, but I think it gets the point across. Current implementation on left, suggested on right. Also, I'm using Kbin Enhancement Suite for the modifications to instance names, but I think they are even more useful for this demonstration.
How it could work: If the same link is submitted across multiple communities in your current view (subscribed, favorites, all, etc) within a certain time period (probably 24 hours), then have them automatically group themselves into the same box, along with a brief list of the duplicate threads and instances. Use whichever of the threads has the highest score as the one to fill the title and thumbnail for the grouped thread.
I didn't make a mockup for this, but when clicking the thread, it could then import the comments from each of the grouped instances. Options on the sidebar could show you each of the instances whose comments are being shown on that page, along with an option to filter them out of your current feed, and options to add your votes to each instance's thread.
EDIT: To add, as I'm seeing some confusion in the comments: I'm envisioning this as a strictly user-side bundling of threads. This would only bundle threads as they are displayed to the user in their own feed based on communities you're subscribed to. So if the same link were to be posted to 5 different communities you subscribe to, when you view the feed, you'll see those 5 links all bundled together. Though perhaps an option could also include seeing non-subscribed duplicates, as well.
view more: next ›
I disagree, you can see so much on the old layout specifically because it's a wall of text. The new layout is unnecessarily bloated and takes up your whole screen on every device you view it from, so you can barely see more than one or two posts at a time. It removes the ability for the user to freely scroll and look at things that interest them, and forces the user's attention onto exactly what the algorithm wants them to. The new layout removes a ton of agency from the user.