• 2 Posts
  • 26 Comments
Joined 2 years ago
cake
Cake day: June 22nd, 2023

help-circle
  • Yes, that’s what I wanted to know. So alas, no out-of-the-box magic for me…I find it incredibly frustrating that in 2023 one can’t simply copy-paste text from one local console to another. It seems like a basic function for a terminal-based *nix systems which doesn’t exist. I know it’s complicated even at the first glance, with huge security implications (like copying text in the root terminal and pasting it to a user one) but I believe it’s all solvable



  • It’s interesting, as most players I know consider bonds mechanics as “least working” in DW. I prefer Homebrew World implementation, where people ask set of questions. For example, questions from “Fighter” playbook:

    • Which of you have I sworn to protect?
    • Which of you am I most worried about?
    • Which of you has my back?
    • Which of you has been flirting with me?

    So, fighter player asks them one by one, and any other player can answer “it’s me” when he likes the question and want to establish that bond. Then they talk a little bit discussing details, and switch to next answer / next player.

















  • Meta-communities in two flawors:

    • user/UI-based, where the user can create an entry in his preferences, add a bunch of communities there and set which one will be its “facade”. The main “con” here that every single user should do a lot of work by himself
    • server-based, where you can create new meta-community, add your own community there, and send invites to all similar communities to join. Every community that joined could(should?) be removed from discovery, but be visible as “nested”. Search by its name should lead to meta-community. Ownership of meta-community should belong to its members in term that not a single one could delete it or make any harm. Meta-community exists while there’s at least one member in it.

    Important part that one to be careful about combining feeds. Small cozy community can just dissolve in valley of posts from much larger one. The thing is controversial, on one hand it’s really handy to see all the posts all at once, on the other hand - it can kill smaller communities, as their creators will lose the sense and desire to have them maintained. There are different solutions:


  • Meta-communities in two flawors:

    • user/UI-based, where the user can create an entry in his preferences, add a bunch of communities there and set which one will be its “facade”. The main “con” here that every single user should do a lot of work by himself
    • server-based, where you can create new meta-community, add your own community there, and send invites to all similar communities to join. Every community that joined could(should?) be removed from discovery, but be visible as “nested”. Search by its name should lead to meta-community. Ownership of such meta-community should belong to its members in term that not a single one could delete it or make any harm. Meta-community exists while there’s at least one member in it. Picture of meta-community in discovery could be anything, one can take it from most populated member community, but user could be able to change it in his preferences to any other member.

    Important part that one to be careful about combining feeds. Small cozy community can just dissolve in valley of posts from much larger ones. The thing is controversial, on one hand it’s really handy to see all the posts all at once, on the other hand - it can kill smaller communities, as their creators will lose the sense and desire to have them maintained. There are different solutions:

    • Make feed combined, but give posts from smaller community higher priority
    • Make user to switch feed manually and let hit set “default” to show when you open meta-community
    • Give user a choice between two

    To me, manual changing feeds feels more healthy for a smaller ones.