Asklemmy

43817 readers

1022 users here now

A loosely moderated place to ask open-ended questions

Search asklemmy 🔍

If your post meets the following criteria, it's welcome here!

Open-ended question
Not offensive: at this point, we do not have the bandwidth to moderate overtly political discussions. Assume best intent and be excellent to each other.
Not regarding using or support for Lemmy: context, see the list of support communities and tools for finding communities below
Not ad nauseam inducing: please make sure it is a question that would be new to most members
An actual topic of discussion

Looking for support?

Looking for a community?

Lemmyverse: community search
sub.rehab: maps old subreddits to fediverse options, marks official as such
!lemmy411@lemmy.ca: a community for finding communities

~Icon~ ~by~ ~@Double_A@discuss.tchncs.de~

founded 5 years ago

MODERATORS

Is creating throwaway accounts on lemmy bad? (lemmy.dbzer0.com)

submitted 1 year ago by SnokenKeekaGuard@lemmy.dbzer0.com to c/asklemmy@lemmy.ml

38 comments fedilink hide all child comments

I was wondering whether that could cause issues for the limited servers available, like when the mass migration from reddit happened. Would it be bad to add more accounts that would be mostly dormant? And if one does create a throwaway would it be better to delete the account afterwards.

you are viewing a single comment's thread
view the rest of the comments

[–] ursakhiin@beehaw.org 8 points 1 year ago* (last edited 1 year ago) (1 children)

Depending on implementation, the lookup should be indexed so the time difference would be very minimal on even large tables.

The cutest of storage could be a problem depending on how many wasted accounts exist, but even that should require a ton of accounts to make an impact.

[–] fiat_lux@kbin.social 2 points 1 year ago* (last edited 1 year ago)

Yeah, there's always room for a lot of implementation-dependent possibilities of good DB practices, but it's also possible for one mistaken PR approval to create exponential load.

In the case of FOSS where there might be fewer formal processes to catch errors, I like to err more heavily on the side of caution. If for no other reason than preventing surprise server scaling bills for the volunteer admins.

Also: if you are making throwaways, please consider donating time and/or cash to those instances.