@carpathianflorist's banner p

carpathianflorist

162 IQ social equity activist (she/them)

1 follower   follows 0 users  
joined 2022 September 04 23:16:40 UTC

STEM major | 21 | nonbinary femme (she/them) | panromantic asexual | independent filmmaker from brooklyn | unapologetically neurodivergent


				

User ID: 264

carpathianflorist

162 IQ social equity activist (she/them)

1 follower   follows 0 users   joined 2022 September 04 23:16:40 UTC

					

STEM major | 21 | nonbinary femme (she/them) | panromantic asexual | independent filmmaker from brooklyn | unapologetically neurodivergent


					

User ID: 264

So it’s exactly like Reddit’s system where if you haven’t been sufficiently upvoted by the entrenched users, you’re invisible without moderator approval, just with a sneaky name and without the automod message letting you know that no one can see your stuff 🤔

It’s one of the thousands of fun rDrama features! I think they just forgot to remove it with the rest of them, though. Stay strong Mottizens.

That’s interesting if true. What is RAND? And do you have a link to the paper?

NEVERMIND, found it.

Incredible.

When rDrama was new (and then not so new), we still had constant outages and hilarious glitches all the time. Like Aevann got 0 sleep for the first six months or so. Every time he’d add a feature, a million other things would break. Then as soon as he’d fix one of them, two million more would break. There was one night where we couldn’t comment or view any threads because something innocuous broke when patching something else and we all just communicated via thread titles and publicly visible reports for hours.

Now everything runs incredibly smoothly and Aevann has learned a ton just through endless trial by fire (and sleep deprivation) for those months. We add huge new things all the time and are constantly optimizing early jank with new knowledge and nothing ever really breaks for more than a couple minutes at worst anymore.

I realize this is a No Fun Allowed by design place, but it’s important - for your own sanity as the dev, and for the userbase’s tolerance of early growing pains and learning moments - to take it all in stride and have fun with it. We fostered a culture immediately of “shit’s going to break, we’re learning, deal with it” and people have always taken it in stride and memed about it endlessly because we built that culture up. No one gets mad. No one has to make tedious mea culpas because we broke something. We reward people for breaking things and encourage it because then we can fix an issue we weren’t aware of. This is a good system and lets people have fun and not freak out when things break.

I’d strongly recommend not setting an expectation for lengthy technical explanations of what happened and why when something goes wrong. A sentence or two at most. “Sorry to I was drunk and fell asleep at 4am trying to fix something else and I was too tired to fix it, that’s why you could only communicate via dick pics for 6 hours” is perfectly serviceable.

That’s one of the many nice parts about not being a massive global megacorp like Reddit. You’re just a few dudes doing something for fun. You don’t owe stakeholders receipts for something that broke. There are no stakeholders. The userbase will understand. But if you go about explaining everything that went wrong every time something goes wrong, you’ll breed mounting discontent and you’ll never have time for anything else.

Lighten up nerds.