![](https://kbin.melroy.org/media/18/2d/182d7ae58ce10a5edd60c5f7de4df1d5dd16a9f6d7be77250b54fa5f0c727182.png)
![](https://lemmy.ml/pictrs/image/st9xYggWap.png)
A fun story: I was curating my magazine on Melroy’s instance and didn’t butt heads with any regression when he switched from Kbin to Mbin. Nice to see priorities set straight on migration!
🎞 Video Editor
🎨 Computer Graphics Artist
🎓 Frontend Mentor
💌 FOSS Enthusiast
A fun story: I was curating my magazine on Melroy’s instance and didn’t butt heads with any regression when he switched from Kbin to Mbin. Nice to see priorities set straight on migration!
In retrospective, it’s a practical decision to move away from downtimes, especially seeing as development is so rapid now.
We might do a mirror to Codeberg to avoid a complete dependency on GitHub, while accepting PRs on the side. Priorities tell us to postpone this idea in favor of long-awaited changes and fixes, though! 😉
It’s a fun idea to explore, which is why I didn’t nod it off. 😄 Imagine: PeerTube channel as a magazine (under the hood, it’s a link between video posts made by actor/boosted by ActivityPub group and magazine entries). Not only we’d have a way to preview several videos on a singular page, but also see description and likes. There is certainly a room for improvement in this model, just leaving it here before I forget.
Hello! I had the same question and I’ve got a perspective from one fellow contiributor: Matrix thread. (There’ll probably be an error when you first open it: join the room with your account and try my link once more.)
What about “We Fedicast”?