[-] frezik@midwest.social 2 points 11 hours ago

Oh, yeah, a lot of people made that mistake. It was badly named.

[-] frezik@midwest.social 11 points 15 hours ago

Lying through its teeth.

There was a bunch of DOS software that runs too fast to be usable on later processors. Like a Rouge-like game where you fly across the map too fast to control. The Turbo button would bring it down to 8086 speeds so that stuff is usable.

[-] frezik@midwest.social 3 points 1 day ago

FWIW, retirement studies would suggest a 4% withdrawal rate the first year, and increasing for inflation each year after. There are some other ways to go with this, but it's a good starting place.

[-] frezik@midwest.social 2 points 1 day ago

To where? Right wing fascism is on the rise pretty much everywhere.

[-] frezik@midwest.social 35 points 1 day ago

Some hackers DoS the code. This guy DoS's the corporate process.

[-] frezik@midwest.social 3 points 1 day ago

Significant digits of accuracy befuddles everyone.

[-] frezik@midwest.social 6 points 1 day ago

Flame throwers are allowed as long as they're not aimed at civilians. Thermite is just another type of flame when it comes down to it.

[-] frezik@midwest.social 5 points 1 day ago

There's downsides to the companies, though. Interviewing new candidates takes money, and takes time away from people already on the team. If everyone is switching jobs to get a higher salary, then companies aren't saving anything in the long run. They also have a major knowledge base walking out the door, and that's hard to quantify.

It's a false savings.

If I were to steel man this, it'd be cross-pollination. Old employees get set in their ways and tend to put up with the problems. They've simply integrated ways to work around problems in their workflow. New people bring in new ideas, and also point out how broken certain things are and then agitate for change.

This, I think, doesn't totally sink the idea of the "company man" who sticks around for decades. It means there should be a healthy mix.

[-] frezik@midwest.social 20 points 1 day ago

I keep waiting for someone to come up with some kind of explanation for this that even sorta makes sense. No, as far as I can tell, companies just work this way.

[-] frezik@midwest.social 52 points 2 days ago

And they validated this data 4 times. It's really good data.

[-] frezik@midwest.social 36 points 2 days ago

This might be the most evergreen article The Onion has ever published.

6
Link broken in app (midwest.social)
submitted 4 months ago by frezik@midwest.social to c/summit@lemmy.world

Not 100% sure if this is a Summit issue or something in Lemmy more generally. Here's the post in question:

https://midwest.social/post/10123989

The link to the blog works on my instance for the desktop. Several other users were reporting the link being broken, and it does break for me on Summit, as well.

When I hit the link on Summit, the requests on the server are GET /api/v3/post?id=2024 and GET /api/v3/comment/list?max_depth=6&post_id=2024&sort=Top&type_=All. It looks like it parsed out the "2024" from the original link and tried to use that in a Lemmy API call.

3

Here's the post in question: https://midwest.social/post/10123989

Which linked to my blog here: https://wumpus-cave.net/post/2024/03/2024-03-20-moores-law-is-dead/index.html

On my instance (midwest.social), this works fine. However, some other users were reporting a broken link, and I also see a broken link when using my mobile app (Summit). When it breaks, I see these calls in the server logs:

  • GET /api/v3/post?id=2024
  • GET /api/v3/comment/list?max_depth=6&post_id=2024&sort=Top&type_=All

Which appear to be Lemmy API calls with some of the actual link data built in.

32
350
view more: next ›

frezik

joined 1 year ago