• 0 Posts
  • 26 Comments
Joined 1 year ago
cake
Cake day: June 10th, 2023

help-circle
  • Yep, sharing your trauma should be an exercise in trust and intimacy. People should not share their trauma with others just to provoke a specific emotional reaction. I also have some second-hand experience with what you mention. One of my SO’s parents is a hideously narcissistic person who would trauma dump all over my SO to invalidate any feelings or concerns my SO might have. That, combined with gaslighting and other forms of emotional abuse and neglect, plus some physical and sexual abuse set my SO up with a fuckton of trauma to process. They also had a hard time with hearing of other people’s traumas, although for them it was in more specific circumstances, rather than generally.

    I like to think that most people trauma dumping are victims who aren’t creating another iteration of the victim/abuser cycle (I base that off of nothing but my own hopes, I have no numbers), but there are definitely people who have weaponized it. I’m sorry to hear that you went through that :/ hopefully you’re free from those toxic people. After my SO’s parent kicked my SO out (a horrible night, but one of the best nights of their life in retrospect), my SO moved in with me, did a whole lot of EMDR therapy, and has managed to heal from the damage caused by their parent. Hopefully you can find a treatment, process, or mindstate to help you, since it sounds like you still have some wounds from what was done to you.


  • Having a frank and vulnerable discussion of your trauma with someone you have emotional intimacy and trust with is incredibly important and can help the healing process. I’d highly encourage people to do that.

    However, I think the term “trauma dumping” often refers to the practice of sharing your trauma with people who you don’t have a close relationship with, or with people who you haven’t interacted with long enough to generate trust.

    I am a former trauma dumper, and I dumped my trauma all over a person who I should not have. That person turned out to be a very untrustworthy person. Their knowledge of my wounds allowed them to do some incredibly harmful things to me over the course of an eleven months relationship. I managed to escape, but it was a bad move, and I learned to become more careful about who I shared that information with.

    Plus, there is always more to you than your trauma. It certainly doesn’t feel that way when you’re really stuck in it. Hell, me saying that may have just made some people very, very angry. I got really angry when my therapist said that to me, because it felt like she was minimizing what I went through.

    I came to understand that she meant I was an adult with passions and a whole life, and that adult is what I should share with people. By letting my adult self live in the present, I became more able to take care of my trauma using the inner child metaphor. My wounded inner child is precious and deserves care, and I share that with people who will appreciate that. The adult that I am also deserves to live and see the world, and deserves to be recognized by friends and family. Trauma dumping inverts that.

    People stop getting to see the awesome person you grew into because humans are wired to pay attention to wounded children, be they physical or metaphorical. Some people will be tender, some will be dismissive, and a few people will take advantage.

    So yeah, please share your trauma when it makes sense to, with people you love and trust. If there’s a mutual understanding, then any sadness they feel will likely be offset by the warm knowledge that they’ve helped you make it through another day and maybe heal a bit more. That’s what is shown in this meme. Let your adult self live your life the rest of the time, and use that adult to give the kid the care they needed but didn’t get.

    (Wow, now that I’m rereading this post, I feel a strong sense of irony. Like, it’s not a trauma dump, but also nobody asked for me to write a fucking essay about a meme lol)


  • I think you may be mixing up Project Orion (let’s chuck bombs out of the back to make us go zoom) with NERVA (a nuclear thermal rocket engine where the heat from chemical reactions is replaced with heat from a nuclear reactor to generate gas expansion out of a nozzle). Something like NERVA is actually a great idea. Let me tell you why!

    • It’s completely clean (unlike Orion and fission-fragment rockets)

      • the reactor and fuel never touch, the fuel goes through a heat exchanger and is not radioactive
    • it provides extremely high efficiency

      • chemical rockets top out at ~400-500 isp in vacuum
      • NERVA tests in 1978 gave a vacuum isp of 841
      • ion thrusters like NEXT has an isp of 4170
    • it provides lots of thrust

      • NERVA had 246kN of thrust
      • NEXT (which was used on the DART mission) is 237 millinewtons
      • That’s 6 orders of magnitude more thrust!
    • No oxidizer is needed

      • All you need is reaction mass, just like ion thrusters

    For automated probes, the extreme efficiency and low thrust of ion thrusters makes perfect sense. If we ever want to send squishy humans further afield, we need something with more thrust so we can have shorter transit times (radiation is a bastard). Musk is supposedly going to Mars with Starship, and the Raptor engine is a marvel of engineering. I don’t like the man and I’m not confident that he’ll actually follow through with his plan, but the engineers at SpaceX are doing some crazy shit that might make it happen.

    Just think though, if the engine was literally twice as efficient and they didn’t need to lug around a tank of oxidizer, how much time could they shave off their transit? How much more could they send to Mars? Plus, they could potentially reduce the number of big-ass rockets they have to launch from Earth to refuel. If you can ISRU methane, then I imagine you could probably get hydrogen.

    There are problems that still need to be resolved (the first that comes to mind is how to deal with cryogenic hydrogen boiling off), but like, the US had a nuclear thermal engine in the 70s. It was approved for use in space, but congress cut funding after the space race concluded so it never flew.

    I’m happy to see that NASA is once again researching nuclear thermal rockets. Maybe we’ll get somewhere this time.



  • People who eat Dayton-style pizza are like the city of Dayton itself—smelly inside and bereft of true purpose. Those of us in the US who haven’t been so psychically damaged wouldn’t eat that shit.

    (I’m only just learning about the disgusting gutter pizza. I don’t like Dayton because my last company was slowly destroyed over several years by a company that was headquartered in Dayton. I associate the city with the asshole who was CEO. Fuck you, Chris! I’ve heard Dayton is, at worst, not great, so take my comment as the joke it is.)


  • Badabinski@kbin.socialtoSelfhosted@lemmy.worldPost your Servernames!
    link
    fedilink
    arrow-up
    2
    arrow-down
    1
    ·
    edit-2
    6 months ago

    I just kinda vaguely name them after what they do and how big they are:

    smol: my tiny little 2 bay Synology NAS that I’m no longer using
    medium: my R620 with 4x 18TB drives that is my current NAS (medium, because it’s larger than my previous NAS). Is also a k3s worker and provides NFS PVCs.
    big: my old full-tower gaming rig that’s a k3s worker and runs my Home Assistant VM
    molecule: my current mini-ITX gaming rig and primary computer, also serves as the k3s master node and runs a lot of my home automation stuff. I think I picked molecule because it’s REALLY tiny (it’s in a Dan Cases A4v2, I think?) and it has a bunch of small stuff running on it (containers and pods)
    monolith: my old T440p laptop. It’s a large, black, featureless slab that doesn’t do much
    slab: my new Framework 13 laptop. I just kinda looked at it and said, “that’s a nice slab of metal”

    All of the above running Linux. I tinkered with Ubuntu for the NAS (because I heard Ubuntu was good at ZFS), but I still absolutely hate Ubuntu, so it’s all Arch Linux.




  • There are definitely a lot of good options out there. What are you using right now for regular old FTP? The odds are actually pretty good that it already supports SFTP. A lot of file management applications do both and lump them together, even though they’re completely different protocols (sftp is from the late nineties).

    If it doesn’t, then I don’t know what OS you’re using, so I’ll just recommend options for the big 3. For Windows, there’s WinSCP. For MacOS there’s Cyberduck. Most file managers on Linux distros let you just type sftp://me@wherever in the navigation bar, meaning you get a totally seamless experience with the rest of your FS.

    EDIT: or, you can use sshfs-win on Windows and have your remote filesystem show up as a regular ol’ drive, just like SMB. MacOS and Linux have sshfs, and I know there are GUIs wrapping sshfs on those platforms. I personally use sshfs at home and it’s great (although no GUI wrapper, I’m a weirdo who doesn’t use a graphical file manager at all).



  • PART 4.

    You expect a file transfer program to reliably and faithfully transfer your files, byte-for-byte, from one system to another. FTP spits in your face and shits on your chest. You know how Linux uses LF (i.e. \n) for newlines and Windows uses CRLF (i.e. \r\n) for newlines? Pretty annoying, right? Well, FTP’s ASCII mode will automatically rip off those \r characters for you! Sounds pretty sweet, right? Fuck no it’s not. All of the sudden, your file checksums have changed. If you pass the same file back to a Windows user with a different and more sane file transfer system, then they get a broken file because FTP didn’t mind its own fucking business. If you have a CRLF file and need an LF file, just explicitly use dos2unix. Wanna go the other way? unix2dos. The tool has been around since 1989 and it’s great.

    Now, what if you’re not transferring text, but instead are transferring a picture of a cute cat? What if your binary data happens to have 0x0D0x0A somewhere in it? Well, ASCII mode will happily translate that to 0x0A and fucking ruin your adorable cat picture that you were going to share with your depressed significant other in an attempt to cheer them up. Now the ruined JPEG will remind them of the futility of their situation and they’ll slide even deeper into cold emptiness. Thanks, FTP.

    You can tell your client to use binary mode and this problem goes away! In fact, modern clients do this automatically so your SO gets to see the adorable fuzzy cat picture. But let’s just stop and think about this. Why use a protocol that is dangerous by default? Why use a protocol that supports no form of security (unless you’re using fucking godawful FTPS or FTP over SSH)? Why use a protocol that is so broken by design that small business hardware has been designed to try to unfuck it? Is it faster? I mean, not really. SFTP has encryption/decryption overhead, but your CPU is so fast that you’d need to transfer at 25+ Gb/s to notice it. Is it easier? Fuck no it’s not easier, look at all of the stupid footguns I’ve just mentioned. Is it simpler? The line protocol is simple, but so is HTTP, and HTTP has a much simpler control flow path (merging the data and control planes is objectively the right thing to do in this context). And shit, you want a simple protocol for cases where you don’t have a lot of CPU power? Use fucking TFTP. It’s dogshit, but it was intentionally designed to be dogshit so that a fucking potato could receive data with it.

    There is no task that is currently being done with FTP that couldn’t be done more easily, more securely, and more quickly with some other protocol (like fucking SSH and SFTP, which is now built into fucking Windows for god’s sake). Fuck FTP.


  • PART 3.
    They made their STUPID MODEMS FUCK WITH THE FTP PACKETS. I have personally experienced this with Comcast Business. The stupid piece of shit DOCSIS modem they provide intercepts the FTP packet from your server saying “oh, connect to this address: x.x.x.x:44010” and they rewrite the fucking address to the public IP. There is no way to turn just this horse piss off. Now, for average business customers, this probably saved Comcast a bunch of money in support calls. However, if you’re using the so-called bridge mode on that degenerate piece of shit-wrapped-silicon (where rather than allowing the modem to give you a DHCP address, you just configure your system to have one of the addresses in the /29 space and the modem detects that and says oh okay don’t NAT traffic when it’s going to this address, just rewrite the MAC and shunt it over the right interface), then something funny happens. The modem still rewrites the contents of the packet, but it uses the wrong fucking IP address! Because the public IP that your server is running on is no longer available to the modem, the modem just chooses another fucking address. Then, the client tries to connect to 1.2.3.5 instead of 1.2.3.4 where your server is listening, the modem says “hey I’m 1.2.3.5 and you can fuck off, I’m dropping your SYN for port 44010”, and I get an angry call from the client asking why they can’t download their files using this worthless protocol. I remember having a conversation like this:

    Me: “Just use SFTP on port 22!”
    Client: “No! FTP is faster/more secure/good enough for my grandfather good enough for me/corporate won’t allow port 22.”
    Me: “Comcast is fucking me right now. What if we lied and served SFTP over port 21?”
    # we try it
    Client: “It’s not working! I can’t even connect!”

    I couldn’t connect either. I couldn’t connect to anything. Trying to do SFTP over port 21 caused the stupid fucking modem to CRASH.

    Are you starting to see what the problem is? It’s like Microsoft preserving bugs in Windows APIs so that shitty software doesn’t break, and then they end up doing crazy gymnastics to accomodate old shit like the Windows 8 -> Windows 10 thing where they couldn’t use “Windows 9” because that would confuse software into thinking it was running “Windows 95” or “Windows 98”. FTP has some bugfuck crazy design decisions that we’ve collectively decided to just “work around,” and it leads to fucking gymnastics.

    Speaking of bugfuck crazy design decisions, FTP’s default file transfer mode intentionally mangles data!

    Continued in part 4.


  • PART 2.

    NAT, much like the city of Phoenix, is a monument to man’s arrogance. Fuck NAT and fuck FTP. If your FTP server is listening directly on a public IP address hooked up directly to a proper router, then none of this applies. If you’re anything like me, the last company I worked for (a small startup), or my current company (many many thousands of employees making software you know and may or may not hate, making many billions of dollars a year), then the majority of your servers are living in RFC1918 space. Traffic from the internet is making it to them via NAT (or NAT with extra steps, i.e. L4 load balancers).

    A request comes in for $PUBLIC_IP TCP port 21 and is forwarded to your failure of a boxen at 10.0.54.187. Your FTP server is a big stupid idiot and doesn’t know this. It thinks that it’s king shit and has its own public IP address. Therefore, when it’s deciding what ADDR:PORT it’s going to tell the stupid FTP client to connect to, it just looks at one of the adapters on the box and says “oh, I’ll tell this client on the internet to connect to 10.0.54.187:44007” and then I fucking cry. The FTP client is an idiot, but the IP stack on the client’s home/business router is not and says “oh, that’s an address living in RFC1918 space, I shouldn’t send that out over the internet” and they don’t get the results of their LIST.

    So, how do you fix this? Well, you fix it by not using FTP. Use SFTP USE SFTP USE SFTP FOR GOD’S SAKE. But since this world is a shit fucking place, you have two options. The best option is to configure your FTP server to lie about its IP address. Rather than being honest about what a fool it is, you can tell it to send your public IP address to the client rather than the network adapter IP address. Does your public IP address change? Fuck you, you get to write a daemon that checks for that shit, rewrites your FTP server config, and HUPs the bastard (or SIGTERMs it if your server sucks and can’t do a live config reload).

    Let’s say that you don’t want to do that. Let’s say you work at a small company with a small business internet plan that gives you static IPs but a shitty modem. Let’s say that you don’t know what FTP is or how it works and your boss told you to get it set up ASAP and it’s not working (because the client over in Bendoverville Arkansas is being told to connect to a 10.x.x.x address) and it surely must be your ISP’s fault. So you call up Comcast Business/AT&T/Verizon/Whoeverthefuck and you complain at their technicians for hours and hours, and eventually you get connected to a human that knows what the problem is and tells you how to configure your stupid FTP server to lie like a little sinner. The big telco megacorps don’t like that. They don’t want to waste all those hours, and they don’t want to hire too many people who can figure that shit out because it’s expensive. You wanna know what those fucking asshole companies did?

    Continued in part 3.


  • I’d like to interject for a moment. What you’re referring to as FTP is, in fact, smelly hot garbage.

    For context, I wrote this while waiting for a migraine to pass. I was angry at my brain for ruining my morning, and I like to shit on FTP. It’s fun to be hyperbolic. I don’t intend for this to be an attack on you, I was just bored and decided to write this ridiculous rant to pass the time.

    I must once again rant about FTP. I’ve no idea if you’re serious about liking it or you’re just taking the piss, but seeing those three letters surrounded by whitespace reminds me of all the bad things in the world.

    FTP is, as I’ve said, smelly hot garbage, and the infrastructure built to support FTP is even worse. Why? Well, one reason is that FTP has the most idiotic networking model conceivable. To see how crazy it is, let’s compare to a more sane protocol, like HTTP (for simplicity’s sake, I’ll do HTTP/1.1). First, you get the underlying transport protocol stuff and probably SSL. The HTTP client opens a connection from some local ephemeral port to the destination server on port 80/443/whatever and does all the normal protocol things (so syn->synack->ack and Client Hello -> Server Hello+server cert -> client kex+change cipher -> change cipher -> encrypted data). FTP does TCP too! Same same so far (minus SSL, unless you’re using FTPS). Next, the HTTP client goes like this:

    GET /index.html HTTP/1.1
    Host: www.whatever.the.fuck
    # a bunch of other headers
    
    

    and you know what fucking happens here? The fucking server responds with the data and a response code on the same goddamn TCP connection. You get a big, glorious response over the nice connection you established:

    200 OK
    # a bunch of headers and shit
    
    HERE'S YOUR DAMN DATA NERD
    
    

    So that’s nice, and the client you’re using to read this used that flow (or an evolution of that flow if you’re using HTTP/2 or HTTP/3). So what does FTP do? It does one of two really stupid things depending on whether you’re using active or passive mode. Active mode is the default for the protocol (although not the default for most clients), so let’s analyze that! First, your FTP client initiates a TCP connection to your server on port 21 (by default), and then the server just sends this:

    <--- 220 Rebex FTP Server ready.
    
    

    ok, that kinda came out of nowhere. You’re probably using a modern client that saves you from all of the godawful footguns, so it then asks the server what it supports:

    ---> FEAT
    <--- 211-Supported extensions:
    <---  AUTH TLS;SSL;
    <---  CDUP
    <---  CLNT
    # A whole bunch of other 4 letter acronyms. If I was writing an FTP server, I'd make it swear at the user since there are a lot of fun 4 letter words
    
    

    There’s some other bullshit we don’t care about right now, although highlights include sending the username and password in plain text. There’s also ASCII vs binary mode. WE’LL GET BACK TO THAT. :|

    So then we want to do a LIST. You know what happens in active mode? Your computer opens up some random fucking TCP port. It then instructs the FTP server to CONNECT TO YOUR GODDAMN COMPUTER. Your computer is the server, and the other side is now the client. I would post a more detailed overview of the FTP commands, but most servers on the internet disable active mode because it’s a goddamn liability. All of the sudden, your computer has to be internet facing with open firewall ports, and that’s just a whole heap of shit.

    I’m probably not blowing many minds right now because people know about this shit. I just want to mention that this is how FTP was built. The data plane and control plane are separate, and back in 19XX when this shit was invented, you could trust your fellows on ARPANET and NAT didn’t exist and sure HAM radio operators here’s the entire goddamn 44.0.0.0/8 block for you to do packet switched radio. A simple protocol for simple times, back before we knew what was good and what was bad.

    So, active mode sucks! PASV is the future, and is the default on basically all modern clients and servers! Passive mode works exactly the same as the above, except when the client goes to LIST, the server opens some random TCP port (I’ve often seen something like 44000-44010) and tells the client, “hey you, connect to 1.2.3.4:44000 to get you your tasty data.” Sounds great, right? Well, there’s a problem that I actually touched on in my last paragraph. Back when this dogshit was first squeezed out in the 70s, everyone had a public address. There were SO MANY addresses! 4 billion addresses? We’ll never use all of those! That is clearly not the case anymore. We don’t have enough addresses, and now we have this wonderful thing called NAT.

    Continued in part 2.


  • Eating this stuff would be about as bad as eating any regular cat litter that uses Fuller’s earth as the primary absorbent. The extra special ingredient (powdered quartz) is effectively nontoxic when ingested. The real issue is the chronic exposure to very fine silica dust.

    Edit: to clarify, I do not believe that it would be safe for humans or animals to use this as cat litter. Just realized that this comment might have been taken as a “well akshually it’s fine.” It is not fine, silicosis is a dreadful condition.


  • So I’d like to chime in. It looks the the two primary ingredients for ZEP-o-zorb are Fuller’s earth and powdered quartz.

    First, Fuller’s earth. This is good stuff! It’s actually often used as an industrial absorbent for chemical spills (the purpose of ZEP-o-zorb), as well as in some types of cat litter. It totally makes sense why this stuff would work well for you, and I understand why you’ve been using it for a year. It’s perfect for the task and has basically no downsides.

    Now, about the powdered quartz… Chemically known as silicon dioxide. It’s often refered to as silica. Silica is also good stuff! It’s in concrete, it’s the main component of glass, and of particular interest for your application, it’s very good at absorbing volatile organic smelly stuff. Seems perfect, right?

    Unfortunately, powdered quartz has a downside. When it’s in a very fine powder, it produces a lot of dust. This silicon dioxide dust is incredibly harmful to your lungs. Long-term exposure to silicon dioxide dust results in silicosis, which is a really serious illness that kills tens of thousands of people every year. Inhaling that dust can also give you lung cancer, lupus, rheumatoid arthritis, or other autoimmune disorders.

    I totally understand why you felt that this product was a great option! I don’t doubt that it serves as an absolutely excellent cat litter. I had two kitties that took the smelliest shits, and I was always searching for ways to fix that (either through diet, litter, stress reduction, or other things). I also understand how upsetting it can be to share something with people and be met with disbelief, denial, and accusations. However, I really want to urge you to look past all of that and reconsider your use of this product. The silica dust is practically invisible and tasteless, and it had the chance to cause you many years of problems. You and your cat deserve to be healthy.



  • Badabinski@kbin.socialtoMemes@lemmy.mlGotta get it right
    link
    fedilink
    arrow-up
    31
    arrow-down
    3
    ·
    9 months ago

    I hate righty-tighty lefty-loosy. Depending on whether you’re looking at the top or bottom of the screw, you can see movement to the right or the left. I hate whoever came up with it, and I wish I had been taught the right hand method. It works exactly the same as the electromagnetic right hand rule:
    an example of the right hand rule as it relates to a screw thread

    Basically, you take your right hand, stick your thumb out, and curl your fingers like you’re grabbing a broom handle. Point your thumb in the direction you want the screw to move to. Want to screw something in? Point your thumb towards the thing. Want to unscrew? Point your thumb away from the object the screw is currently in. Then, just look at the way your fingers are pointing! If it helps, squeeze your fingers into a fist and see which way they move. Alternatively, bend your wrist in, and observe which way your fingers are moving. Works every time.

    It sounds complicated, but there are plenty of people who are unable to intuitively differentiate from right and left the way they can differentiate up and down. I am one of those people. Thanks to this method, I’ve been able to develop the muscle memory/intuition to know which way to turn a screw.

    It’s important to note that this only works for screws that are “right hand threaded.” If the screw is only getting tighter when you’re using this method, then it’s likely reverse threaded, or left hand threaded. If that’s the case, just use your left hand instead of your right hand.



  • Badabinski@kbin.socialtoAsklemmy@lemmy.mlWhat's with all the tech layoffs?
    link
    fedilink
    arrow-up
    115
    arrow-down
    1
    ·
    edit-2
    9 months ago

    I want to offer my perspective on the AI thing from the point of view of a senior individual contributor at a larger company. Management loves the idea, but there will be a lot of developers fixing auto-generated code full of bad practices and mysterious bugs at any company that tries to lean on it instead of good devs. A large language model has no concept of good or bad, and it has no logic. It’ll happily generate string-templated SQL queries that are ripe for SQL injection. I’ve had to fix this myself. Things get even worse when you have to deal with a shit language like Bash that is absolutely full of God awful footguns. Sometimes you have to use that wretched piece of trash language, and the scripts generated are horrific. Remember that time when Steam on Linux was effectively running rm -rf /* on people’s systems? I’ve had to fix that same type of issue multiple times at my workplace.

    I think LLMs will genuinely transform parts of the software industry, but I absolutely do not think they’re going to stand in for competent developers in the near future. Maybe they can help junior developers who don’t have a good grasp on syntax and patterns and such. I’ve personally felt no need to use them, since I spend about 95% of my time on architecture, testing, and documentation.

    Now, do the higher-ups think the way that I do? Absolutely not. I’ve had senior management ask me about how I’m using AI tooling, and they always seem so disappointed when I explain why I personally don’t feel the need for it and what I feel its weaknesses are. Bossman sees it as a way to magically multiply IC efficiency for nothing, so I absolutely agree that it’s likely playing a part in at least some of these layoffs.