

does changing to a different dark vim theme help?
aspiring Rustacean, JavaScript jockey, 3D printing addict, use Bluefin Linux, (Apple|Google)-captive, Meta-escapee, parent, husband with a husband, cisgender, he/him


does changing to a different dark vim theme help?


hmmm, I’d consider Apple and Google to be roughly equal in terms of general overall evilness these days
they both donate to support fascism and genocide, remove anti-fascism apps and anti-surveillance apps from their stores upon government request (even when not legally required), spy on their users, etc
and their software/products seems to be in the final phase of enshittification
the fact that GrapheneOS exists and works on Google hardware at all seems like a plus in Google’s column, however it’s only necessary because default Android/Chrome are not allowed to go so far as to protect users from surveillance capitalism (so it’s a plus only necessary because of a negative)
unless there’s a specific measure where Google does significantly worse?


thanks, i hadn’t actually heard of ntop / ntopng before!
i believe ntopng works everywhere independent of whether calico is installed or not (and even calico is a Kubernetes-compatible and Kubernetes-optional system, just like ntopng)
but, calico whisker displays networking information made available by the rest of calico, so it’s able to give you a live display of when a firewall rule managed by calico is allowing or blocking traffic
i think this particular feature is absent from ntopng, but i could be wrong


yeah, when I say “far far too long” I think I’m on roughly the same window of time there 🫂
that said, still manage my nftables firewall on my other systems with firewalld and those concepts of zones has never really clicked in my brain
i did try cilium first, but it currently doesn’t work on Raspberry Pi 4B nodes: https://github.com/cilium/proxy/issues/1027
and now that my understanding of calico has improved, i appreciate that it works outside of Kubernetes, too
to help communicate and troubleshoot what is broken here, we need to think of Wayland as a protocol just like HTTP is a protocol
saying “Wayland broke X” is like saying “HTTP broke X”, which is possible but not likely to be what you’re actually trying to say
rather, we need to be talking about the implementation(s) of the protocol, not the protocol itself
e.g. “HTTP broke X” -> “Google Chrome broke X”
e.g. “Wayland broke X” -> “GNOME broke X”