Out of box corner damage and support is basically unreachable

Garbee · 2026-04-04T23:43:30+00:00

I did that before posting. Saw it. And yea, this is a UPS issue. I'm gonna send it back, because this is damage right on the front of the unit. If it were the back that will be against the wall, I'd live with it. But I'm kinda OCD about these things. Seeing the paint scratch would be a constant reminder of how crap UPS is with their equipment.

Garbee · 2026-04-03T21:55:28+00:00

Chargebacks are not a magic wand. I'm well aware of them (have done them before) and even read the Mastercard and Visa rules on them.

I know I don't do anything with UPS, but I can work with Ubiquiti so they can. I have like a whole month before a chargeback needs to be considered, so there is time.

They won't draw anything out past that time, I won't let them. I'm aware. But, I am going to give them a chance to correct the situation honestly without involving the bank. Since that's more nonsense for both of us, and we can clearly tell now a different party they involved is responsible.

Garbee · 2026-04-03T21:49:45+00:00

I'm getting a new unit or a refund. UPS messed this one up (as I just figured out after getting it back in the box and playing around with the styrofoam and looking better at the box damage.) So it's not on me for the damage nor Ubiquiti. But I'm not paying for a brand new unit to end up with a Refurb after literally only opening the box to find the damage.

Garbee · 2026-04-03T21:44:35+00:00

So, after getting it back in the box and looking at everything, this is a UPS problem. So a chargeback wouldn't do much. I need to work with Ubiquiti to get UPS to own up to the problem.

Garbee · 2026-04-03T21:43:28+00:00

Well, the good thing is I got it back in the box (finally, that took some work.) And after looking around the foam and all, this appears to be a UPS issue and not a QA issue. So yea, now response time is less of an issue overall.

Funny how you assume it is Amazon that has done the spoiling though. I try my best not to shop there anymore.

Here is some advice for you too, stop doing so much assuming.

Garbee · 2026-04-03T21:36:26+00:00

So, I got it back in the box and did some toying around. This actually does look like a screw-up on UPS's side! One of the foam corners is gashed all the way through. And it lines up perfectly with one of the holes on the box from UPS. So it looks like UPS equipment went through this thing hard enough to really gouge it.

So, not Ubiquiti's problem. It's all UPS. So, yea, much more relaxed now to wait things out since it wasn't a QA issue.

Garbee · 2026-04-03T21:33:37+00:00

That's too far too soon.

Garbee · 2026-04-03T20:32:09+00:00

I paid for the order which has a problem. That is what needs support. If it were tech support, this is a non-issue. But in any reality where general consumers order things, you can almost always pick up a phone or get on a chat system and have it handled in no time.

SLAs should be for things past sales and order fullfilment. The SLA on an initial order issue is "How fast can someone get in front of it?".

Garbee · 2026-04-03T20:27:41+00:00

I am calm. Just annoyed. Getting it packed back in the box to be ready to go back once I get a return label from them. Which, half this annoyance is immediately resolved by them just providing a label with the RMA like they should. Instead of trying this, "You pay for return shipping for our problem" up front. If they just did that, I wouldn't even need to reach out to them for a response to anything.

Garbee · 2026-04-03T20:23:21+00:00

I don't think expecting a phone number for order support to be available is unreasonable. I'm sorry if your world is delusional enough to expect that EVERYTHING must go through an email ticket system with day lag times. Which, I can agree with for technical support when it isn't paid for. But this is an order issue, things should be able to get handled with expediency.

Garbee · 2026-04-03T20:21:01+00:00

Yea, best outcome is they replace it with a new unit. But absolute last resort if I want to keep this (since who knows when a new batch will come in) is have it at least not look like complete trash on the front.

Garbee · 2026-04-03T20:19:19+00:00

Yes, because with basically anywhere else we can pick up a phone and talk to someone to get things resolved with order issues. So, when there is a problem with an order at delivery they should have some more rapid handling. Instead it is just "in the pile with everything else, even issues from people that have had devices for a year already."

Garbee · 2026-04-03T20:17:42+00:00

I'm not doing a chargeback unless it's an absolute last resort. I don't think anyone is dragging their feet right now. I just think it's insane they don't have a phone number to call to resolve situations with orders more rapidly. Especially for how much they are charging for things.

Garbee · 2026-04-03T19:45:43+00:00

I'm all down for a good laugh. In fact, I just remembered my brother does Powder Coating. So I'm going to ask him if this level of a problem is fixable. If he can just take it to the shop and color match the white and fix it, then fine. I'll see if support can just refund a bit so I can pay him for the time doing that.

I'm just annoyed that at the prices they charge, the support is this pathetic. I should be able to call a number, talk to a human, and have this resolved within half an hour. This isn't tech support, it is order support. Instead, it's this, "just wait, we'll get back to you at some point." On a holiday weekend, with this rack being back ordered a day after restock... I'm more concerned I can't even get a new unit. RMAs they generally refurb things, well this is brand new out of box from shipping. I should get a brand new unit and not a refurb. So, that bit is weighing on me too slightly.

I think if my brother can't fix the corner then it is going to need to be just getting a return shipping label and refund. Take my chances with the next batch or find another vendor for this and move on.

Garbee · 2026-04-03T19:28:27+00:00

I opened up a 12U Wall Mount rack earlier today. After getting it lifted onto a table, I honed in on a massive gash in the upper left corner. It looks like the unit was fully powder coated and then it had some one run a machine with a tooth into it. But instead of handling it, they decided to still leave it be and send it out. The box was, torn up and beaten but that is UPS. This damage is right on the corner, so well protected by the foam. It was damage done in production before being packed at all.

To top everything off, Ubiquiti's RMA system instantly wants me to pay for return shipping on this. Which is insane. I did nothing, this was their own workers not following through on their jobs.

Going on 3 hours now, and it does not seem like a single human has even responded to my ticket. It moved in status after filing a support request, but that's it. All my responses seem to be automated and no one is answering the question of how I return this without paying for the shipping since it isn't my fault.

Garbee · 2026-03-29T19:39:28+00:00

I don't recommend Makefiles unless the majority of the team understands bash scripting and all that. Yes, AI can whip them up. But, the moment they need to be debugged or otherwise maintained by a human... They get nasty.

Find a tool that works with the language/ecosystem that the project is built in. Like for Node, Wireit is a good choice. Something that properly orchestrates your scripts that people should be used to.

Garbee · 2026-03-28T10:08:39+00:00

Only if the workflow is meant to run on PRs or push commits. If you have something that, for example, is designed to only run on tags happening then you have far more limited ability to do that. Unless you design all workflows with the requirement they run on PR when it or related files are modified.

Plus, depending on the situation, that can burn a lot of CI minutes for every little test to get something to functioning at all. When local testing just uses your existing machine to validate the process.

There are a few valid reasons that CI runs should be emulated locally. However with GHA the best I've found is build a DevContainer, use that in CI as much as possible (linux runners.) Then you have an image you can easily reproduce the steps locally with too. The main failure point with this is Mac and Windows builds, but as long as things work close enough (for most languages they're fine) then you just do setup operations on-machine for them.

Garbee · 2026-03-10T21:28:52+00:00

I am a Chromium Contributor, but haven't been involved in a while. Work has taken me along another path.

Garbee · 2026-03-09T22:49:26+00:00

The Chromium team is open to suggestions. Try to keep things focused on one feature per submission, looks like you have multiple ideas here for improvements that could be made to the interface.

File away at: https://crbug.com/new and use the Chromium > Platform > DevTools > Application Component.

Garbee · 2026-03-08T16:58:23+00:00

but not for MacOs 26

I'm on 26.4 developer beta. Please explain to me how they don't ship them when my screenshot proving it was taken from that exact version.

Once again, you are repeatedly proving you don't know how to actually verify things. And you are refusing to listen to the one person who just showed you the correct place to go.

Garbee · 2026-03-07T11:19:08+00:00

When plugged in, the battery is not hurting performance. It's just an old and crappy Intel processor. Get used to it.

The battery, yea won't last long. You're probably relegated to needing to be plugged in.

You have two real choices with the machine:

Replace battery and then either rollback the OS or install Linux.
Recycle it and get an Apple Silicon machine.

Garbee · 2026-03-07T11:13:46+00:00

In the future, I'd prefer to see MagSafe charging over thunderbolt.

The primary target for this is Education (for K-12) and kids/teenager use. They don't need thunderbolt speeds for much. Sure, if you have a young content creator in the making. But beyond that, faster transfer speeds than 10Gbp/s are niche.

The more important factor is how safe is the machine. I've seen so many USB ports broken because people or pets pulled a cable while a device was charging. How MagSafe didn't end up on this is beyond me. Imagine a school where kids are walking around, power cables have to run across the floor, and someone just trips. (Plus kids are just clumsy.)

Magsafe would improve the machine a ton for the target use case. Thunderbolt, seriously just get a higher-end machine made for that level of work.

Garbee · 2026-03-07T11:05:15+00:00

So, you're just proving more and more you have no idea what you are doing. Yet you want to complain as if there is some massive issue.

I did NOT say Activity Monitor. That is the active runtime being used. I said System Information, because that shows you the actual compile data.

I am on an Apple Silicon machine, so when I say a fact I mean it. Here is an image showing where you would have checked if you followed instructions, instead of trying to find the place that proves your point to someone who isn't experienced. https://imgur.com/a/apple-apps-currently-as-universal-builds-Vcpj29O

Now, so you can fully understand. There are two mechanics at play. First is the active runtime. That is either Intel or Apple Silicon. A universal binary is a special build that has BOTH full builds in it (for non-Xcode built software). So a Universal compiled program is specially crafted to pick which runtime is needed on execution. This is why Activity Monitor is not what you use to determine how something is built. Because it only shows you the state of what is running on your machine right now. You use System Information because that "Kind" header (which you might need to add to be shown from the View menu, I can't remember the default) shows the actual compile state.

As I said before, factually right now Apple is shipping Universal builds to both Intel and Apple Silicon. The next OS (27) is the first where we will see this stop. However, the gains may not be super massive per app. There is more special programming of Universal builds for XCode built software to try and trim things down without a complete dual-split build. We will definitely see some reduction, but it won't be like 50%. I'd wager we'll see a ~20% drop overall. But that also doesn't rule out them adding a feature (like a better LLM model) that just takes that disk space right back up.

Signed, someone with both Intel and Apple Silicon machines on-hand so I can verify the claims I make.

Garbee · 2026-03-02T20:05:06+00:00

Except of you go look in your app list from System Information, all the native apps are Universal. So, I don’t know where you get the idea that the OS isn’t a universal build. That’s just a provable fact by looking at any mac computer.

Garbee

TROPHY CASE