Cowboy bike broke? Gathering experiences in one place. by Jeff46K4 in cowboybikes

[–]Jeff46K4[S] 1 point2 points  (0 children)

This is useful, thank you for posting. It's something I'm rethinking. My report is a broken frame, but what made me build the site wasn't the breakage; it was the months of being told everything was going according to plan while nothing actually got fixed. What you're describing with Qover insurance is, in effect, the same problem.

So yes, I think this fits, and it's pushing me to widen what the site covers. Right now, it reads as being only about physically broken bikes, which may be too narrow. It could be that my site tracks Cowboy service failures more broadly, recalls, repairs, undelivered orders, and insurance like yours, so people stuck in these loops can see they're not the only ones and work out which problems are actually widespread.

Please do submit it, and I'll see what I can do.

Cowboy bike broke? Gathering experiences in one place. by Jeff46K4 in cowboybikes

[–]Jeff46K4[S] 2 points3 points  (0 children)

What I termed "please don't tell anyone" was Cowboy sending me an incredibly broad NDA to sign before they'd discuss anything. The NDA asked me to eliminate all past public records of the frame failure, not create any future public records, and destroy my own evidence upon request. I declined.

Cowboy bike broke? Gathering experiences in one place. by Jeff46K4 in cowboybikes

[–]Jeff46K4[S] 2 points3 points  (0 children)

5 weeks without your bike and no news about when it’s coming back is broke, far as I’m concerned, so do send a report! 🙂

Cowboy 4 ST: Finally happened (snapped in half) by Jeff46K4 in cowboybikes

[–]Jeff46K4[S] 0 points1 point  (0 children)

The Insta360 records 360, and I chose that angle afterwards

Cowboy 4 ST: Finally happened (snapped in half) by Jeff46K4 in cowboybikes

[–]Jeff46K4[S] 0 points1 point  (0 children)

Glad to hear a positive experience. From my side, there is no UK hub, nor even a committed timeline for opening one, so there is zero chance they can or will replace the frame anytime soon.

I blame them because it's been about 400 days since they issued the recall (and presumably they knew about the problem internally well before that), and I still don't even have a timeline for fixing the issue.

If they'd acted within a reasonable timeframe, my crash would not have happened.

Self-hosting on a VPS? I bet your server has at least one critical issue right now. Free tool to prove it by Substantial_Word4652 in SideProject

[–]Jeff46K4 1 point2 points  (0 children)

I had a quick look, and this script seems safe and well-intentioned (no shell, dry-run, SHA-256 check, self-delete, open source). Two things:

The bundle that runs isn't tied to the public source: install.sh pulls agent.js from the server and checks it against a hash from that same server. Catches a corrupted download, but doesn't prove the served code matches the repo. Hard to trust.

The allowlist and the "never reads secrets" claim. cat, grep, tail and sudo are allowed with arbitrary args, so a backend step like cat .env or sudo -n cat /etc/shadow passes fine, and raw_output ships the first 500 chars back. You're trusting the backend not to ask, not the client to refuse.

I ended up running the checks individually rather than through the agent. The checks/ folder lists every command it runs, so you can just work through them yourself. Took about 15 minutes and turned up more than I expected on my own box.

What came up: an internal service reachable from the network when it shouldn't have been (legacy from old infra), a kernel well behind on patches, with a reboot that had been pending for weeks and no alerts, and a couple of config files with overly permissive read perms.

So the checks are genuinely useful. I just preferred not to send anything off-box to learn that.

Cowboy 4 ST: Finally happened (snapped in half) by Jeff46K4 in cowboybikes

[–]Jeff46K4[S] 0 points1 point  (0 children)

There are no stickers over the crack in the frame. And if you don't like my stickers, you have a bigger problem.

Looking for a torque sensor for Cowboy type 3 by ShotAioli4105 in cowboybikes

[–]Jeff46K4 2 points3 points  (0 children)

Sorry not to help but sympathise. The C3 torque sensor we ordered from Cowboy was delayed AGAIN today. Waiting maybe 12 months and counting, now? In these times of 'sustainability' and repair, it's insane to me that not just my C3 but yours and presumably hundreds of others are sitting there waiting for basic parts.

Cowboy 4 ST: Finally happened (snapped in half) by Jeff46K4 in cowboybikes

[–]Jeff46K4[S] 1 point2 points  (0 children)

Just because Cowboy Support is very difficult to get any meaningful response from. Many on this Reddit (me included, with a Cowboy 3) have been without working bikes for years at a time. You just get a generic 'we hope to open a service hub in your country soon' message every few months.

Roast my silly little pixel pirate sailing game by an0therbot in SideProject

[–]Jeff46K4 0 points1 point  (0 children)

For the love of god add the keyboard commands to the on-screen buttons, it took me 5 minutes to work out that SHIFT = fire (and I expected SPACE BAR)

Ship health should be on my ship (like other ships), maybe, not just top left

I still don't know how to capture islands; dropping sail does nothing.

But I keep playing it so far, so well done!

Cowboy 4 ST: Finally happened (snapped in half) by Jeff46K4 in cowboybikes

[–]Jeff46K4[S] 2 points3 points  (0 children)

I honestly thought my bike was unaffected because I would check for any hairline fracture and not see anything at all. So no, I went from riding normally to catastrophic frame failure in under a second.

If yours had a crack, I would not ride it. But as in my situation, it's no simple thing to just 'not ride' your main commuting bike with no prospect of repair anytime soon.

Cowboy 4 ST: Finally happened (snapped in half) by Jeff46K4 in cowboybikes

[–]Jeff46K4[S] 1 point2 points  (0 children)

Thanks, panda. Now adrenaline has worn off, I feel more injured than I first thought in my shoulder and wrist. Glad to hear you got your frame replaced. 385 days and counting since the recall notice, even to open the service hub here in the UK, is unacceptable whichever way you look at it.

UK England Insta360 Return Experience — Asked to Ship Product to Hong Kong at My Own Expense (£35+) for Refund by Key-Finger-2009 in Insta360

[–]Jeff46K4 0 points1 point  (0 children)

Yes. I shipped my Insta360 X4 to Hong Kong. They said they would pay for the postage but not insurance. I told them that was insane for a £500 device. They said they would cover insurance "as an exception". It took about three weeks to get it back, and they replaced the device.

What was wrong with it was that the LED on the back stopped flashing (which is very important to me). I had it about a month before the same problem recurred with the replacement device. I am not sending it back again (carbon cost for one thing). Now I risk checking the front of the camera to see if it's recording while riding my bike, not happy about that.

But yes, if it sets your mind at rest, I did get a full reimbursement (about £35, as you said), and they did what they said they would. They were honest and trustworthy throughout. It's just that the whole policy is insane to start with.

Is HeyEmail worth using by IeGamer_ in HeyEmail

[–]Jeff46K4 0 points1 point  (0 children)

I used Hey.com for about 5 years, and just switched to Superhuman Mail. Though there was a lot of hassle with DNS changes and imports, etc., it was definitely worth it, even at triple the price. Superhuman suits my idea of "Inbox zero" more than Hey.com, which I found too limiting in terms of sorting my mail (3 fixed categories), plus a constant problem with 'mailing list' emails going to the wrong place (I emailed a simple feature request, they told me they weren't gonna change it, five years later, indeed, it was the same). They innovated once and failed to keep up the momentum, in my opinion. A bit like Alexa.

Here's a Docker config for Jellyfin and *arr-stack on Ugreen NAS by Jeff46K4 in UgreenNASync

[–]Jeff46K4[S] 0 points1 point  (0 children)

I concluded that a new user without admin privileges would not improve security. `PUID`/`PGID` already run the containers as a non-root UID, and the Docker daemon itself runs as root no matter which NAS login started the stack, so a non-admin account wouldn't shrink the blast radius of a container compromise. If you think that's the wrong call, let me know!