Is American Pragmatism a thing? If you explain it to me, will I feel better about myself?
Is American Pragmatism a thing? If you explain it to me, will I feel better about myself?
Devops is a meaningful term
Indeed, and good points. How many users do you have? I assume this isn’t just for you, and setting up multiple nfs shares with tailscale access policies isn’t feasible. SMB might be the best play. I’ll have to refresh my memory on file sharing protocols
NFS for storage, tailscale / wireguard for access control?
Your current setting is the “loopback” address. You’re listening for traffic to this address, and the only thing that can send to the loopback is yourself. This is a safe default, it means only the computer running the software can talk to it. Generally 0.0.0.0 listens on all available addresses. If that doesn’t work, use your local / internal ip.
This ui smells like it’s trying to hide the implementation details, but that makes things extremely difficult when troubleshooting
You can reduce doorknob turning dramatically by running on a non-standard port.
Scanners love 80 and 443, and they really love 20, but not so much 4263.
I used to run a landing page on my domain with buttons to either the request system / jellyfin viva la reverse proxy. If you’re paranoid about it, tie nginx to a waf. If you’re extra paranoid, you’ll need some kind of vpn / ip allow-listing
That looks promising. Just keep in mind that this will take a very long time to run. I believe there is a *arr out there that can manage this / show progress, but the name escapes me
Are you telling me that pop tarts are not in fact ravioli?
The VPN catches all network traffic and puts it far away - you can’t be on vpn and see local network resources (casting targets) at the same time.
If your vpn has an app, check your settings for something like “local network access”.
Otherwise, start reading about split-tunnels and/or default gateways
The game of Mao begins now.
Even more unusual variants include […] a game which, instead of allowing voting on rules, splits into two sub-games, one with the rule, and one without it.
This sounds insane and delightful
I gave their protocol page a look; it’s extremely in-depth. I have no idea what a vector clock is but now I get to learn. I like how they explain why blockchain isn’t a good fit.
I’m a touch worried about the extensability of the protocol, but I haven’t given it a deep read yet. I very much appreciate the share!
At EoL, corporate security tells the IT department to uninstall it.
Windows works great because MS tapes it back together slightly faster than it falls apart.
When EoL hits, those devices are either trashed, firewalled into oblivion, or assimilated into the kube.
Wanna come configure optimus for me?
This will go about as well as broadcom’s acquisition of Symantec (not well).
If you can get rid of vmware, you will have to, and if you can’t, you’ll ship buckets of benjamins to broadcom and in return they might keep your company alive.
It is exceptional, thank you for asking :)
10 minute intro
Proceeds the weedian
5 minute solo
Nazareth
song continues in this manner for another 45 minutes
Any form of bread with a filling, generally assembled cold
But, dare I say, does that not make a ravioli a sandwich? A poptart? Mayhaps even … Lasagna?
Ah, you proclaim! But those are cooked further!
But so too is a grilled cheese! And a patty melt!
Where will the madness end?
I must disagree.
We need not wait for marginalized groups to be impacted to decry T1 ISP censorship. Ban whatever speech you want; the method of enforcement should be to arrest the perpetrators - not stop the sale of paper, the delivery of mail, or blocklist class A ip ranges.
On a more philosophical level, this is the question of “kindergarten policy” - do we punish those who crayon on the walls, or do we take away everybody’s crayons. To punish the ability to do wrong, or the act of doing wrong. Like most philosophical questions, there’s no good answer to this.
Thank you, that’s an excellent read! This reminds me of the “expected value of perfect information” - sometimes it is worthwhile to answer a question, and sometimes it isn’t. Every once in a while I find myself in an engineering call discussing a minor problem, and I run the numbers to see if the change we are discussing is even worth talking about. One time the combined salaries of the people on the call had already outpaced the cost savings of the change over the next 10 years. We quickly stopped that discussion lol