I serve nothing worth encrypting and never will.
For auth. I use: https://datatracker.ietf.org/doc/html/rfc2289
Quantum safe for eternity.
750 karma · joined September 11, 2015
I serve nothing worth encrypting and never will.
For auth. I use: https://datatracker.ietf.org/doc/html/rfc2289
Quantum safe for eternity.
Big companies and governmental branches have their own root certificates.
To remove HTTP is the biggest mistake humans have made with the internet so far.
But it will trigger a reaction that deprecates both companies and governments:
Edit: Loving the down vote without comment and now the whole submission is flagged.
Google really does not want HTTP around. They seem threatened by it?
SMTP (TCP 25) and HTTP (TCP 80) are the pillars of the internet.
Tried running tiptop on Raspberry 4, it fails with no workaround on the internet.
shrugs and goes back to write poor software.
Last week I tried to get RDMA bypassing the kernel.
Also did not work.
Nothing works. Like NOTHING!
Reply works fine and comments too even if only local.
You have four properties of feeds: category, tree-comment, real-time and persistent.
Reddit was the winner on all those except real-time.
Decentralization is now the most important feature, and taking responsibility of your own data is the best version of that.
The only missing part is decentralized RSS servers and clients. Think backup for your posts and RSS reader services that also backup your favorite feeds.
All you need for that is a distributed db underlying it all like this: http://root.rupy.se and a reader web tool.
The only feature we lack is a category (think hashtag) for RSS.
So a combination of all services below:
Add mail and video hosting/streaming and you got the complete deal.
If you have a closed source game and copyright expires then how does that affect the sources?
Do closed source games not require the sources to be released after copyright expires?
JSON I use in my distributed DB (http://root.rupy.se), it's less verbose but XML to me is also a development tool that gains with human readability.
The bottleneck is almost never bandwidth on small solutions.
What I'm considering now is making my own ActivityPub, adding Reddit like features and Email.
I would like to make the format pipe (|) separated instead of XML/JSON...
The social protocol to end all social protocols. XD
http://sprout.rupy.se/feed?rss
http://sprout.rupy.se/feed?atom
Now that I look at them they are equally bad.
That said ActivityPub with JSON does not strike me as better.
Seriously considering getting into the fray...
Eventually every device on the planet will run it but companies that twart it should not be encouraged.
No comment.
http://move.rupy.se/file/logic.html
Still works great, I currently use it to chop up sprite sheets and bundle them with my app as base64 encoded pngs! XD
XML must be the future.
Also use this parser: http://edit.rupy.se/?host=move.rupy.se&path=/file/Parser.jav...
Indentation from hell and some code missing but you get the point. No bloat... and XML! :P
And please don't down vote without comment.
I agree and already imagined an animation that would make it clear why async. on both ends of transition servers connections is useful.
The sorry excuses of visualizations I have now are truly WTF.
Also all links being out-of-order does not help.
I just need to pick tools. Leaning towards animated .gif now.
Edit: I fixed the example link atleast. It fetches data from the distributed db.
But I might work some more on it if anyone is interested.
Otherwise you are completely blind as to how the systems really work.
1 hour in the right direction is worth an infinity of time in the opposite direction.
So letting your brain rest and melt the direction you should pick is leverage to infinity.
That said, with due respect to his skills; Carmack is also an example of going in the wrong direction; from tick based network, spraycones and headshots, violent games, to energy wasting AI and rockets.
His legacy will not age well unfortunately.
Bring on the downvotes!
What does their definition of event-driven really look like in practice.
Nobody has a clue.
Here is the ideal event driven system, it's async-to-async: https://github.com/tinspin/rupy/wiki/Fuse
The example is not working because I had to shut down the services for multiple reasons, but the high level of it is that you use 4 (potentially different) threads to do one request/response middle man transaction.
That way you have _zero_ io-wait or thread idling. I'm surprised nobody has copied this approach since I invented it 10 years ago. I understand why though you need your entire chain to be async and that means rewriting everything and that is a big risk when it's hard to debug.
But if you succeed you can build something that is 10x perf/watt than all other implementations. Which is going to be important when interest rates go higher and crash our entire industry.
- Arrays of 64 byte Structures with C. (client)
- Java. (server)
Everything else is not atomic.
Long term; lies cannot master truth, colonization is over / will reverse.
In practical terms margins are permanently gone, so no more invention / exploration is made.
Either way we are peaking in complexity. Simplify your life or get wrecked.
No need for HTTPS.
So software is where you can make the difference: http://host.rupy.se