Thanks for the info!
Thanks for the info!
Is there some drama I’m not aware of here?
Also there are 40-something packages depending on it, so I guess it gets pulled automatically when they are used.
You’ll find an npm package to help you count up to 2.
(I recently learned - maybe here - that the is-even package has over 170k weekly downloads)
Being able to choose between single player, coop, and multiplayer.
OVH because cheap enough for me, europe based and reliable.
It’s not about competing, it’s about providing an alternative. GNU/Linux isn’t really competing with windows as a desktop OS for the masses, but people who want more freedom and privacy get the alternative. Fairphone isn’t competing with Samsung or Apple either.
I feel like if we follow your line of thought, then we should never try to do things better because the existing is too big.
I already have another account I only use on beehaw, so I wouldn’t mind a compkete defederation or software change. Safer/nicer spaces are really hard to maintain without moderation control, and lemmy clearly isn’t there yet and might not be there for some time. If staying federated/on lemmy means beehaw administration/moderation ends up burnt out, I feel like it’s the right move to move.
As a personnal aside, the only thing that would prevent me from staying on beehaw is if you chose a closed-source platform (eg discord).
Anyway, thanks for the things you do and the way you do them !
Nah, it’s a matter of personnal preferences and use case.
I love CLI mainly because it allows me to sceipt suff, but lots of people don’t mind actually seeing what they are doing and clicking on stuff to achieve it.
It’s a good news there are piracy tools with a CLI, makes it more accessible to more people - and we should rejoice about it.
I might be wrong, but for me OP is not trying to actually run email, rather have a staging ground that pulls all emails from their accounts on actual providers, apply some treatment to said emails and pull them from client-side apps on their devices.
I haven’t tried any of the following, just my 0.02.
The official documentation page about registration states:
When deploying a self managed Rocket.chat >=6.x workspace you are automatically required to register your workspace upon completing the Setup Wizard
According to the same page, for versions below 6.x you have to manually register your instance.
Official documentation page about Air-gapped installs registration
Hope any of this helps. I’m quire surprised (and not in a good way) to see this mandatory requirement from Rocket.chat. Even if kt means functionality loss (access to their push notif framework for example) you should be able to decline it.
Sounds like a good idea from a reddit - the company -POV.
It’s definitely happening. Hurting the vulnerable harder than usual seems to be one of the many perks of hosting olympics games along extra pollution, extra corruption… /s