I'm back to work updating OnePo's codebase to modern standards on the server side. Specifically async/await as opposed to callbacks. it's BOOOOO-RINNNNG. But I have "only" one file left. Of course, it's the one where most of the code is.

So after that I should refactor that file as well. Also BOOOOO-RINNNG, and yet somehow satisfying. Then maybe crank up eslint to call me on my shit. Poor man's typescript. Then maybe typescript?

Then rethink the frontend code. Using [ugh I will not even think about choosing a framework today].

Of course OnePo is still a tiny, tiny place. As in "I've never bothered to index the database collections for performance" tiny.  I may need to dial up the disk space just a tad soon though.

"But Tom, aren't you gearing up to welcome former Twitter residents?" No, not really, although the six people who will actually leave in this, the most recent of many outrages are warmly welcome.

Moderation of a successful public social media site is a huge, unsolved problem. As others continously have pointed out, the real challenge for something like Twitter is moderation, not engineering. Yes, it's bad that Musk's plan is basically to fire the moderators.

But I'm in no position to improve on that. There's no moderation in practice on OnePo at the moment, although I'm pledged to supply some in the event of certain types of abuse.

What we have instead is an invitation-only model and a predilection toward thoughtfully locked posts, which reduces (though it absolutely does not eliminate) the likelihood that someone you're connected to needs moderating... at least from your perspective. So far this seems to work OK for our needs.

But, a system like that cannot function as a public square. If we indulge my ego in imagining OnePo writ large, we wind up with a worse echo chamber than Twitter, because it's so difficult to discover new people and the general habit is to limit audiences for things.

Also, OnePo is just a whole 'nother idiom. The intersection of OnePo and Twitter is a ridiculous idea. That would be... uh... BeReal, actually. BeReal is pretty fun. But it does one tiny job.

Actually I kinda like the idea of doing one tiny job. OnePo's one tiny job is allowing friends to know and support each other better. That's fine for what it is, which is a lot.

MORE
10/29 '22 9 Comments
"modern standards on the server side" sounds like lyrics to a Joe Jackson song.
And with our modern standards on the server side
Get into a car and drive

Checks out.
Haha, I can hear it in his voice.
a feature that I think may bring more people would be something tumble like where you can search posts by date or "random post."

There are a lot of times I've needed to check something that happened, say, more than six months ago, and I've thought, Oh, I should check OnePo and- Nope. But I also understand that I can search by tags and I owe it to myself to tag more of my own posts.
Search would be nice I agree. I don’t know if it would lead to growth because you have to be able to see stuff in the first place… which means public posts.

Also the existing users have invited everyone they want to invite, and there’s no other on ramp right now.

Hmm.

Maybe a communities feature, he said, continuing to reinvent livejournal.

Maybe a signup that more clearly paves the road to bring your community with you.
typescript just copies all I/O to a file, right? :)
Knew you were listening.
Any recommendations for good tutorials on properly implementing async/await? Asking for a bearded friend trying to get up to speed on contemporary JavaScript.
Did you want to push this site? I have considered posting content here and posting a link to it on facebook.