I don’t have direct experience with them, but my understanding from youtubes is that the ugreen NASes are specifically designed for you to just ignore their OS and install your own (so truenas or proxmox).
Hardware tinkering is more limited but… there is very much a question of how much of that people actually do.
Raspberry pi: No. Or, at least, not without doing something to make sure you have a real storage backend and aren’t just running it off an SD card. The wear on SD cards is exaggerated and largely minimized if you use an OS that is configured to be aware of it but you are also increasingly relying on a ticking time bomb.
Mini PC/NUC? I am a huge fan of these and think they are what most people actually need for stuff like home assistant, adguard, etc. Just understand you are going to be storage limited sooner than you expect and you can oversubscribe that CPU and memory a lot faster than you would expect.
My general suggestion? Install proxmox on the mini PC and deploy on top of that. If/when you decide you want something more, migration is usually pretty easy.
And if you just want a NAS? It is really hard to go wrong with a 4 bay NAS from one of the reputable vendors (which may just be ugreen at this point?) as those tend to still come out cheaper than building it yourself and 4 disks means you can either play with fire with RAID5 or not be stupid and do RAID1.
Its cops. They just saw a black kid and figured they could plant a dime bag or a toy train after the fact.
Presumably most of those services on the same physical host are running in containers? So just add tailscale as a sidecar to that. Each container will be its own host as far as your tailnet is concerned and have its own internal IP. The official tailscale youtube has tutorials on that because it maps much better to a portainer based setup and more or less requires clients to have the tailnet running constantly (which, in my opinion, defeats the purpose of selfhosting but you do you).
Or do a mess with SRV records and… good luck with that
Wait… if you JUST want your domain to point to the tailscale IP and to only work when the client is on the tailnet, this is… super duper easy?
Just install tailscale. Go to your dashboard, and get the IP. And point your domain at that. No tunnels or reverse proxies needed.
This is one of the big problems with tailscale for home users. For people who only access a system remotely (e.g. a corporate VPN) it is amazing. For people who are both on and off network… yeah.
What I actually settled on was NOT using one of my domains and to instead just use the tailscale FQDNS in all situations. Mostly because I saw they added more human readable names so it is now like foo.happy-panda.ts.net instead of foo.tb12415161613616161616.ts.net
foo.sad-hamster.ts.net with zero additional config. Which is good if I am using an app on my phone or helping someone I trust set up their own machine without needing to drive/fly out there with a laptop.foo.sad-hamster.ts.net goes to foo.localdomain which goes to a 192.x IP seamlesslyEnd result is that I don’t need any special config in any devices or apps and everything just uses the tailscale FQDN regardless of whether it is a “client” connected to the tailscale itself. Which ALSO avoids issues where things stop working during an internet outage.
I’ve seen alternative setups that specify their own DNS server in their tailnet and… that is a lot of effort if you ask me. Also it seems to be the leading cause of “When I connect to my tailnet I can’t see the outside internet anymore”.
The big drawbacks to this are that it makes assigning actual certs rather messy since the same FQDN goes to multiple very different IPs… at least one of which being a potential security vulnerability since it is assigned by whoever controls the LAN you are on at any given moment. Not the end of the world and, truth be told, I am less likely to bother with proper certs for fully internal resources (unless I am getting paid to do it). So no NEW risk vectors.
The other is that you are kind of at the mercy of tailscale corp changing their business model entirely and suddenly having to deal with the fqdn that points to your plex server now actually being used for the latest dating app and everything catching on fire until you remember you did this. But that is a problem that is multiple years down the road…
Also, depending on what DNS/network shenanigans you do, this could cause other issues. But that is why you always test things yourself.
Two parts to this:
The first is Reddit (or any site) being able to identify you. And that is not a hard problem. Either they fingerprint the browser so your cookies tell who you really are or they just analyze your traffic and realize this user in Istanbul is constantly looking at the Cleveland subreddit. Its why VPNs aren’t really (at all) useful for privacy unless you are combining it with burner accounts and even browsers. VPNs mostly are just useful for accessing region/network limited resources and spinning up a true beater.
As for the ban? They probably changed VPN, got an IP that a known “bad” user used, and got immediately caught in the same automated banwave. Don’t use VPNs with accounts you actually care about. Partially because of the risk of data leakage but also because you don’t know what the last person using that IP did. See also why you wear a condom before you stick it in the glory hole.
Bit late but nobody really answered the core question yet so:
Intake fans: Intake fans are generally used in conjunction with exhaust fans to create airflow and improve cooling. This is why computers have two fans (at least) and so forth.
Exhaust fans: In addition to the above, exhaust fans are also used to control emissions/pollutants. If your printer has an exhaust fan it should, bare minimum, have a cheap carbon filter attached to it. A proper exhaust system is theoretically better but that tends to be better handled as a fume hood.
So when would you use either? A rule of thumb is that exhaust should probably always be on (while printing) if only to mitigate fumes and particulates. Even with the door open it will still help a bit. This applies to both “safe” filaments like PLA and outright toxic stuff like ABS.
As for intake? You probably also want it on any time the exhaust fan is on (so always) just to improve airflow and make the exhaust fan more effective. You aren’t going to pull a vacuum without it but it still helps.
So when would you control them separately? I would probably say “never” but I could see a case where you have a particularly toxic low temperature/fragile filament (like TPU cut with a lot of ABS or something?) combined with a fragile print. You want as much filtering as possible for health reasons but you want to minimize air flow to minimize premature cooling or even the risk of “blowing down the print” as it were.
So… yeah. I would very much lean towards just having the intake/exhaust on the same controller.
While it amuses me greatly to think his dick is disfigured from a botched surgery and he is in constant pain and embarrassment, the reality is likely that…
There are two broad ways to have sex. The first is to actually engage with the other person and have some fun. The other is to pump until you nut and then move on because you just care about saying you had sex.
Many chud adjacent white males do the latter. They just care about saying they had sex and care so little about the other person’s pleasure that they don’t even care about their own. Many are also taught to consider pleasure to be a sin but… talk to some sex workers. It is more likely just varying levels of sociopathy.
So under those circumstances? I could see a world in which they banged solely for the cuckolding aspect. Just like the flight attendants he allegedly sexually assaulted and had to pay off. But the vast majority of the women he “sleeps with” are going to be a case of jizzing into a test tube and telling them to get IVF because his goal is just breeding and banging would take up time that could otherwise be spent snorting ketamine. And when he DOES want to get his rocks off, he can just exploit some rando around him because it doesn’t matter who does it so long as someone does.
deleted by creator
Even in a scholarly discussion, giving the source of a quote (“the UN’s criteria for Genocide”) is usually more than enough for a discussion and arguably even a journal paper.
Optimally? Yes, you do actually get your bibtex on. But fricking nobody likes footnotes in a discussion. If it is central to the thesis then you definitely cite (and date/archive that). But as an aside or a fun fact? You’ll get dinged in English class but made fun of by editors who acknowledge you are correct but also want to give you a wedgie for actually doing it.
Lemmy is the public facing internet. It is no different than anywhere from a community standpoint (and has a lot of implications from a privacy/security one).
But, to harp on that: You randomly popped in and accused someone of potentially spreading misinformation. I pointed out that they actually already provided the source of that quote and you could find it yourself with a quick google.
Which gets into the idea of algorithm driven versus self curated online experiences. The Algorithm is wonderful for getting your rocks off. But, as you rightfully pointed out, it is not a good idea to have other people curate your facts and information. Hence: Learn to verify stuff yourself.
Really fucking dark story time!
Back before the latest war kicked off and nobody gave a shit about Ukranian sovereignty outside of that one bit on Seinfeld, Crimea was a discussion point for one reason or another. With the main argument being that russia can’t give it back because it is not even Ukranian in culture or ethnicity and is really russia anyway.
And a friend pointed out… they aren’t wrong. Because they ethnically cleansed the hell out of it after invading.
https://letmegooglethat.com/?q=Forcibly+transferring+children+of+the+group+to+another+group
Yes, you are correct in that people should be wary of basically everything they read on the internet.
The previous poster not only told you the context but also gave a trivially searchable string. And it is always good to do your own research rather than decide you don’t trust someone to tell you the truth but you DO trust them to tell you they are telling the truth.
Historically? Mid-20s when you enter the work force and start wondering why groceries are so expensive. And then you lose your mind and get angry that life was so much better when you were 10 and not paying attention to that.
Yeah. There are a few useful websites I end up at that serve similar purposes.
My usual workflow is that I need to be able to work in an airgapped environment where it is a lot easier to get “my dotfiles” approved than to ask for utility packages like that. Especially since there will inevitably be some jackass who says “You don’t know how to work without google? What are we paying you for?” because they mostly do the same task every day of their life.
And I do find that writing the cheat sheet myself goes a long way towards me actually learning them so I don’t always need it. But I know that is very much how my brain works (I write probably hundreds of pages of notes a year… I look at maybe two pages a year).
One trick that one of my students taught me a decade or so ago is to actually make an alias to list the useful flags.
Yes, a lot of us think we are smart and set up aliases/functions and have a huge list of them that we never remember or, even worse, ONLY remember. What I noticed her doing was having something like goodman-rsync that would just echo out a list of the most useful flags and what they actually do.
So nine times out of 10 I just want rsync -azvh --progress ${SRC} ${DEST} but when I am doing something funky and am thinking “I vaguely recall how to do this”? dumbman rsync and I get a quick cheat sheet of what flags I have found REALLY useful in the past or even just explaining what azvh actually does without grepping past all the crap I don’t care about in the man page. And I just keep that in the repo of dotfiles I copy to machines I work on regularly.
I would generally argue that rsync is not a backup solution. But it is one of the best transfer/archiving solutions.
Yes, it is INCREDIBLY powerful and is often 90% of what people actually want/need. But to be an actual backup solution you still need infrastructure around that. Bare minimum is a crontab. But if you are actually backing something up (not just copying it to a local directory) then you need some logging/retry logic on top of that.
At which point you are building your own borg, as it were. Which, to be clear, is a great thing to do. But… backups are incredibly important and it is very much important to understand what a backup actually needs to be.
It is obviously based on an outdated concept of gender, but it actually is pretty useful to help match people to passports. If someone identifies as male but is dressed like a woman, it raises red flags. The answer to that might be as simple as “This is a 90s sitcom and I lost a transphobic bet” but it is there. Same with hair color.
Which, funny enough, is an argument for people to actually write down the gender they identify as. But it is also a lot like hair color or facial hair in that it is just too cost and time prohibitive to update a passport every time someone tries a new look. Because… genderfluid people exist.
For a (first) NAS, I generally discourage this.
Office liquidation desktops are great for home servers (if you aren’t paying for power). But they generally are very limited on storage. Limited bays to install hard drives and limited SATA ports. So you rapidly end up with drives just sitting on the bottom of the case and real jank pcie boards to extend your storage.
Which then becomes a HUGE issue when you have a drive failure. Because now you need to actually identify which drive is the failed one which involves reading off serial numbers and, depending on the setup/OS, making sure you get the order right when you plug them back in.
Whereas a 4-bay NAS generally has dedicated hardware and hot swap bays which make this trivial. You might never actually use the hot swap capability, but it makes checking which drive is the bad drive fairly trivial.
Also, a good 4 bay NAS is REAL easy to unplug and put in the trunk of your car during a disaster. Don’t ask me how I know.