If you’re sick of issues being automatically closed due to inactivity, I present the latest innovation: repositories being automatically deleted due to inactivity

GitLab Castopod project page with a warning that, due to inactivity, the project is scheduled for deletion on June 30, 2027. — Open image attachment ⁨1⁩ of ⁨1⁩
GitLab Castopod project page with a warning that, due to inactivity, the project is scheduled for deletion on June 30, 2027.
en
😆3😢1

Replying to @⁨liaizon@wake.st⁩

@liaizon @benjaminbellamy Yeah, good call, codeberg would be a nicer place for such a project.
Btw, a fix for castodon federation is partially live (see episode or screenshot), but there is still a few things I'm improving over there, and Plamenu went public at codefloe.com/plamenu/plamenu
Not asking to be my PR department, but if fediday is still happening perhaps there might be some reason to mention it or something, I dunno

Replying to @⁨lnkr⁩

@lnkr @benjaminbellamy this is sorta amazing codefloe.com/plamenu/plamenu/i
I guess this is really a spesific shim until Castopod adds the audio attachment directly to the AP JSON but it's sorta amazing how straight forward it was for you to pull it from the preview player. I guess it's similar to how you added the extra peertube caching compatibility

Summary card of an issue titled "interop: Castopod episode posts render without audio playback" in repository plamenu/plamenuCodeFloe - the Forgejo developer platforminterop: Castopod episode posts render without audio playback### Software - Peer: Castopod at `solarcast.cc` - The public object was fetchable without authorized fetch ### Activity flow 1. `@solarcast@solarcast.cc` publishes a Castopod episode as a Note linking to the episode page. 2. The Note federates to Plamenu and appears in the timeline. ...

Replying to @⁨liaizon@wake.st⁩

@liaizon
It’s similar to some extent. Come to think of it, custom shims might be the bread and butter of my entire project, helping me work around my own expectations, ActivityPub, and established best practices, (hopefully) for the sake of interoperability and accessibility. And tbh it wasn’t exactly straightforward, rather it was one of those instances where I was lost for a moment and kind of had to turn to some pesky AIs to figure out the shortest path and E2E-test a potential solution. Perhaps not the best one, but a solution nonetheless.
I really hope that, eventually, I’ll be able to turn shims like these into PRs that improve interoperability and accessibility for the whole Fediverse the same way I was randomly able to to push for quoteposting improvements in Mitra
@benjaminbellamy

Replying to @⁨lnkr⁩

@lnkr I suppose that if you set up a GitLab instance and you only allow people that you trust to use disk space, you shouldn't enable this setting: "You can configure GitLab to automatically delete dormant projects after a specific period of inactivity." https://docs.gitlab.com/administration/dormant_project_deletion/
GitLab DocsDormant project deletion | GitLab DocsConfigure deletion of dormant projects.