Kobolds with a keyboard.

  • 2 Posts
  • 158 Comments
Joined 1 year ago
cake
Cake day: June 5th, 2023

help-circle


  • I’d hardly describe this as the product of a ‘great mind’, but I do think it’s important to discuss alternative ways of doing things. There’s some good reasons voiced here for why this (as written) is impractical, and it sounds like a solution with similar goals but better implementation is in the works, so that’s great to see. My favorite thing about Lemmy is that you can post something a bit out there like this and have a legitimate discussion about it; if this were Reddit, it’d have 400 downvotes and a bunch of replies telling me to kill myself, and that’d be the end of it.




  • In this system, each community needs moderators from each instance it is on. A small instance run by one person would face a challenge finding people to moderate potentially hundreds of communities.

    Each instance would be responsible for moderating its own posts, so a single user instance wouldn’t need a moderator at all unless other instances were failing to moderate their content, but I agree, this is a hurdle, and would make it easier for bad actors to go to tiny instances and post spam.

    You mention that a user who doesn’t like their instance’s moderation can use a different instance, but this isn’t easy. There’s no account migration at the moment. This is more of an issue with the lack of that functionality, since there are many other reasons people would want to switch instances.

    Sorry, I might’ve been unclear - I simply mean that you could visit the community from your instance via that instance - e.g. [yourcommunity]/c/[email protected] - to see lemmy.world’s “view” of the community. Your account would still exist on your own instance.

    If this was implemented, presumably it would require merging all existing communities that share names.

    A fair point; while it’d benefit some communities to have their content combined, it would not benefit others; this is a very valid criticism.


  • So all the spam and CSAM would have to be taken down by each individual instance.

    Or only by the instance from which they were posted. If an instance is a moderation graveyard and is generating CSAM spam, it probably just needs to be defederated from, but I agree that the necessity to rely on local moderators to cleanly remove a post is a problem with the proposal.

    Would also somehow have to find a way for instances to pull the hashtags out of every federated instance too.

    If each instance shared a list of communities that it hosts with each instance that is aware of it on first discovery and periodically thereafter, it would assist with this. Wouldn’t need to duplicate the content, just share a list of communities that exists. (I think that lack of duplicated content would actually be an improvement over the current system where, unless I’m mistaken, content is being duplicated, but I might also have an imperfect understanding of how it functions now.)


  • Your proposal seems to target the same issues as with multi-community support https://github.com/LemmyNet/lemmy/issues/818, which just got 6000€ funding from NLnet. Which seems to be a cleaner way of achieving the same goal.

    That’s great, maybe it’s (or will at some point in the future be) a non-issue, then. (For what it’s worth I did search for similar things before posting this, but apparently didn’t hit on the right search terms.)

    Some suggested points are also against ActivityPub standard.

    I’m not familiar enough with the intricacies of ActivityPub to be able to comment on that; this is obviously not a set-in-stone implementation, and it sounds like some version of the underlying idea is possible, judging by the above.




  • The only things I’ve found that just straight up don’t work on the deck are things with draconian anti-cheat (which don’t work on Linux in general, not just the deck), and very old titles that have weirdly restrictive resolutions or control schemes or whathaveyou. Some games require some tweaking (mostly around controls, occasionally changing the Proton version, which is very easy to do within Steam), but generally that’s been minor. The things that don’t work well are typically things you wouldn’t expect to work anyway.

    It’s worth noting that it makes it very easy to remap controls, even for games that don’t natively support controllers or don’t let you remap the controls at all normally. You can also invoke an onscreen keyboard as needed (for e.g. typing names). The controller mapping is very strong; it’s not limited only to single buttons; you can create custom contextual radial menus, for instance, so even games that need many more unique controls than the Deck has buttons work fine with some tweaking. You can also view / download / rate other users’ control mappings for any game that has them, so you don’t even need to do the work yourself.

    It’s a fantastic piece of hardware for gaming. Looks great, feels great. It’s a bit large (won’t fit in a pocket, obviously), but that shouldn’t be a problem for anyone who would reasonably want a handheld gaming PC. It’s not a phone or a Gameboy.

    I was without a desktop PC for a week or so due to a hardware failure, and was able to do everything I needed to do on the Steam Deck (with a USB mouse/keyboard, plugged into a monitor via a dock). So it’s a great piece of hardware even for that.











  • That being said, creating a private instance is a relatively difficult hurdle. By providing private communities, an admin can take care of the hosting, along with all of the other communities, while those who want something more controlled and closed can have an easily accessible option.

    That’s fair, and I’m honestly probably just thinking about worst-case scenarios that won’t actually happen. There’s plenty of ways malicious actors could already be doing some pretty bad things and they don’t seem to be, so it’s probably fine.