Dev, Systems engineer
@piefed.social
Dev, Systems engineer
Most people have bad taste. Most developers are not able to discern quality from bullshit. You see it every day. People enslaved by the news, by religion, by politics. OpenClaw is a fad like most of the other garbage out there. It uses 1000x the tokens of a normal AI user so obviously the AI wholesalers are paying attention. They want AI adoption and to maximize token usage. Remember the crypto bros punting web 3.0 as the world changing idea of the century? Well now it's easy to see that was garbage and it will be easy to see this paradigm of giving an insecure system access to all your shit is a bad idea in the near future.
My boy was fiv+ and he lasted 15 years after contracting it at age 9. He didn't get sick often and when he was younger he could go years without any issues but as he got older he developed kidney/liver issues and food sensitivity to even the best dry/wet foods. In the end he only ate tuna and boiled chicken breast. Every animal is going to be different and you just have to deal with things as they come up.
Hello!
If you want a bigger challenge, try solving the Dolby Vision vs HDR10+ fight between Samsung and LG/Sony.
I haven't seen anyone with a fully compatible solution yet. Im in the process of building some Tdarr plug-ins based off of this repo
https://github.com/...
The goal is to take source content that contains either DoVi profile 4,5,7,8 or HDR10+ and output a mp4 or mkv that contains the base HDR10 layer along with BOTH HDR10+ and DoVi 8 additional streams, and then test on various players to see if they can utilize those streams correctly for the ones they support.
This topic goes quite deep so be prepared to get sucked in. Your existing tickbox for "preserve HDR" probably doesn't work at all for DoVi profile 5.
Proper routers can be used to effectively firewall your services from the net (Cisco/Aruba/Juniper/Fortigate etc). Mikrotik is the cheapest.
For example, on a Mikrotik router in the IP filter rules:
Rule 1 - drop input traffic from a custom blacklist.
Rule 2 - accept input traffic that you want to port forward to your server.
Rule 3 - accept established and related traffic (tcp sessions that have passed SYN ACK stage).
Rule 4 - add source IP to blacklist for input traffic that you dont want to port forward to your server. Example: not 443,22 will trigger on all other ports.
This way if someone is scanning your ports they will be blacklisted and then will never get back in even on your open ports. I manage some large networks and our blacklist grows by around 50k IP addresses per week that are just scanning the internet. With a setup like this you don't have to worry that much about the servers open ports or its firewall. You can also write to the router log all successful requests and their source IPs if you ever want to double check who's been getting in.
Maybe I'm old, but I completely agree with you. There is a natural tendency to try reinvent something when you don't understand it enough to be comfortable with it. Then that new thing lacks the maturity and scrutiny that the old thing went through to survive the test of time. This is basically how overconfident tech bros are transforming the web.
Our VMware has become expensive enough that we're looking at Proxmox for enterprise workloads. We also run Azure local clusters but we can get much better hardware if the budget isn't drained by licensing. On Azure local the storage is expensive because you need 3x or more mirrors for all volumes and the deduplication doesn't make it that much better. We're thinking about a PowerStore with fibre channel for the block storage and then workloads on Proxmox clusters. One of the issues with Proxmox is their support for high network speeds like 100G is experimental.
thanks for using Leebra!
go to feed...