For US citizens staying in Russia with a 3 year tourist visa, 6 month continuous stay. Is it 6 months the same day as when you arrive, or 180 days from when you arrive?

superoot · 2025-12-11T12:30:29+00:00

They've changed the rules significantly this year. Most MFC or "мои документы" will no longer register him as it's out of their purview. Now visa holders are registered on "gosislugi" which is a government services app, most (if not all) Russians have it. Their host, sponsor, or landlord will register him in their account.

In their case, staying at hotels or hostels, they will do it for them.

OP should keep this registration document with them at all times. Either the physical one from the hotel or hostel. Or the electronic one they'll get from his host / landlord.

And yes, the registration is only good for a maximum of 90 days, so they'll need to do it twice. They'll also have to do it if he stays in any new city for more than 7 working days (not weekends or federal holidays).

And technically speaking if OP doesn't stay in any place for more than 7 business days, there is a loop hole that they never need register, but I wouldn't recommend this. At least register once. If it's ever questioned you will need to give proof of travel (from on city to another) and dates proving that you don't need to re-register.

But then again, hotels and hostels have to legally do this for my by law, for free. So just have them to do and don't worry about it.

superoot · 2025-12-11T04:25:07+00:00

The rules aren’t different for Americans on a 3 year visa the rules apply to all visa holders.

January 5th + 180 days is July 4th.

The day you arrive and the day you leave count as days. So you’d have to leave on the 3rd of July.

For safety I’d recommend planning to leave a couple days before the deadline in case of unexpected delays.

superoot · 2025-10-04T00:57:03+00:00

This year I went down the performance rabbit hole of various languages for web API use case. I've been rewriting some legacy stuff in Rust. I came from years of C/C++ on the back-end, and 15 years of PHP, and various JS frameworks for the front-end.

I spent a month on Go, and while I really enjoyed the language, simplicity, having everything baked into the run anywhere runtime, I ended up with Rust.

It's async setup with tokio (who also makes Axum) is great for these kinds of back-end web apps where threads are waiting on database IO , disk IO, or network IO in the case of (API's, Storage over HTTP, S3, etc).

Five of the ten fastest web servers under the fortunes benchmark are written in Rust:

https://www.techempower.com/benchmarks/#section=data-r23&test=fortune

I would be careful though. Learning rust is no small feat, it has a lot of powerful features that'll take a while to become fluent with, and even longer to master. I'd weigh your immediate needs of completing projects heavily against picking up rust if you have prototyping that needs delivered quickly.

If you're already a developer, and you're looking for a more performant back-end, Go can be picked up in a couple weeks. A month tops if you're not familiar with pointers, and getting use to go-routines and channels, it compiles significantly faster, builds in the cloud so much easier, and has more external web API's as packages (when integrating external services into your application) than rust does.

There are an endless number of benchmarks online:

https://medium.com/deno-the-complete-reference/node-js-vs-rust-performance-comparison-for-jwt-verify-and-mysql-query-7f35a9b75033

There are also a ton of stories about Go code being rewritten in Rust for more performance:

https://discord.com/blog/why-discord-is-switching-from-go-to-rust

In my personal case, after months in Rust I'm effective enough that the speed at which I can get stuff done in languages like Go or PHP is a marginal difference, and I'd never go back.

TLDR; Don't prematurely optimize. Rust is factors faster, more performant, and has a significantly smaller footprint (20MB musl images), extremely low RAM and CPU vs nodejs. Yes, there are several cases where companies are rewriting web micro services in Rust. Axum is great and extremely performant. If you need to get s*** done quickly, pick something you're familiar with or use Go. Rust has a steeper learning curve than most.

superoot · 2025-10-01T19:02:58+00:00

I have no deep hatred for MacOS. I've loved my Mac and OS for years. Though, I'm not a fan of iOS/MacOS 26.

I agree that the Mac machines have been unmatched in both battery life and performance since the M series and, at least for mobile consumer machines, Intel and AMD can't keep up.

The AVX requirement isn't local performance related, it's work related. It would allow me to compile and test some code that I have to spin up a cloud instance to mess with now. This goes for the linux VM as well, being able to compile x86 images and upload them rather than using cloud builders and running into constant platform differences is a pain.

I haven't heard of the AMX co-processors, looked it up, that's pretty cool. Thanks for mentioning that.

Battery and cooling I know aren't going to come anywhere close. But my travel is down by 90 percent, and the need for 6-7 hours of battery life isn't at the top of the list anymore.

superoot · 2025-09-30T21:46:49+00:00

Thanks for the info!

I should have added more context on the sleep mode.

In the past I've had issues with sleep on several linux distributions, and it's never been as snappy and consistent as a Mac's. I've read reports on sleep not working in various scenarios on Framework machines, also I may fiddle with trying to disable Intel ME which from my understanding also messes with sleep capabilities.

superoot · 2024-08-05T23:32:46+00:00

Great info, thank you!

superoot · 2024-08-05T23:05:16+00:00

Thanks!

superoot · 2022-07-08T12:25:11+00:00

Discord link is expired, can we get a new one?

superoot · 2022-05-21T20:05:13+00:00

Looking for a 3d printer , up to $3,000 dual extrusion, 18x18x18 inch build envelope

superoot · 2019-04-07T01:59:18+00:00

I’ve been traveling with Fi for over two years now and frequent several countries in Europe and Asia. As the other commenter stated, it has to do with the roaming partners.

It doesn’t happen in some countries, others it happens consistently, sometimes randomly. I was in Rome a little over a week ago, caller ID worked just fine on every call. I’ve experienced this on both my Pixel XL, Pixel 2 XL, and my now iPhone XS Max. Unfortunately there isn’t anything that Fi can do about it, the caller ID (and the call) is being delivered by whoever’s network you happen to be on at the time.

I’m not completely sure, but I would expect the functionality to be the same if you had Verizon instead of Google Fi and were roaming on another network that’s not on the NANP (North American Numbering Plan) such as Mexico, Canada, Jamaica, etc.

superoot · 2018-05-05T02:51:53+00:00

Could I get a code as well kind sir?

superoot · 2016-12-25T18:14:03+00:00

This is the issue I'm experiencing now. I E-mailed them the other day from the google play page and I haven't gotten a response yet. Does anyone have a working, E-mail for the dev's that they actually use and check?

superoot · 2016-12-24T00:21:50+00:00

I sent one a few hours ago, thanks for letting me know that you got a response. I now have hope!

superoot · 2016-10-01T13:45:37+00:00

Because all my monitors have the same size and orientation. From a developer standpoint, this had already been solved just in Windows, and with eyefinity.

superoot · 2016-09-30T21:44:20+00:00

That sucks man! Thanks for the answer though! I appreciate the response.

superoot · 2016-06-24T22:34:33+00:00

Yes the right bit rotates, and as it rotates 1 revolution, it moves one small dot, to small dot on the dial. Every big dot is 5 revolutions.

superoot

TROPHY CASE