If you want to expose it publically for others to use consider using Cloudflare for easy setup and avoiding exposing your home IP. If you want to use it for yourself you can access it with Tailscale and forward traffic to certain ports based on the subdomain using Nginx Proxy Manager.
The metadata showed it was edited in Adobe Premiere and was a combination of several other videos. As AstralPath said, Coffeezilla (a YouTuber primarily known for exposing and investigating crypto scams) has a video about it on his second channel.
Yes, but I still don't know why they seem to think it's so important to write a new browser engine instead of improving Gecko or Servo. To me it just seems like people like it because they don't know other things aside from the Chrome, Safari, and Firefox browser engines exist and just chase something new and shiny.
And obviously their option is the "best". From the conclusion:
Talos Linux is unique. It’s the only option that includes OS management in a purpose-built distribution for running Kubernetes. There’s no compromise for scaling up or down. In terms of small-scale numbers, it “wins” in several of the examined categories, including memory usage, disk r/w, and installation size. But all of these metrics are side effects of Talos Linux’s defining characteristic: It’s simple.
At some point they l announce that paying for a Reddit premium account allows you to be unbanned and free to do whatever you want.
What other reasons or ideas can you think of, that mass banning users, (some with years of age and contributions, some of them mods.) could be the first step in a plan to capitalize.
To me it seems like it's a consequence of both cost cutting moderators and lowering the threshold for bans to make the plaform more appealing to large companies advertising.
...definitely takes some getting used to when you come from a non-memory safe language...
I actually think it's more like the opposite. The compiler takes the normal rules you apply to avoid issues with a non-memory safe language like C/C++ and enforces them explicitly where memory safe languages don't have those rules at all. I think lifetimes are much more confusing if you've never dealt with a user after free and usually let GC deal with it.
Also yes the compiler warnings and errors are amazing, the difference between rustc and gcc is night and day.
If you want to expose it publically for others to use consider using Cloudflare for easy setup and avoiding exposing your home IP. If you want to use it for yourself you can access it with Tailscale and forward traffic to certain ports based on the subdomain using Nginx Proxy Manager.