Welcome to my little kbin instance and account.

ゲームが好きです。配信もしています。気軽に楽しくやりましょう。ゲーム以外もいろいろな趣味があります。よろしくお願いします。Playing Games. Streaming Games. Games for everyone. I have some hobbies outside of games, too. Nice to meet you.

(He/Him/His)

#gaming #dnd #twitch #ttrpg #xbox #xboxSeriesX #games #Bilingual #casualGames #ConsoleGaming #dndj #dnd5e #adhd #日本語 #adhd

  • 2 Posts
  • 12 Comments
Joined 1 year ago
cake
Cake day: June 3rd, 2023

help-circle
  • @azezeB Some suggestions

    1. Dead By Daylight. 5 people with one being the Killer so you can rotate that if desired.
    2. Halo Infinite multiplayer can do 12 person parties for the “Big” map modes.
    3. I believe Lego Fortnite also lets you have up to 8. It’s more Minecraft and not a Battle Royale at all.
    4. Lethal company modded can support more than 4. That could be lots of fun.
    5. Retro FPS like Quake from various years. Just as a small distraction

  • @HarkMahlberg

    The technical details will determine what can and can’t be done, but from the Mastodon documentation:

    https://docs.joinmastodon.org/user/moving/

    Moving your account is the same as redirecting your account, but it will also irreversibly force everyone to unfollow your current account and follow your new account, if their software supports the Move activity. Your posts will not be moved, due to technical limitations. There is also a 30 day cooldown period in which you cannot migrate again, so be very careful before using this option!

    Depending on if k/m/bin receives a “Move” activity, it may be possible to update user blocklists based on the information in the “Move” activity. However, “Move” activity is generally only sent to existing followers. (I don’t know all the details on that) Activities are generally sent to an instance to handle, not individual user accounts, though, so I suspect this might not be as big of a hurdle as it might seem.

    Short answer: Maybe. Depends on how they “Moved”. It wouldn’t be simple to implement, however I don’t see anything preventing it in this particular case. You should open an Issue for feature request for it. I recommend including the above piece from the Mastodon documentation, however in your issue.


  • @ReverseModule

    As someone who really enjoys PeerTube, I also feel like the technical barriers to it being as popular as other platforms are a bit tougher to overcome.

    I would love for it to be more popular. I also know it’s really hard to convince content creators and live streamers to embrace it.

    I love PeerTube. I have been trying to help the projects however I can. I also know that the economics of moving to PeerTube is quite different. Very few people make money microblogging (Twitter). Very few people make money posting to Reddit.

    Streaming on Twitch or YouTube, or making content for YouTube can and for many people does bring in money, though. Creating an ecosystem where viewers are willing to pay, while increasing viewer counts of content so that sponsorships can be more common, all while trying to slowly convince people that we should be supporting things financially that up to now has been “free(not really, but experientially it ‘feels’ free)” is a lot of work.

    I plan on supporting PeerTube as much as I can in the future. I want it to grow. Maybe someday, it will get there. I can hope.


  • @e569668

    why it isn’t getting sent to rabbitea.rs

    If feddit.uk doesn’t know about rabbitea.rs, then it won’t send it there. The originating instance is responsible for sending it out, but it can only send to instances it knows are subscribed. This can result in some instances not getting new content if it originates on an instance other than the one that is the “home” for a magazine.

    And surely the destination magazine must be involved somehow to run rules on like, banned users?

    That depends. It depends on if the “home” instance federates out blocks. I don’t actually know if kbin federates out blocks (many Fediverse platforms don’t actually because it’s used as a vector for harassment and dogpiling and other very harmful behaviors), but the 2 cases are as follows:

    1. If Kbin (or the “home” instance platform) federates out blocks, then all subscribing instances will receive the block information. Whether or not they honor it or not is not guaranteed, but for simplicity sake, let’s assume they do.

    In this scenario, instances that receive the block will behave as you might expect: they won’t allow the blocked user to view the content in the magazine/community but will allow other users to view it. They also will not accept content into their local copy of the magazine from the blocked user.

    1. If kbin (or the “home” instance platform) does not federate out blocks, then other instances cannot know not to display content from a blocked account, nor do they know not to accept content created by a blocked account. The “home” instance will block such content from being displayed and added to the magazine and thus users on the “home” instance will not see the content, but users on other instances could, in theory, still see the content.

    Note: This is partially why the mod_log can be viewed. I’m not 100% sure of the details, but the home instance moderation decisions should be visible on other instances (or at least by visiting the magazine on the “home” instance itself) and moderators/admins should be able to take similar actions on their own local-copy of the magazine.


  • @chris

    This is by design. ActivityPub is a push model and it’s a Push-once (in general).

    What that means is that the instance that the creator/author of the content is on will push the content to all the other instances that it knows are subscribers to the “account/magazine” that the content is being pushed to.

    What that means is:

    • Feddit.uk will push the content to Feddia.io because that’s the “destination” account/magazine.
    • Feddit.uk will push the content to any instances that is also happens to know subscribe to the magazine “ukdtt”
    • Fedia.io will not re-push the content to all the instances that subscribe. That’s the responsibility of the instance that the content “originated” from, not Fedia.io