![](/static/253f0d9b/assets/icons/icon-96x96.png)
![](https://fry.gs/pictrs/image/c6832070-8625-4688-b9e5-5d519541e092.png)
Season’s the reason!
Season’s the reason!
This is basically asking why anyone would live in or near a city like Los Angeles or New York City when Minot exists and has everything you could possibly need.
If you had to look up where Minot even is, you’ve proven my point.
Say what you will about whether living near the proverbial big city is worth it or not. But it cannot be denied, there is a world of experiences on offer at larger platforms that a smaller platform simply cannot provide. Network effect can be a cruel mistress.
I’m pretty sure they’re referring to the concept of defederation and how that can splinter the platform.
Bluesky is ““federated”” in largely the same ways as Mastodon, but there’s basically one and only one instance anyone cares about. The federation capability is just lip service to the minority of dorks like us who care.
To the vast majority of Twitter refugees, federation as a concept is not a feature, it’s an irritation.
Happy Debian daily driver here. I would never ever recommend raw Debian to a garden variety would-be Linux convert.
If you think something like Debian is something a Linux illiterate can just pick up and start using proficiently, you’re severely out of touch with how most computer users actually think about their machines. If you even so much as know the name of your file explorer program, you’re in a completely different league.
Debian prides itself on being a lean, no bloat, and stable environment made only of truly free software (with the ability to opt-in to nonfree software). To people like us, that’s a clean, blank canvas on a rock-solid, reliable foundation that won’t enshittify. But to most people, it’s an austere, outdated, and unfashionable wasteland full of flaky, ugly tooling.
Debian can be polished to any standard one likes, but you’re expected to do it yourself. Most people just aren’t in the game to play it like that. Debian saddles questions of choice almost no one is asking, or frankly, even knew was a question that was ask*-able*. Mandatory customizeability is a flaw, not a feature.
I am absolutely team “just steer them to Mint”. All the goodness of Debian snuck into their OS like medicine in a kid’s dessert, wrapped up in something they might actually find palatable. Debian itself can be saved for when, or shall I say if, the user eventually goes poking under the hood to discover how the machine actually ticks.
Everything works the same, times of website incompatibility are long gone.
Not completely true. It’s mostly true. I’ve daily driven Firefox for years, and the number of websites I’ve crossed that wouldn’t function in it correctly but would work just fine in Chrome was very slim… but not zero. Definitely not comparable to the complete shitshow of the 90’s and 00’s. That’s true. But it’s not a completely solved problem.
And with Mozilla’s leadership practically looking for footguns to play with combined with the threat of Google’s sugar daddy checks drying up soon due to the antitrust suit (how utterly ironic that busting up the monopoly would actually harm the only competition…), that gap can get much worse in very little time if resources to keep full time devs paid disappear.
I recently had a rather baffling experience trying to preemptively avoid this by downloading the stupid app right away, only to discover I needed the website version anyway.
I was attempting to add my Known Traveler Number to an already booked trip with Southwest Airlines, booked by someone else. I was able to link the trip to my account right away in the app, no issue. And I could see the KTN field for my ticket sitting there, empty, greyed-out, and not interactible. I opened up the moble version of their website, completely unsurprised to find it was identical to the app, except for the detail that the KTN field there was functional. Put in the information, changes reflected in the app instantly, and I was in the TAS-pre line that afternoon.
Why did the two versions obviously built from the same codebase have two different sets of capabilities? Why was the website the more capable of the two this time? I have no clue. All I know is I never want to be a developer at a corporation where I’d have to be responsible for this flavor of trash.
The more egalitarian principle would be to not assume. I won’t deny that. People from more minority locales have every right to be upset at being marginalized.
But at the same time, whenever I read passive aggressive comments on socials from residents of crown countries or from EAASL people around the world bitching about US defaultism as if people are doing it just to be ignorant dicks, I can only think to myself, “Uhh, hello? What do you think the demographics of this space were? What did you expect?”
Americans are hardly the majority of the world’s English speakers, but for all the reasons you listed, they tend to remain a massive plurality, if not an outright overwhelming majority, of any mainstream online English language platform. No, that’s not a license to perpetuate US defaultism. But like… read the room, people. Your good fight is far more uphill than you seem to think it is.
I’ve seen at least one company press kit in rules on how to display their logo refer to it as “respect distance”.
I recognize three kinds of comments that have different purposes.
The first kind are doc block comments. These are the ones that appear above functions, classes, class properties, methods. They usually have a distinct syntax with tags, like:
/*
* A one-line description of this function's job.
*
* Extra details that get more specific about how to use this function correctly, if needed.
*
* @param {Type} param1
* @param {Type} param2
* returns {Type}
*/
function aFunctionThatDoesAThing(param1, param2) {
// ...
}
The primary thing this is used for is automatic documentation generators. You run a program that scans your codebase, looks for these special comments, and automatically builds a set of documentation that you could, say, publish directly to a website. IDEs can also use them for tooltip popups. Generally, you want to write these like the reader won’t have the actual code to read. Because they might not!
The second kind is standalone comments. They take up one or more lines all to themselves. I look at these like warning signs. When there’s something about the upcoming chunk of code that doesn’t tell the whole story obviously by itself. Perhaps something like:
/* The following code is written in a weird way on purpose.
I tried doing <obvious way>, but it causes a weird bug.
Please do not refactor it, it will break. */
Sometimes it’s tempting to use a standalone comment to explain what dense, hard-to-read code is doing. But ideally, you’d want to shunt it off to a function named what it does instead, with a descriptive doc comment if you can’t cram it all into a short name. Alternatively, rewrite the code to be less confusing. If you literally need the chunk of code to be in its confusing form, because a less confusing way doesn’t exist or doesn’t work, then this kind of comment explaining why is warranted.
The last kind are inline comments. More or less the same use case as above, the only difference being they appear on the same line as code, usually at the very end of the line:
dozen = 12 + 1; // one extra for the baker!
In my opinion, these comments have the least reason to exist. Needing one tends to be a signal of a code smell, where the real answer is just rewriting the code to be clearer. They’re also a bit harder to spot, being shoved at the ends of lines. Especially true if you don’t enforce maximum line length rules in your codebase. But that’s mostly personal preference.
There’s technically a fourth kind of comment: commented-out code. Where you select a chunk of code and convert it to a comment to “soft-delete” it, just in case you may want it later. I highly recommend against this. This is what version control software like Git is for. If you need it again, just roll back to it. Don’t leave it to rot in your codebase taking up space in your editor and being an eyesore.
That’s the thing, though. I computed from the claimed figure above of 13 billion net income. The costs are already accounted for.
I’ve been told we have state senators who openly claim to only be there to keep speeding tickets low.
If you make $50k/yr after taxes, the equivalent fine would be on the order of about $120.
Where I’m from, that’s a speeding ticket.
I still won’t forgive Shopko for consuming Pamida and ultimately taking the remnants of Pamida down with it.
I’m surprised to see on Wikipedia that Shopko actually owned Pamida basically the entire time I was growing up, they just ran it independently. They even broke up breifly before re-merging later. The second merger sent it all to shit, though. “Shopko Hometown” my ass.
I drive Linux for a similar reason to why some people prefer driving manual transmission cars to automatics.
Automatic transmission cars are ideal for a certain kind of driver that has no interest in how the machine actually works, they just want the machine to do its job as smoothly as possible without them having to think about it. Not bothering with the details is the whole point.
For those of us who do have an interest in knowing how the vehicle works, automatics become kind of suffocating. They’re designed to only ever behave in certain specific ways. If there’s a weird niche thing that we know is possible for the machine to do with manual control, but the automatic system doesn’t support, you’re just SOL. You can’t. This starts coming up in all sorts of annoying little ways, increasing in frequency as your knowledge increases. Death of a thousand cuts. You start feeling like you’re not really driving this car, you’re being taken for a ride.
Windows is like the automatic. It is a black box designed to allow people who don’t care how the computer works to use the computer. To prevent morons from breaking the internal components, they put up barriers around everything and tell you to keep out.
Linux is like the manual. Yes, it does demand more finesse and active knowledge about how the computer works to drive properly. But you’re in maximum control of it. If you want to pop the hood and tinker with every facet of its innards for whatever reason, it does not attempt to stop you. It’s all open, laid bare for you to do whatever you want with it.
Linux has a lot of options available to make it more automatic like Windows, if you want it. The difference is that the automatic-ness is completely optional in Linux. Imagine a car that can be automatic most of the time when you don’t care, but can become manual at the drop of a hat when you need it. Linux can be that if you want it to be. Windows can’t.
It’s speculated that the patent in question (or one of) is one that essentially protects the gameplay loop of Pokémon Legends Arceus.
https://ipforce.jp/patent-jp-P_B1-7545191
Running the first claim of the invention through Google Translate yields this massive run-on sentence description:
The computer causes a player character in a virtual space to take a stance to release a capture item when a first category group including a plurality of types of capture items for capturing a field character placed on a field in a virtual space is selected based on an operation input of pressing an operation button, and causes a player character in the virtual space to take a stance to release the capture item when a second category group including a plurality of types of combat characters that engage in combat is selected, and determines an aiming direction in the virtual space based on a directional input, and further selects the capture item included in the first category group when the first category group is selected, and the combat character included in the second category group when the second category group is selected, based on an operation input using an operation button different from the operation button , and causes the player character in the virtual space to take a stance to release the capture item when a first category group including a plurality of types of capture items for capturing a field character placed on a field in a virtual space is selected, and determines an aiming direction in the virtual space based on an operation input using an operation button different from the operation button, A game program which, based on an operation input of releasing the operation button pressed when having the player character perform an action, has the player character perform an action of releasing the selected capture item in the aiming direction if the capture item is selected, and has the player character perform an action of releasing the selected combat character in the aiming direction if the combat character is selected, and when the capture item is released and hits the field character, makes a capture success determination as to whether the capture is successful, and when the capture success determination is judged to be positive, sets the field character hit by the capture item to a state where it is owned by the player, and when the combat character is released to a location where it can fight with the field character, starts a fight on the field between the combat character and the field character.
Essentially, Nintendo has a patent on video games that involve throwing a capsule device at characters in a virtual space to capture them and initiate battle with them. In other words, they have a patent on the concept of Poké Balls (as they appear and function in Legends Arceus, specifically).
Palworld has “Pal Spheres”, which are basically just Poké Balls with barely legally distinct naming.
If this sounds like an unfairly broad thing for Nintendo to have a patent on, I’m not so sure I agree. It’s not like they’re trying to enforce a blanket patent on all creature collectors. Just the concept of characters physically throwing capsule devices at creatures.
If you think about it, that’s kind of the one thing that sets Pokémon apart from others in the genre. If there’s anything to be protected, that’s it. It’s literally what Pokémon is named after–you put the monster in your pocket, using the capsule you threw at it.
Palworld could have easily dodged this bullet. They claim they aren’t inspired by Pokémon, and that they’re instead inspired by Ark: Survival Evolved. Funny, then, that Ark doesn’t have throwable capsules, yet Palworld decided to add them. I’m not sure I buy their statement. And if this is indeed the patent being violated, I don’t think a court will buy it either.
I’m not trying to be a Pokémon apologist here. I want Palworld to succeed and give Pokémon a run for its money. But looking at the evidence, it’s clear to me Pocketpair flew a little too close to the sun here. And they’re kind of idiots for it.
I’m just surprised they aren’t getting nailed for the alleged blatant asset theft.
The primary thing I hate about them is that every snap package appears to your system as a separate mounted filesystem. So if you look in your file explorer, you can potentially see dozens of phantom drives clogging up your sidebar.
Debian Testing.
Learning about the xz backdoor was a fun week.
Surprised how, of all the people who took the bait, not a single one of them complained about systemd.
My beard isn’t long enough to have an opinion about systemd. All I know is all my homies hate systemd for some reason.
Stop threatening. Commit. Take the leap. A lot of us here are already on the other side and we’ll help you find your footing.
That sounds worse than I thought it was. I just assumed Mastodon was like Lemmy, where every instance federates with every other instance basically by default and there’s only some high-profile defed exceptions.
A Fediverse where federations are opt-in instead of opt-out sounds like actual hell. Yeah, more control to instances, hooray, but far less seamless usability for people. The only people you will attract with that model are the ones who think having upwards of seven alts for being in seven different communities isn’t remotely strange or cumbersome. That, and/or self-hosting your own individual instances. Neither of these describe the behavior of the vast majority of Internet users who want to sign up on a platform that just works with one account that can see and interact with everything.