The "long and tedious meeting" mentioned below involved the Lead Dev Team; four people in vastly different timezones, discussing (over VoIP, over various days) the future of The Hydraulisc Network.
"stopping the process keeping it alive" makes no sense; likely refers to killing the pm2 daemon? Also, "the indefinite end of Hydraulisc" is misleading. It's more of a "rebirth".
Images added here were added on the date this notice was written, replacing previous "insert image here" comments.
Welcome to another Developers Digest.
This time featuring: the indefinite end of Hydraulisc.
Hydraulisc has come a long way from it's origin
Image Source: @sooox#0001.
From a measely crash-prone single-threaded pile of hot trash, to a... less crash-prone multi-threaded pile of hot trash...
For those just joining, Hydraulisc is a Free and Open, Social Image Sharing Network Like no other :)
Hydraulisc has fallen into disrepair, after many, many dependencies which Hydraulisc's dependencies depend on, have fallen in a similar time period to multiple different vulnerabilities, and the only way to fix the majority of these vulnerabilities is to upgrade the dependencies Hydraulisc uses, but this comes at the cost of the most necessary of these dependencies having changed to ESM-only packages.
If you're still wondering, Hydraulisc is made entirely in CJS.
After a long and tedious meeting, we've decided to remake Hydraulisc instead of refactoring the old code, as this will be both more time efficient and, in the long run, just generally better and easier to maintain.
Additionally, we've decided to follow through on our promise of clear and transparent code, meaning that future builds of Hydraulisc will be completely Free and Open Source (FOSS).
Additionally, this does mean there will be some major changes, such as the return of the PAT and PBT testing phases. We may also remove the hydraulisc.xyz domain, reduce the amount of resources Hydraulisc.net may have access to, and even pause the service keeping it alive.