I think its better to keep your gateway basic, and run extra services on a separate raspi or similar. Let your router/gateway focus on routing packets.
Openwrt can run Adguard, and as long as your gateway can run docker, you can probably get pihole working.
Not sure what the exact law is, but there are noise restrictions after 10pm in my area. So not just domestics, lawnmowers, reving car engines, drumkits etc are all prohibited. Its at the polices discretion to how they handle it, whenever I have called it in, usually the cops tell them to be quiet, and that theyll swing by a bit later to make sure its peaceful.
I’d call the cops on the noise alone. Its their job to decide whether to, and how to intervene. Of course, the police in my country aren’t trigger happy morons, so that does change it a bit.
For openwrt+wireguard, see: https://cameroncros.github.io/wifi-condom.html
Looks like tailscale should work in openwrt: https://openwrt.org/docs/guide-user/services/vpn/tailscale/start
For the wireguard server, I am using firezone, but they have pivoted to being a tailscale clone, so I am on the legacy version, which is unsupported: https://www.firezone.dev/docs/deploy/docker
Edit: fixed link
That is likely a speed test server within the same data center as your vps, or they have special traffic shaping rules for it.
Try using iperf from your local box to the VPS and see what speeds you get
The militarys goal isn’t to make money, its to maintain their tactical edge. And they are up against relentless competition, so they must continuously innovate or lose their advantage.
It’s not so much that the army dudes are buying the tech once its developed, they often ARE developing it. And if its giving them an advantage, they will obviously want to hold that as long as possible.
As others have said, rather than learn a language, solve a problem. Find something that bothers you, and write some code to fix it. The specific language doesn’t matter.
Its kinda similar to learning a spoken language, there is no point learning French if you cant use it in someway.
Never heard that term, but its a very obscure concept, so wouldn’t surprise me if it had multiple names. Probably vender specific names?
Seems quite a few people havent heard of it, hence a lot of the split DNS answers :/
I can’t remember exactly what its called, but something like router NAT loopback is what you want. I’ll have a look around. But if you set it right, things should work properly. It might be a router setting.
Found it: https://community.tp-link.com/en/home/stories/detail/1726
4 cores is a bit limiting, but definitely depends on the usage. I only have 1 VM on my NUC, everything else is docker.
I thought all the core processors had VT* extensions, I was using virtualization on my first gen i7. They are very old an inefficient now though.
I5 3470 is old, but its not that bad. Lots of people are homelabing on NUCs which are only very slightly faster. Performance per Watt will be terrible though. (I am on an i7-10710u, and I’ve yet to run out of steam so far - https://cpu.userbenchmark.com/Compare/Intel-Core-i7-10710U-vs-Intel-Core-i5-3470/m900004vs2771 )
It has VTx/VTd, so should be okay for proxmox, what makes you think it won’t work well?
You have a typo: platform: esphome
.
Thanks for posting, good catch!
I think my instance is now defed’d from hexbear, but when it wasn’t, they were the reason I wouldnt recommend lemmy to my partner. Their “trolling” was pure obnoxiousness.
The other major issue I think is the lack of moderation, lemmy just isnt a very pleasant space. There are still issues with spam. The CSAM incident a while back hasnt been repeated, but I have no reason to beleive it cant/wont happen again. Porn seems to hit All every so often.
With an agressively curated block list Lemmy can be nicer, but by default it just isnt.
Here is an idea for dissection: There should be a default blocklist that instances can provide and update. Defederation is too coarse a tool, but if instances (or third parties?) could provide a list of “bad” instances, “bad” communities and “bad” users that are used as the default blocklist. Users are free to opt out of the blocklist, but with a sane default lemmy could be a lot safer. (Or maybe not, im no expert)
Clevo/Metabox have always been my goto for upgradable/repairable machines. I got a Metabox P650SE over a decade ago, and it was rock solid for a very long time (still is usable, but its quite heavy now, so I upgraded to a thinner and lighter laptop).
Super easy to open and replace RAM, harddisks, clean out dust etc.
No trouble getting a replacement battery and bottom shell as it aged.
Definitelt thick as well. Downside is cost, they are not cheap. But also not Apple level expensive either.
I cant test this, but should it be something like:
# Example button configuration
button:
- platform: template
name: Livingroom Lazy Mood 1
id: my_button
# Optional variables:
icon: "mdi:emoticon-outline"
on_press:
- logger.log: "Button 1 pressed"
- platform: template
name: Livingroom Lazy Mood 2
id: my_button2
# Optional variables:
icon: "mdi:emoticon-outline"
on_press:
- logger.log: "Button 2 pressed"
As for the other thing, that might be something you need to write your own driver for? if you need some inspiration, this repo has a driver for mitsubishi heatpumps, which does something similar (read/write to a uart): https://github.com/echavet/MitsubishiCN105ESPHome
A bit of sniffling helps sell it, but it definitely seems to keeo people away from me. Or maybe i just smell bad :D
touch
😏