Kobolds with a keyboard.

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

help-circle

  • 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.


  • Eh, we already have private communities.

    I did mention further down the comment chain the one use case for this I can think of - communities for info and feedback about the specific instance to / from its members; things like donations, financial disclosures, etc. - that you wouldn’t want participation in from anyone not actually using the instance. It has its place; I’m more afraid of seeing popular communities going instance-only for whatever reason, with it being used solely to drive signups on a specific instance.


  • I mean it’s fine on paper. But like… imagine that a popular instance - lemmy.world, let’s say - has a community that’s very popular and, for whatever motivation, decides they want to push people to move to their instance (or at least create accounts there), so they change one or more of those popular communities to be local-only.

    Best case, they fracture the community. Worse case, a very large number of users start making accounts there to use those communities, and abandon other instances. Worst case, they use the large influx of signups they get from such a move to promote themselves, grow even further, and eventually do something malicious.

    We can already create private instances that don’t federate for those niche communities; I don’t really see what this feature is adding other than specifically having communities dedicated to that specific instance (With instance-specific information like donations, financials, outage notices, that sort of thing.)









  • KoboldCoterie@pawb.socialtomemes@lemmy.worldYeap, it is
    link
    fedilink
    English
    arrow-up
    3
    ·
    2 months ago

    Oh, no! I only have 7 hours until I have to get up! I’ll be too tired tomorrow and have an awful day! I really hope I don’t have trouble falling asleep because I’m stressed about that, then wake up every hour in a cold sweat because I’m dreaming I missed the appointment!








  • KoboldCoterie@pawb.socialtoMemes@lemmy.mlBrute force protection
    link
    fedilink
    English
    arrow-up
    6
    arrow-down
    1
    ·
    edit-2
    4 months ago

    My current favorite “memorizable” method (obviously a random hash from a PW manager is still better) is to take a sentence of moderate complexity that includes the name of the service you’re signing up for in it, and use the first letter of each word as your password.

    For example, “When I wake up in the morning, the first thing I do is go to pawb.social.”

    Password would be “WIwuitm,tftIdigtps.”

    Easy to remember, immune to dictionary attacks, and you get a (mostly) unique password for each service, so stolen passwords can only access that one thing.

    Edit: To be clear, the value is that you can use the same sentence everywhere, switching out the name of the service to generate semi-unique passwords for each service. Obviously someone analyzing your passwords would be able to figure out the pattern, but that’s basically never what actually happens; it’s more likely someone gets 1 password and tries your email address + that PW in a variety of services, which this is strong against.