Is there some drama I’m not aware of here?
Is there some drama I’m not aware of here?
Thanks for sharing, this looks awesome ! I can’t waut for the opensource release.
Btw, did I skip through the article too fast or is tomhardware unable to provide links in its content ? /rant
Anyway, here are the ones that seemed relevant to me.
Official website (kinda empty at the moment, but it’s going in my bookmarks)
Hackernews original discussion in which the author states:
Let’s be clear here, this is a toy. Beyond being a fun project to work on that could maybe get my foot in the door were I ever to decide to change careers and move into hardware design, this is not going to change the GPU landscape or compete with any of the commercial players. What it might do is pave the way for others to do interesting things in this space. A board with all of the video hardware that you can plug into a computer with all the infrastructure available to play around with accelerating graphics could be a fun, if extremely niche, product. That would also require a significant time and money investment from me, and that’s not something I necessarily want to deal with. When this is eventually open-sourced, those who really are interested could make their own boards.
Always heartwarming when people on the internet refer to women as a commodity that only exists for the pleasure of men, putting it on the same level as a bottle of rotten grape and some wrapped dried leafs.
OVH because cheap enough for me, europe based and reliable.
TIL Suicide Linux was a thing, thanks !
Linux Mint Debian Edition looks like a common ground for you two ;)
I agree with your point on the necessity of FSF and pure free software. Your comment seems to describe pretty well the Overton Window
I was very confused. Thank you :)
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.
Thanks for the info!