OUCH my thighs hurt!

I loved it! 😄

you ah, probably shouldn’t donate anymore money to the project that’s been talking shit behind your back so frequently that the person behind their PR account felt that saying “ah, another high-quality mastodon discussion” and trying to redefine slop to be “not what we’re currently doing with AI, the thing our marketing said our application doesn’t have at all” was normal and a good idea on mastodon

@GuitarSith @geoffduncan @ambergrey Working in an otherwise well equipped four track studio in the eighties, we'd put the rhythm tracks down on a stereo pair, use a track for lead vocals and the other for instrumental breaks or backing vocals or (shudder) both.

Sometimes we even overlaid simple keyboard pads during the mix which often required three pairs of hands.

Here's an example, rather degraded by spending twenty years on a cassette before it was digitised. Shame about the kick.

@lightweight Would they be wrong?

they don’t need your money anymore, that’s what they’re signaling with this

they don’t give a shit that you like libreoffice or that you use it at all

they saw your applause and it made them angry because you were applauding the wrong thing

Hollo security updates: 0.8.17 and 0.9.25

If you run Hollo, update to 0.8.17 or 0.9.25 now. These releases fix GHSA-r48c-xx2h-fv4g, a DNS rebinding vulnerability in Fedify that could bypass Hollo's server-side request forgery (SSRF) protection and cause requests to reach internal services.

Fedify checked that a hostname resolved only to public addresses, then let the HTTP client resolve it again when connecting. An attacker controlling the hostname's DNS answers could return a public address for validation and a private or loopback address for the connection. Redirects and alternate-document links had the same gap.

The affected Fedify paths used by Hollo include remote document loading (authenticated or not), outbound activity delivery, and WebFinger lookups. On Node.js, which Hollo uses, the fix restricts connections to addresses that passed validation. Hollo's ALLOW_PRIVATE_ADDRESS=true option still permits private destinations; leave it unset for public federation. For full technical details, see the Fedify security announcement and the advisory linked above.

All releases on the supported Hollo 0.8.x and 0.9.x lines up to and including 0.8.16 and 0.9.24 are affected. 0.8.17 and 0.9.25 are the first fixed releases and the latest on those lines, incorporating Fedify 2.1.31 and 2.2.20 respectively. Hollo 0.7.x and earlier are no longer supported under the Hollo security policy; operators on those lines should move to a supported release.

For 0.8.x deployments, update to 0.8.17:

docker pull ghcr.io/fedify-dev/hollo:0.8.17

For 0.9.x deployments, update to 0.9.25:

docker pull ghcr.io/fedify-dev/hollo:0.9.25

After pulling the image, recreate your Hollo container using the new image. With Docker Compose, update the image tag in your Compose file and run docker compose up -d. For source deployments, check out the corresponding release tag, run pnpm install --frozen-lockfile using the pnpm version pinned in that tag's package.json, run pnpm run build, and restart the server.

If you have a large 0.9.x database and are upgrading from a release before 0.9.20, follow the 0.9.20 index preparation instructions before starting the new version to avoid blocking writes during the new version's automatic migration.

Thanks to @finalchild for reporting the DNS rebinding issue to the Fedify project.

If anything is unclear, ask below.

That’s why I have this account. I only have to break it out once or twice a year, honestly. For the most part out server is pretty stable, but then every now and then, a rare Azorian moss creeps in though the window hosting the server, and begins to colonize. This results in much delicate work, as @ProdigalFrog@slrpnk.net and @poVoq@slrpnk.net carefully scrape the moss off the motherboards, using hori-hori knives imported directly from Japan. They then coax the moss onto several 9x13 Pyrex dishes loaded with a home made agar and begin the trek up Mount Pico, to relocate the moss to its natural habitat. This is only done under light or a full moon and with much chanting. If done right, a Satyr emerges from the bushes (erect phallus and all), playing melodic flute music, and thanks them for restoring the nomadic moss back to the wild. After a few moments of awkward silence for both the admins walk back down the slope, wondering what actually just fucking happen, and how this became part of the routine maintenance of the server.

@violetmadder Spot on.

@PhoenixSerenity

Especially when the devices are deliberately designed for addictive, unhealthy crap.

oops, your PR account accidentally revealed that your team hates your community

oof, one might say you had one job

If it helps, one positive thing on which you haven't self-censored is that I've been prompted to learn the term "doomerism."

(Having done that: if "doomerism" isn't "shitting on" other things in turn, then what do you mean by "shitting on"? Perhaps I'm positioned to learn another term!)

that doesn’t imply that libreoffice isn’t all in on slop by the way

the PR account’s still official, even if the person behind it is a dickhead embarrassing themselves online and making the project look horrible

libreoffice’s anti-AI marketing statement was very specifically crafted: there’s no AI features in their office suite. they didn’t say anything about the codebase.

when that proved to be extremely popular, they learned nothing from the positive feedback they got. in fact, the feedback being mostly “good, don’t ever slop up your codebase” appears to have pissed off the person running the PR account.

it has been 0 days since an official FOSS PR account on mastodon was just some dickhead’s personal alt account

Also, my favorite set as a child, which had bobbleheads for the 3 astronauts:
https://www.youtube.com/watch?v=4k22cUbyLfY
#lego

@delve 😊

Keep it short for today... Next up in Linux's initialization sequence might (this can be disabled at compiletime) be initializing the jump-labels!

With appropriate locks grabbed & after sorting the jump label table (as well as checking flag to see this hasn't already run) it does so by iterating over an build-generated table.

0.5/1.5!

@whitequark @glyph let me get back to you about this in approximately 23 months

@aesthr And there you go again

@PhoenixSerenity

Has someone got Rayven watching mid-century MGM films?

https://www.youtube.com/watch?v=ftDPrCfYESo