Signal refuses to even try to accommodate for UnifiedPush or MQTT for those not using play services requiring an extra battery-draining socket to their servers. You are also still required to use one of the mobile duopoly OSs as a primary device to register (SIM still required). Good luck if you use a Linux phone, KaiOS, or just don’t want an ever-present tracking beacon on you. We all know the Electron-based desktop client is shit. I would flip this on its head & say it is the service’s probably if they choose to prioritize & mainly support the shitty mobile OS duopoly it’s their problem for providing a bad service & getting the criticism they deserve.
There are several browsers that can operate with low memory requirements, but you have to be willing to live without JavScript & the front-end needs to have been built with accessibility & progressive enhancement in mind. …Which most front-end developers don’t do & the industry doesn’t normally pay them enough to care or get better results (& following YouTube tutorials always tells you to use the latest bloated framework which is overkill for your project).
Also Fedora doesn’t ship with LTS kernels which makes me question their package management strategy.
Which is largely whether or not the eventual consistency model or not is the route to take. Is the resilience for chat worth the explosion of storage & preformance cost of sync/search & maintaining all that data amongst all servers? Or is limited/functional sync without always duplicating the entire history with the occasional out-of-order message & missing old attachments good enough? Is ephemeral chat okay to save resources which in turn makes it more feasible to self-host on lower-end hardware or is it better to trust a couple big servers with massive storage who probably have admins?
Correct me if I am wrong, but my understanding is that you use Coq to prove your theroem, then need to rewrite it in something else. I think there is some OCaml integration, but OCaml—while having create performance for a high level language & fairly predictable output—isn’t well-suited for very low-level kernel code. The difference in the ATS case (with the ML syntax similarity 🤘) is you can a) write it all in a single language & b) you can interweave proof, type, & value-level code thru the language instead of separating them; which means your functions need to make the proof-level asserts inside their bodies to satisfy the compiler if written with these requirements, or the type level asserting the linear type usage with value-level requirements to if allocating memory, must deallocate memory as well as compeletly prevent double free & use after free.
For those in the back: Rust can’t do this with its affine types only preventing using a resource multiple times (at most once), where linear types say you must use once & can only use once.
If you believe in ADTs, limiting mutation, & a type system that goes beyond Rust’s affine types + lack of refinements (including a interleaved proof system), you could be writing kernel code in ATS which compiles to C.
There’s a small learning curve I wish some bothered to understand first. Does this app help? The part of this I don’t like is vacationers leaving useless names like ‘Mango lady’, ‘many street vendors’ for a block, or ‘local restaurant’ since they can’t read the sign as opposed marking up the cuisine type, maybe adding an English description, & leaving the name blank. Nobody expects uploads to be perfect but Bangkok is littered with this noise that makes it hard to follow or find things.
While the greater knowledge tells us the jack integration costs the manufacturer less than a greenback, the narrator buys @ 20× the price a dangling dongle whose DAC quality is an unknown. Strolling with cellular apparatus in hand, the narrator’s new phone tails are inserted—one side waving in the wind & the other causing a weird, uncomfortable cinch in the junction with 3.5mm jack. Additional stress is forced upon the singlar USB-C port. Who will last longer on this phone, port, battery, screen? “This is fine” he tells himself lifting the screen searching “best Bluetooth headphone 2024” just to see what’s out there—even tho his headphones have no performance issues & a replaceable, detachable cable already built to last.
Self-hosting & other content producing has been pushed against for ages. Look at the cost to get symmetric internet speeds in many places like it is somehow more expensive to upload the bits. I am pretty sure this is a part of a conspiracy to make sure everyone is a consumer for more $$$ & not expressing their own ideas except on platforms they don’t control.
Many of these will handle the TLS for you, but that supposes you need a specific service. Then & even now you can still host your own website / services at home without any specialized gear (I do). If IPv6 were more common, it would be even easier.
Responding broadly to the thread of folks talking about userScripts & add-ons. This effort would be better put to getting folks to a different protocol where client modification & alternate clients are the norm.
Signal refuses to even try to accommodate for UnifiedPush or MQTT for those not using play services requiring an extra battery-draining socket to their servers. You are also still required to use one of the mobile duopoly OSs as a primary device to register (SIM still required). Good luck if you use a Linux phone, KaiOS, or just don’t want an ever-present tracking beacon on you. We all know the Electron-based desktop client is shit. I would flip this on its head & say it is the service’s probably if they choose to prioritize & mainly support the shitty mobile OS duopoly it’s their problem for providing a bad service & getting the criticism they deserve.