• 5 Posts
  • 84 Comments
Joined 1 month ago
cake
Cake day: July 3rd, 2025

help-circle


  • I already have a bunch of my own feeds. My issue is that from UX perspective those work best when I have them opened as separate tabs on laptop. In PWA there are no tabs. And in the feeds dropdown not all are shown, only a handful. So in order to check what’s new in a bunch of feeds (too big to get notification about all that’s happening in those) in PWA, I have to

    1. Click the feeds
    2. Click my feeds
    3. Click the one I want to check
    4. Repeat for the next one
    5. And next one

    Being able to switch between my feeds like between “subscribed” and “local” would be much better










  • So the plan is kind of like porting GameBoy Pokemon/Final Fantasy game (you walk on the map, then suddenly the combat begins with different mechanic) to a TTRPG?

    I’m not very familiar with commander format, but I don’t think it’s one of the fastest ones. So if I were doing this, I would try to minimize the mechanics between the combat. I would take Blades in the Dark, strip all the setting, playbooks, distill it to a bunch of approaches basically and reskin them as it fits the game.
    And then maybe take a look at Traveller quadrant(?) generation tools for coming up with map hexes? That one might be a bad advice, I’m not using hexes in general







  • Ah, you mean for fediverse to work as an LDAP?

    My point is Let’s imagine we have a board on some instance. You use your account on another instance to ask the owner of the board to give you access to the board. The contents of the board are, IMO in most cases of such boards, “members only”. So any changes happening inside should not be sent out to federating instances. Otherwise, privacy of such boards would be at the mercy of privacy of other instances. If restricted changes were sent out, technically speaking, any server it federates to can choose to show that content to everyone. Which means you won’t be able to access the contents via any other instance. Apart from the logging in part, you will still need to go to the instance hosting the board. Unless it would be for publicly accessible boards only, like codeberg issues. That use-case could work