Bring back what? It’s still around. I use Matrix channels for some topics that are bridged from IRC.

Same here. I only got my 14 because the battery on my 12 was starting to fade fast shortly before a trip to Europe, and the 14 is still holding up well.

I noticed that, too. Had to re set it in settings.

Conceptually I like this Eurovision knockoff, but even the thought of listening to and picking the top three of 72 songs is exhausting. Can we have semifinals?

Perhaps another useful option would be to show the poster’s name on reblogs, so it’s easier to spot reposting trends. As it is now, I have to open the post to see who made the re-post.

It’s one of the reasons I stopped following technology at Lemmy.world. So many reposts and no easy way just to swipe and make disappear, so I have to act on everything.

My first thought was a new block list for Lemmy or Mastodon admins.

I’ve updated my PWA to the latest version, and I don’t see this toggle. Perhaps it is specific to the native apps.

(Re-read the release notes. Yup, it’s native app only.)

Still using it as a self-hosted PWA over here. I’ve even made a script to fetch a version from git, cross compile it for my Pi and ship it over. Keep up the good work! :)

ETA - Since rebuilding my PWA host, I’ve had no issues with running the corepack inside of buildx. Dual-stack is enabled, so it’s a mystery what happened! Maybe the folks hosting corepack fixed an issue with their hosting.

Fingers crossed!

Weirder yet, posting this now didn’t require anything, neither did it when I posted here a week ago.

By the way, since I did the one build with IPv6 disabled, I’ve since re-enabled it, and subsequent builds seem to accept that corepack is cached and haven’t had further issues. Should it come up again, I’m going to have tcpdump running in the background just to see whether there is some host that the build process is trying to lookup that is returning bogus AAAA responses. (More often than not IPv6 problems stem from improper configuration either on the client or server side.)

I do run IPv6, but not exclusively!

Tacking “strace” onto the front of the docker build command gives me a lot of nice output before step 1, but at the crucial step 3, there’s nothing. However, I decided to temporarily disable IPv6 processing on the device, and lo and behold, it carries on without a problem.

That means either my IPv6 tunnelbroker or some of BuildKit’s services are having issues handling IPv6 traffic. (I was gonna say it was corepack, but that’s run even with BuildKit turned off.) Now to find a way to get the build to work with IPv6, but that’s my homework now.

Thanks for the tip!