n4bz0r
Given it's a "VPN", would it work alongside real VPN?
I've read reviews from people who put 32GB sticks in these boxes no problem. Not sure why they put "16GB max" in the specs, that's just misleading. But the CPU you ordered is way more powerful so no grief there.
The cheaper and most popular one is N150 [2] which is a replacement for N100 [3]. The newer one boosts a bit higher. The 6-7W TDP in specs is a lie, but these CPUs still have fairly modest consumption working at about 10-20W on average.
There are some low power chips from AMD, but that's mostly NAS territory. Don't see them a whole lot and don't know much about them either.
[0] https://www.techpowerup.com/cpu-specs/?f=codename_=Gracemont
[1] https://www.techpowerup.com/cpu-specs/?f=codename_=Twin%20La...
[2] https://www.techpowerup.com/cpu-specs/processor-n150.c4109
[3] https://www.techpowerup.com/cpu-specs/processor-n100.c3007
I recently had a similar issue with the wardrobe. I've been bedridden for an extended period of time and lost a lot of weight in the process. As a result, I had to replace every basic piece of clothing, both indoors and outdoors - things either didn't fit or were too worn. I still didn't feel too good to go shopping around town so I had to order online. On top of that, I was short on money. With little room for error, the task felt daunting, to say the least. Couldn't get around it for a while.
Long story short, I solved the shopping problem by figuring out how to sell the old things first. That helped me with both getting the old pile of crap off my mind as well as moving forward with the new purchases without the fear of unrecoverable losses. Now purchasing clothes feels less like gambling and more like something I can be in control of. The stars don’t have to align the first time, but eventually, they will.
Started a fresh profile, but couldn't find an AI button. The AI stuff in the context menu? You can remove the chat bot functionality right there. As for the buttons, if there is an undesirable button, it should be removable via context menu or toolbar customization.
Some of the cases are so ridiculously evil, I'm beginning to think they have black marketing division that mostly consists of lawyers.
Sure, you must, I guess, but is anyone really going to jail over this piece of ancient history? I find these disclaimers cute.
You can also use secondary domains for landing pages. But that's probably out of pet projects' scope.
I can certainly see how containerizing apps and using "layered" FS solves a class of problems, but I highly doubt this alone would be incentive enough for the major OSes to go that way. I do agree it would be neat to see such developments, though.
I was thinking about trying ChatGPT Pro, but I seem to have completely missed that they bumped the price from $100 to $200. It was $100 just a while ago, right? Before GPT-5, I assume.
Such blanket statements really don't bring anything to the table.
PS: I think you might be confusing Yandex with VK. VK are known to be loyal to government and provide users' data to law enforcement at a whim, without proper procedures.
Actually, that's the question (or rather the feeling) I had even before seeing these numbers. Just by reading the docs and looking at everything they built (and how they built it) made me wonder if they spend more than they make. That's a really funny feeling I never had before. Like, surely economies can't be that forgiving when it comes to polishing things. Is that what's happening to the company? Mere overspending?
How do they handle such situations?
Mind telling more about that?
> What's most interesting is what content companies are getting the best deals. It's not the ragebait headline writers. It's not the news organizations writing yet another take on what's going on in politics. It's not the spammy content farms full of drivel. Instead, it's Reddit and other quirky corners that best remind us of the Internet of old.
Removing all the vibrant parts is long due, apparently :')
If you do small scale (we're talking self-hosted git here after all), all these are either non-issue or a one-time issue.
Figuring out backups and firewall is the latter. Once figured out, you don't worry about that at all. Figuring these out isn't rocket science either.
As for the former. For minimum maintenance, I often run services in docker containers - one service (as in compose stack) per Debian VM. This makes OS upgrades very stable and, given docker is the only "3rd-party" package, they are very unlikely to break the system. That allows to set unattended-upgrades to upgrade everything.
With this approach most of the maintenance comes from managing containers' versions. It's a good practice to use fixed containers' versions which does mean there is some labor involved when it comes to upgrading them, but you don't always have to stick to the exact version. Many containers have tags for major versions and these are fairly safe to rely on for automatic upgrades. The manual part of the upgrades when a new major release comes out can be a really rare occasion.
If your services' containers don't do such versioning (GitLab and YouTrack are the examples of that), then you aren't as lucky, but bumping a version every few months or so shouldn't be too laborsome either.
Now, if DDoS is a concern, there is probably already the staff in place to deal with that. DDoS is mostly for popular public services to worry about, not for a private Gitea instance. Such pranks are costly to randomly poke around and require some actual incentive.
But why keep a private instance out in the open anyway? Put it behind a VPN and then you don't really have to account for security and upgrades as much.
> Waste Yield Rate: Endless kilograms/second
Now we're talking!
If we're talking web-services - absolutely. I put Caddy in front of everything just to be able to simply use domains. You can also use it to map ports to either standard or more convenient ones if that suffices. Configuring reverse-proxy with Caddy [0] takes just a few lines:
http://some-service.internal {
reverse-proxy localhost:12345
}
- DNS-server: most routers can be that; another easy option would be PiHole.
- DHCP-server: same as above (PiHole does DHCP too).
- Reverse-proxie(s): you can have either just one for the entire network or a number closer to the amount of services if you choose to have HTTPS between everything. Wouldn't bother with Nginx for that unless there is a strong incentive.
- ACME-server: provides the certs for the local reverse-proxies if you choose to have HTTPS between everything. Caddy can also act as a very easy to set up ACME-server [1].
If you have all that set up, you can access all the local services securely and via readable URLs. Given all the services get their certs from the ACME-server, the consumers only need to trust (install) one root cert in order to consider all the local connections secure.
Might seem like a lot at first, but the configuration is fairly straightforward and I found it's worth the effort.
[0]: https://caddyserver.com/docs/caddyfile/directives/reverse_pr...
[1]: https://caddyserver.com/docs/caddyfile/directives/acme_serve...
Thanks, didn't even know it existed.
> I didn't see a specific RFC that reserved .lan
There is no RFC AFAIK, but it has certainly seen some adoption over the past decade. Mikrotik devices use `router.lan` as a default domain name for their routers, for instance. Home labbers on YouTube seem to like to use `.lan`, too.
Would it be fair to think there is a chance `.lan` might get an RFC of its' own given the popularity? Or that's completely irrelevant in case with RFCs? Hard to tell what's the reasoning there - `.home.arpa` seems excessivly long and inconvenient.
Would be a real shame and a bummer if `.lan` ends up becoming public :')