rupy VS Shynet

I have been running a Raspberry 2 cluster for 10 years: http://host.rupy.se

A few weeks back the first SD card to fail got so corrupted it failed to reboot!

My key learning is use oversized cards, because then the bitcycle will wear slower!

I'm going from 32GB to 256/512/1024!

I think we're all confused over the definition. Also one might understand what all the proponents are talking about better if they think about this more as a process and not some technological solution:

https://github.com/tinspin/rupy/wiki/Process

All input I have is you want your code to run on many machines, in fact you want it to run the same on all machines you need to deliver and preferably more. Vertically and horizontally at the same time, so your services only call localhost but in many separate places.

This in turn mandates a distributed database. And later you discover it has to be capable of async-to-async = no blocking ever anywhere in the whole solution.

The way I do this is I hot-deploy my applications async. to all servers in the cluster, this is what a cluster node looks like in practice (the name next to Host: is the node): http://host.rupy.se if you click "api & metrics" you'll see the services.

With this not only do you get scalability, but also redundancy and development is maintained at live coding levels.

I have hosted my own web server both physically and codevise since 2014.

It's on a Raspberry 2 cluster:

http://host.rupy.se

Since 2016 i have my own database also coded from scratch:

http://root.rupy.se

We need to implement HTTP/1.1 with less bloat, a C non-blocking web server that can share memory between threads is probably the most interesting project for humans right now, is anyone working on that?

I have one in Java: https://github.com/tinspin/rupy

Here is the 2000 lines of code of the entire database: http://root.rupy.se/code?path=/Root.java

And here you can try it out: http://root.rupy.se

The smallest PaaS you have ever seen is one order of magnitude larger than mine: https://github.com/tinspin/rupy

And I bet you the same goes for performance, if not two!

Absolutely not, HTTP/1.1 is the way to make SSE fly:

https://github.com/tinspin/rupy/wiki/Comet-Stream

Old page search for "event-stream"... Comet-stream is a collection of techniques of which SSE is one. My findings are that SSE go through anti-viruses better!

I would look at my own app-server: https://github.com/tinspin/rupy

It's not the most well documented but it's the smallest implementation while still being one of the most performant so you can learn more than just SSE.

The data is here: http://fuse.rupy.se/about.html

Under Performance. Per watt the fuse/rupy platform completely crushes all competition because of 2 reasons:

- Event driven protocol design, averages at about 4 messages/player/second (means you cannot do spraying or headshots f.ex. which is another feature in my game design opinion).

- Java's memory model with atomic concurrency which needs a VM and GC (C++ copied that memory model in C++11, but it failed completely because they lack both VM and GC, but that model is still to this day the one C++ uses), you can read more about this here: https://github.com/tinspin/rupy/wiki

You can argue those points are bad arguments, but if you look at performance per watt with some consideration for developer friendlyness, I'm pretty sure in 100 years we will still be coding minimalist JavaSE on the server and vanilla C (compiled with C++ compiler) on the client.

+1 on shynet! I use it for my personal website and my blog, and it's been working great.

I got it up and running with Podman, so no need to install and run the Docker daemon. I also fixed SQLite support [1], so no need for an additional DB server.

I analyzed available open-source web analytics tools [2] and AFAIK there is simpler solution for web analytics that doesn't involve a third party.

[1] https://github.com/milesmcc/shynet/issues/208

[2] https://blog.fidelramos.net/software/privacy-respecting-self...

I like shynet

I am using shynet for a while now. Really all I need to know :)

https://github.com/milesmcc/shynet

There's also Shynet.

Oh that is actually shynet self hosted analytics which is privacy friendly. https://github.com/milesmcc/shynet

But I think I'll just remove it for now.

Shynet: https://github.com/milesmcc/shynet

The goal is to provide, privacy-friendly, and detailed web analytics that works without cookies or JS. And it's completely open source.

Full disclosure: I am the primary maintainer.

I have a strong technical background and a passion for digital safety and privacy. Especially interested in trust & safety, privacy engineering, human-centered design, tech policy, and open source software. Looking for an internship or fellowship adjacent to trust & safety or privacy engineering.

Some of the projects I’m most proud of are Shynet [0], PrivacySpy [1], PolitiTweet [2], and a17t [3]. I co-instruct CS 106S [4] at Stanford, and I worked on cyber policy for a 2020 presidential campaign. I also work at the Stanford Internet Observatory on both research and technical infrastructure.

Location: NYC or SF Bay Area

Remote: yes but ideally no

Willing to relocate: no

Technologies: Python, Rust, JS, Java, Kubernetes, C, OSINT, web dev, and more.

Résumé/CV: https://docs.google.com/document/d/1wnIBWjEPmgdYXQ_EYZRU--KE...

Email: [email protected]

[0] https://github.com/milesmcc/shynet

[1] https://privacyspy.org

[2] https://polititweet.org

[3] https://a17t.miles.land

[4] http://cs106s.stanford.edu