loco VS cli

Well, no, that's not really a fair assessment. Someone is quite literally doing "rails but for Rust" with loco: https://loco.rs

As far as I know, the bulk of this effort has been one developer pushing it along. I wouldn't personally use it but it _does_ exist.

It's also worth noting that these older frameworks all come from a different era of development - nowadays most newer devs seem to want to build microservice-after-microservice, where these don't quite fit into the picture.

Moreover, I especially like where Rust is right now in the web space. It really feels like there’s a lot of smart people working on the next generation of web development tools - it feels like the place to be. There are a range of great open-source web dev tools that are just reaching critical levels of maturity. Axum, which I used to build Prodzilla, feels ready for out of the box web dev, and is crazy-performant, as I write about later. More recently available is Loco, a Rails-like framework for building web applications in Rust that's picking up steam. And in dev-tooling and hosting there’s Shuttle, a 1-line hosting solution for Rust backends.

Interested in more? Check out the full tour of Loco here. Check out their discussions here.

Try https://loco.rs/ or maybe tell us what to add?

Note: You can check the quality of SOCKS5 or HTTPS proxy with companies like: https://ipinfo.io or whoer.net

You need an access token from ipinfo to access their API. Go to ipinfo.io and sign up for an account. After signing up, you'll get an access token. Keep it handy as we'll need it in the next step.

stories: - name: get-ip-info steps: - name: get-ip url: https://api.ipify.org/?format=json http_method: GET - name: get-location url: https://ipinfo.io/${{steps.get-ip.response.body.ip}}/geo http_method: GET expectations: - field: Body operation: Contains value: "Australia" schedule: initial_delay: 10 interval: 60 alerts: - url: https://my.site/notify

3- IPinfo

Mullvad VPN location set to Frankfurt germany

Using the us east test server:

Proxy Score: 10/100 - Very likely not a Proxy

VPN Score: 0/55 - Very likely not a VPN

Using german test server:

Proxy Score: 10/100 - Very likely not a Proxy

VPN Score: 30/55 - Very likely a VPN

The thing that changed between both tests was the flow latencies vs ping latencies check. Clicking on more info it said: "flow variance too large in relation to avg flow: 0.6937484181219945"

I guess it works kinda, but not very consistent.

But e.g. https://ipinfo.io/ reveals immediately that this IP is a VPN IP address.

If it's a work computer it may be connecting to it's own VPN automatically. If you go to a site like https://ipinfo.io/ do you recognize the external IP address, region, and org?

Then just check IP of the server when ping is high for you, put IP in https://ipinfo.io/, and block range for all other servers in same datacenter.

3. Check the IP address information by ipinfo.io, and confirm the IP location information is right with okeyproxy's we pasted into ProxyHelper.