okwhateverdude

What's wild is that the nethack source is so easy to read and understand, that it is trivial to add new content. I'd like to see some of the mechanics from the newer gen roguelikes like Shattered Pixel Dungeon make it back into trad nethack

Depends on the people. Eternal September has been a meme for over 30 years at this point. It is a cyclical pattern in just about anything social: experimentalists/creatives create new thing, early adopters join which gives new thing legitimacy, social contracts are implicitly drafted because the community is small and easy to reach consensus, then it gets exposure, masses of new people join the thing that aren't interested in the social contract, community cohesion eventually evaporates. This is how you go from "Man, our thing is so cool" to "Fucking newbies spamming in general, begging." You don't want to share your cool thing with a bunch of mouth breathers that aren't capable of appreciating what makes the thing actually cool. Eventually the grifters come, and then it is game over. So the original community members scatter to the winds. Some creative people make some new thing and it starts all over again.

I can't get the accent that goes with this phrase out of my head. This response is so perfect 🤣

Not GP, but reading gnarly code and making definitive statements about who/what/when/where/why such that your documentation is accurate, especially in a corpo context where there are not clear boundaries of responsibility, requires quite a bit of brain power. Not to mention the ever increasing entropy in systems driven by profit means that whatever you write in terms of documentation will have a pretty short shelf-life. The code might stick around as an unholy amalgamation of copypasta after a refactor or two.

One time worked in an office building with a pretty shitty floor on the second floor. Wouldn't have surprised me if it wasn't really all that structurally sound, because I could bounce my leg, just like I am doing right now, and the dude sitting next desk over could feel it in the floor. I ended up moving to another desk to avoid the conflict with the coworker... and in case the building was shitty enough that it was a weak spot in the floor.

Brave? Dude probably can taste it while feeling like a corndog

It is somewhat difficult to source N2 that hasn't been adulterated as a consumer now. They do the same thing with He2. I'm with shotgun sammich dude. My retirement plan definitely involves my mouth watering for bullets.

Since 2013, about the time the american's solidified their control over the company, from what I remember working there then. Gee, what a coincidence.

Okay cool, just making sure you covered all your bases 🖖

I'd carefully consider using email for this. If you're hosting the service, you might need to use one of the bigger email providers that already have reputation (unless you already have good IPs with good rep). Otherwise, you risk the emails sitting in spam and people's switches being flipped. If it is self-hosted, you'll probably need to explain the risks to users.

Given today's world of pocket computers, you might consider using push notifications of some kind. Or have a companion client that pokes an API and there is some kind of challenge/response.

Are your users technical? If not, crontab syntax is definitely to be avoided. Instead, I'd offer some simple options like daily, weekly, monthly, etc. Then convert that syntax into crontab syntax.

I glanced at the repo, but there is no content in the README.md to get a sense of what your project is actually doing.

For processing cron, you should consider just using cron. You can setup a user specific to the process, use that user's crontab, and manage the entries. If the source of truth will be from the database, then you don't even need to read the crontab itself, only (over)write it on demand.

Okay cool. Thanks for sharing your game