AnyOldName3

joined 2 years ago
[–] AnyOldName3@lemmy.world 2 points 13 hours ago (1 children)

First, someone has to email licensing@xkcd.com to tell Randal Munroe that there's a potential licence violation so he can file a suit.

[–] AnyOldName3@lemmy.world 13 points 15 hours ago (3 children)

xkcd comics are available under a CC-By-NC 2.5 licence, so you've successfully pirated by not including attribution (as long as people can't tell at a glance that it's xkcd from the art style or comment thread you posted it to), but to seal the deal, it'd be a crime to sell it.

[–] AnyOldName3@lemmy.world 3 points 16 hours ago

A Spud apologist! Sabotage by a scarecrow was beyond Bob's control, and the cause of most problems.

[–] AnyOldName3@lemmy.world 12 points 2 days ago (3 children)

Most of the languages you've mentioned aren't systems languages, so don't make being a good language to write an OS in a high priority. More languages might be accepted in the future, but if they are, it'll be ones that are a natural fit for the problems they're solving.

[–] AnyOldName3@lemmy.world 6 points 2 days ago* (last edited 2 days ago)

Returns and refunds happened because the EU warned them that if they didn't, they'd create legislation so they'd have to, as they were already in a grey area under EU law. EA had a similar refund policy for games bought through Origin before Steam did.

Other than that, nearly everything you listed was done because it made business sense and would lead to more profit. Decoupling PC gaming from Windows by working on Linux means they're not at the mercy of Microsoft's whims, and was started at a time where it looked like Microsoft might make a version of Windows that could only install third-party software through the Windows Store. Discouraging kernel-level anti cheat discourages one of the last hurdles to Linux being able to play all Windows games. Supporting VR lets them still VR games through Steam.

Not being publicly traded lets them be concerned about their long-term profits above their short-term ones, so they won't do things that tarnish their reputation nearly as often as their competitors, and can do multi-year projects. They look good because their competitors are bad rather than because what they do is altruistic.

Edit: I just did some maths. The Steam Deck has sold somewhere around 5 million units and a Windows licence costs somewhere around $50 to an OEM with a volume licensing deal. Both these figures are approximate as I couldn't find precise numbers, but they're enough for a ballpark figure. This means that Valve have saved around $250 million by shipping the Deck with SteamOS instead of Windows. Even if my figures are way off, it's still a huge amount of money and goes a long way towards making all their work on Linux pay for itself.

[–] AnyOldName3@lemmy.world 1 points 3 days ago

Arch is at least more likely to update to a fixed version sooner, and someone getting something with pacman is going to be used to the idea of it breaking because of using bleeding edge dependencies. The difference with the Flatpak is that most users believe that they're getting something straight from the developers, so they're not going to report problems to the right people if Fedora puts a different source of Flatpaks in the lists and overrides working packages with ones so broken as to be useless.

[–] AnyOldName3@lemmy.world 23 points 3 days ago

People fall off rooftops fitting solar panels, burn to death repairing wind turbines that they can't climb down fast enough to escape, and dams burst and wash away towns. Renewable energy is much less killy than fossil fuels, but per megawatt hour, it's comparable to nuclear, despite a few large incidents killing quite a lot of people each. At the moment, over their history, hydro is four times deadlier than nuclear, wind's a little worse than nuclear, and solar's a little better. Fission power is actually really safe.

The article's talking about fusion power, though. Fission reactions are dangerous because if you've got enough fuel to get a reaction at all, you've got enough fuel to get a bigger reaction than you want, so you have to control it carefully to avoid making it too hot, which would cause the steam in the reactor to burst out and carry chunks of partially-used fuel with it, which are very deadly. That problem doesn't exist with fusion. It's so hard to make the reaction happen in the first place that any problem just makes the reaction stop immediately. If you somehow blew a hole in the side of the reactor, you'd just get some very hot hydrogen and very hot helium, which would be harmless in a few minutes once they'd cooled down. It's impossible for fusion power, once it's working, not to be the safest way to generate energy in history because it inherently avoids the big problems with what is already one of the safest ways.

[–] AnyOldName3@lemmy.world 2 points 3 days ago (2 children)

PowerShell has a system to sign scripts, and with its default configuration, will refuse to execute scripts, and with the more sensible configuration you should switch to if you actually use PowerShell, refuses to execute unsigned scripts from the Internet.

I suspect that most of the scripts you're referring to just set -ExecutionPolicy Bypass to disable signature checking and run any script, though.

[–] AnyOldName3@lemmy.world 8 points 3 days ago

That's misleading in the other direction, though, as PhysX is really two things, a regular boring CPU-side physics library (just like Havok, Jolt and Bullet), and the GPU-accelerated physics library which only does a few things, but does them faster. Most things that use PhysX just use the CPU-side part and won't notice or care if the GPU changes. A few things use the GPU-accelerated part, but the overwhelming majority of those use it for optional extra features that only work on Nvidia cards, and instead of running the same effects on the CPU if there's no Nvidia card available, they just skip them, so it's not the end of the world to leave them disabled on the 5000-series.

[–] AnyOldName3@lemmy.world 14 points 1 week ago

It does also get pushed by organisations that profit from fossil fuels as an excuse to never need to decarbonise as they can hypothetically just capture it all again later, which is dumb and impractical for a variety of reasons, including the one alluded to above. Some kind of Carbon sink will need to be part of the long-term solution, but the groups pushing most strongly want it to be the whole solution and have someone else pay for it so they can keep doing the same things as caused the problem in the first place.

[–] AnyOldName3@lemmy.world 3 points 1 week ago

A billion dollars worth of bitcoin isn't that much of the total amount of bitcoin any more, so any impact on the price would be because of people reacting emotionally to the news, not because they're was suddenly a flood of extra bitcoin in circulation.

[–] AnyOldName3@lemmy.world 1 points 1 week ago

The Free Software movement was generally a leftist objection to the limitations on computer use that capitalism was causing, and the open source movement was a pro-corporate offshoot to try and make the obvious benefits more compatible with capitalism (which it's been pretty successful at, even if it has reintroduced some of the problems Free Software was trying to stop in the first place). Anyone who's making a distinction between the two at the minimum is recognising that capitalism is why we can't have certain specific nice things, so it's not a huge leap to blame it for other problems, too.

As for a sensible middle ground, the Free Software movement designed its licences to work in the capitalist societies they operated in, so the incompatibility with corporate use has never been as big a deal as it's been made out to be. Corporations can use copyleft-licenced software just fine as long as they're not unreasonable about it. It's totally fine for a corporation to use a GPL tool internally and even have an internal fork as long as they put the source code for their internal fork on the company's file share so the employees using the tool can improve it if they get the urge. They can even sell products that depend on LGPL or MPL libraries if they make the source of the builds of those libraries they used available on their website or otherwise accessible to their customers (and use a DLL/.so/.dylib build of the library of it's LGPL). These restrictions are all less of a pain than making an MIT-licenced clone of an existing project, but companies have opted to make clones instead. The only bonus this gives them is that they can make it proprietary again later, and it has the added risk that one of their competitors could make a proprietary fork with a killer feature they can charge for, which isn't a nice risk. There are other benefits to investing in making your own clone of something, but they don't depend on the license it uses.

 

I've got a 3D printed project, and went over it with a couple of airbrushed coats of a 50/50 mix of Tamiya X-35 (their alcohol-based acrylic semi-gloss) and Mr Color Levelling Thinner. As far as I can tell, it looks good so far, but now the room next to the one I sprayed in smells of solvent a few hours later, despite extractor fans running. I knew the lacquer thinner was nasty, so bought a respirator, and haven't been in the room with the model without it (hence only knowing that the next room stinks), but would like to know when I won't need it anymore. The best I've been able to find with Google is the ten-minute touch-dry time, but I'm assuming the VOCs will take longer to be entirely gone.

 

Edit 1: I'm attaching the image again. If there's still no photo, blame Jerboa and not the alcohol I've consumed.

Edit 3: edit 2 is gone. However, an imgur link should now be here!

Edit 4: I promise the photo of some plugs does not contain erotic material (unless you have very specific and abnormal fetishes). I can't find the button to tell that to imgur, though. You can blame that on the alcohol.

Edit 5: s/done/some/g

Edit 6: I regret mentioning the dartboard, which was a safe distance below these sockets, and seems to be distracting people from the fact that one's the wrong way up. I've now replaced the imgur link with a direct upload now I'm back on my desktop the next day.

 

When I visit lemmy.world in either Firefox or Chrome, go to the log in page, enter my credentials, and press the Login button, it changes to a spinner and spins forever. No error is logged to the browser console when I press the button.

On the other hand, when using Jerboa on my phone, I can vote, comment and post just fine. That makes me think it's not an issue with this account.

I was briefly able to log in on my desktop a few days ago, but don't think I did anything differently when it worked.

Update

I tried again with my username lowercased, and with the password copied and pasted instead of autofilled, and it worked despite not working a few seconds earlier when I tried it the usual way. I'm going to log out and see which of the two things it was that made the difference.

Update Two

Copying and pasting the password while leaving the username with mixed case also let me in, so it's somehow related to the password manager autofill.

Update Three

I figured it out. I generated a password longer than lemmy.world's password length limit. When creating the account, it appears to have truncated it to sixty characters. When using the password manager to autofill Jerboa, it's also truncated it to sixty characters. When copying and pasting the password from the password manager manually, it truncated it to sixty characters, too. However, the browser extension autofill managed to include the extra characters, too, so the data in the textbox wasn't correct.

In case an admin or Lemmy developer sees this, I'd recommend:

  • Not limiting the password length. It should be hashed and salted anyway, so it doesn't increase storage requirements if it's huge.
  • Giving feedback when creating an account with a too-long password that it's invalid for being too long instead of simply truncating it. Ideally, the password requirements would be displayed before you'd entered the password, too.
  • As mentioned by one of the commenters, giving feedback when an incorrect password is entered.
 

Test post for @testman@lemmy.ml to test posting.

view more: next ›