Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Search - "not that kind of leak"
-
!dev
So the ceiling in our (upstairs) laundry room started leaking. After some troubleshooting, we determined it was the A/C, and not the water pipes. (The house is cheap as hell and fucking stupid.) We did some troubleshooting and research, and tried fixing it ourselves; no luck. Cleaning the pipes from outside: no joy. Cleaning the pipes from inside: no access. The attic is ... small. Maybe half a small closet? and doesn’t give access to fucking anything. The builders must have installed everything before putting up the walls and ceilings, sealing everything off, because there is no access. It’s fucking stupid. Also, the usual maintenance openings aren’t even there either because why the fuck would they be?
But fucking whatever.
We called an a/c repair guy, who never showed. We assumed he was busy (it’s fucking hot), so we called him again the next day; two days later he showed.
Busy. Whatever.
Guy didn’t bring a ladder. Whatever, we have one right there in the hallway because we’ve been trying in vain to fix it.
Guy didn’t bring a wrench of any kind. Guy didn’t bring a screwdriver. Guy didn’t bring a bucket. Guy didn’t bring any pipe. Or any pipe sealant. Or fucking anything but his sagging fucking pants, fat belly, and fat stench. We had to supply everything, which fortunately we had on hand as we were already trying to fix it. Hoorah for being proactive.
Guy said he drained both primary and secondary pans. Somehow. Without access. I’m not even convinced it HAS a secondary pan. Guy said he cleaned out the pipes, too. From inside the house. Without access. Somehow. Maybe he did that from outside, without tools, while I was chasing the brats and someone else was watching the fat bastard. Who knows; I wasn’t with him most of the time.
When he was done, the guy said “pay whatever you think it’s worth” (or whatever). Fine, if he actually cleaned the pipes out and it isn’t leaking anymore, that’s great.
Guy leaves.
We go up to check. AND THE FUCKING A/C IS STILL LEAKING. BUT NOW IT’S FROM BEFORE THE PIPES, TOO. AND HALF AN HOUR LATER, THE LAUDRY ROOM CEILING IS ALSO LEAKING, WHICH MEANS THE PIPES ARE STILL LEAKING.
It turns out the asshole broke the pan.
We call him back, he goes blah blah blah, we send him a video. Drip, drip, drip.
His response?
“The pan must be rusted.” IT’S FUCKING PLASTIC.
“Oh, in that case, it’s probably a rusted coil that’s leaking.”
a) HOW DID YOU NOT KNOW IT WAS FUCKING PLASTIC IF YOU DRAINED IT?
b) THE COILS CARRY FREON, NOT WATER, AND THE A/C IS STILL WORKING. IF THERE WAS A LEAK, SHIT WOULD BE HOT. AND RANK. FREON SMELLS NASTY AND DOESN’T CAUSE IT TO RAIN IN THE FUCKING HOUSE.
REPLACING A COIL IS ALSO A $2000 FUCKING REPAIR.
THE FAT BASTARD PROBABLY BROKE THE PAN INTENTIONALLY JUST TO UPSELL. I WANT TO FUCKING MURDER HIS LYING FUCKING FACE OFF.
It’s possible he didn’t break the pan intentionally, so I’ll tentatively remove that from his charges. BUT TO FUCKING LIE?
LIE AND DIE, FUCKER.rant i can’t wait to move lie and die reasons why i’m a misanthrope lying fucking people everyone lies7 -
"There's more to it"
This is something that has been bugging me for a long time now, so <rant>.
Yesterday in one of my chats in Telegram I had a question from someone wanting to make their laptop completely bulletproof privacy respecting, yada yada.. down to the MAC address being randomized. Now I am a networking guy.. or at least I like to think I am.
So I told him, routers must block any MAC addresses from leaking out. So the MAC address is only relevant inside of the network you're in. IPv6 changes this and there is network discovery involved with fandroids and cryphones where WiFi remains turned on as you leave the house (price of convenience amirite?) - but I'll get back to that later.
Now for a laptop MAC address randomization isn't exactly relevant yet I'd say.. at least in something other than Windows where your privacy is right out the window anyway. MAC randomization while Nadella does the whole assfuck, sign me up! /s
So let's assume Linux. No MAC randomization, not necessary, privacy respecting nonetheless. MAC addresses do not leak outside of the network in traditional IPv4 networking. So what would you be worried about inside the network? A hacker inside Starbucks? This is the question I asked him, and argued that if you don't trust the network (and with a public hotspot I personally don't) you shouldn't connect to it in the first place. And since I recall MAC randomization being discussed on the ISC's dhcp-users mailing list a few months ago (http://isc-dhcp-users.2343191.n4.nabble.com/...), I linked that in as well. These are the hardcore networking guys, on the forum of one of the granddaddies of the internet. They make BIND which pretty much everyone uses. It's the de facto standard DNS server out there.
The reply to all of this was simply to the "don't connect to it if you don't trust it" - I guess that's all the privacy nut could argue with. And here we get to the topic of this rant. The almighty rebuttal "there's more to it than that!1! HTTPS doesn't require trust anymore!1!"
... An encrypted connection to a website meaning that you could connect to just about any hostile network. Are you fucking retarded? Ever heard of SSL stripping? Yeah HSTS solves that but only a handful of websites use it and it doesn't scale up properly, since it's pretty much a hardcoded list in web browsers. And you know what? Yes "there's more to it"! There's more to networking than just web browsing. There's 65 THOUSAND ports available on both TCP and UDP, and there you go narrow your understanding of networking to just 2 of them - 80 and 443. Yes there's a lot more to it. But not exactly the kind of thing you're arguing about.
Enjoy your cheap-ass Xiaomeme phone where the "phone" part means phoning home to China, and raging about the Google apps on there. Then try to solve problems that aren't actually problems and pretty vital network components, just because it's an identifier.
</rant>
P.S. I do care a lot about privacy. My web and mail servers for example do not know where my visitors are coming from. All they see is some reverse proxies that they think is the whole internet. So yes I care about my own and others' privacy. But you know.. I'm old-fashioned. I like to solve problems with actual solutions.11 -
2nd part to https://devrant.com/rants/1986137/...
The story goes on...
After I found more bugs that seem to be related to the communication break, and took a closer look, I sent detailed logs of my research and today we had a conference call.
"We have 2,5 million user, our system is widely-used and there is no plan to change it" they said.
And "We cannot reproduce the issue, but even if there is one, you will have to work around the problem, because we cannot make changes on our side" was one answer
As well as "If we would make changes, we will have to re-certify everything"
So I said we told 'em about the issue to let them improve their system. And I can work around it, I already figured out a solution for my side, but if there is a bug, they'd better fix it for future releases.
And with my additional research I have a bad vibe of some kind of memory leak involved on their "certified" implementation, and that could trigger various other problems.
But it is as always, if I try to be nice, I just get kicked in the ass. I should really be more of an asshole. -
What to do if someone asks for your help with problem X, but then you figure out they originally tried to fix problem A and recursively came up with bad solutions until they got at X at which point the entire codebase overlaps responsibilities, implementations leak, concrete instances are created in controllers ignoring DI and you just can't say ANYTHING nice about it?
Also does not follow a methodology and just does whatever, thinks singletonning a database context is a good option because stuff isn't saved, says they will 'refactor later' even though it should have been done last week and just doesn't seem to get it?
I've told them that what they're doing is plain wrong and they're making it harder for themselves than it needs to be, but they just seem to not get it, even though at this point basic stuff like that shouldn't be an issue.
Posted this in rant since it became kind of a rant instead of a question6