I just noticed that most episode pages on the web now only contain JavaScript, without any HTML content about the episode. Please tell me this is just temporary!

I’m using a custom piece of software that automatically titles all the links I post on my blog, and I list all the podcast episodes I’ve listened daily in my posts. The titles are parsed from the HTML, but the new JS-only pages don’t even have the episode title embedded in them!

For reference, here’s one episode where the page is just JavaScript: https://pca.st/nzceirq9

Here’s another one, which (as of this writing) still has actual episode-related content in the source code: https://pca.st/episode/b5553ab4-36d1-475e-bc30-b7fd4e0fe5e5

If this is a permanent change, it no longer makes sense for me to link to episode pages on Pocket Casts; I’ll have to go back to referring to various other podcast sites’ episode pages instead.

That nitpick corner bookshelf almost @standupmaths levels of slantingness

At least in the mobile app this (showing of posts that should be filtered out completely) seems to occur when those posts get loaded after tapping ”Load missing posts”. So it’s like the filters don’t get applied to posts loaded on demand: I just had one shown to me earlier with the ”matches filter”, ”show anyway” preamble, but now that I went to check the timeline on the same device again, said post was now filtered out completely. (It hadn’t been deleted in the meantime, I checked.)

(I couldn’t remember if the example in my web UI screenshots above was similarly loaded with ”Load missing posts”.)

Tuhtotien ja Teljotien liittymät veden vallassa. Myös Koskelantiellä vähän ennen Sulfiittikatua klv:llä samanlainen allikko.

Valopylvään paneeli auki. Ehkä aura rouhaissut ohi mennessään.

Trying to build v2.25.1 with `npm build:android` fails with what looks like a missing dependency. This was not an issue with v2.25.0, so the cause is some recent change.

The full log is below, but here’s what I think is the crucial part:

* What went wrong:
Could not determine the dependencies of task ':app:mergeReleaseNativeLibs'.
> Could not resolve all dependencies for configuration ':app:releaseRuntimeClasspath'.
> Could not resolve project :frameanimation.
Required by:
project :app > project :expo > project :expo-image
> No matching variant of project :frameanimation was found. The consumer was configured to find a library for use during runtime, preferably optimized for Android, as well as attribute 'com.android.build.api.attributes.AgpVersionAttr' with value '8.2.1', attribute 'com.android.build.api.attributes.BuildTypeAttr' with value 'release', attribute 'org.jetbrains.kotlin.platform.type' with value 'androidJvm' but:
- No variants exist.
> Could not resolve project :gif.
Required by:
project :app > project :expo > project :expo-image
> No matching variant of project :gif was found. The consumer was configured to find a library for use during runtime, preferably optimized for Android, as well as attribute 'com.android.build.api.attributes.AgpVersionAttr' with value '8.2.1', attribute 'com.android.build.api.attributes.BuildTypeAttr' with value 'release', attribute 'org.jetbrains.kotlin.platform.type' with value 'androidJvm' but:
- No variants exist.

fail.log

Czechoslovakia hasn’t existed in decades. Prague is the capital of the Czech Republic.

As per title. Unlisted posts can not be reblogged, but the web UI still shows a reblog icon for such posts, and it can be clicked. After spinning for a while it then returns to its initial state, which is confusing (especially if you’re unaware of the limitation of reblogging unlisted posts).

The official mobile client does better: there such posts apparently don’t have the reblog icon. An alternative solution is Mastodon’s (web UI’s) way of showing a boost icon, but disabling it (so that it doesn’t react to clicks).

(The instance I’m on is pixelfed.social. The most recent post I had this issue with was federated from https://vernissage.photos/@magda/7470629220893329794#)

Attached is a screenshot of one of my filters, and of a post on my timeline matching the filter (see the hashtags at the end). There’s nothing (at all) in the console log. My handle is @uusijani@mastodon.social. The post in this case apparently comes from a federated blog.

I have a feeling that most times I’ve seen posts that should have been filtered out, they’ve been boosted ones and not OC from people I follow. But obviously it could just be that I don’t follow many people who post about things that I like to hide with filters.

In at least the past couple of updates of Mattermost, the .deb package has changed contents of /opt/mattermost/client/root.html sometime after installing the update, which changes the file’s checksum. This is an issue for people like me, who run debsums --changed daily as part of monitoring the integrity of my server.

I’m not intimately familiar with Debian packaging, but I don’t think those (checksummed) installation files should change post-install. Maybe an unchanging template file should be installed instead, and the final file generated from that?

(I’ve inspected the file, and the only change from the package-provided one is an addition of ”js.stripe.com/v3” to aheader tag, so I’m pretty sure this is a packaging issue and not filesystem corruption or a malicious attacker.)

As a workaround, I can of course recalculate the new checksum, and update the .md5sums file where it’s listed accordingly, but… eww.

(Somewhat related: #26769)