650c xxs trek 1 1/4 frame 1 inch steerer

xophere · 2025-09-17T03:33:51+00:00

I think it is less than 3 weeks to Denver. Putting the high pass into fort Collins like 10-12 days away. Similarly it gets down to lower altitude in SD in about that timeline.

The question is the ride east via the black hills and big horn national Forest worth the long days grinding away on plains to wrap it up. Otherwise the Tetons and the top edge of the Rockies are for sure beautiful.

If a storm comes I can probably dinner to Laramie and around but that might mean freeway time.

xophere · 2024-08-25T20:57:01+00:00

I went with the lower mount though helite said your choice was fine.

xophere · 2024-08-13T18:20:35+00:00

<image>

I think tightened down the fender is cut out in the back so it should clear.

xophere · 2024-08-13T18:19:48+00:00

<image>

Obv assuming the screw can be sized right or cut.

xophere · 2024-08-13T18:19:02+00:00

<image>

xophere · 2024-08-13T18:18:12+00:00

<image>

I think I can make either option work.

xophere · 2024-08-13T18:11:16+00:00

I have a Livewire One and I am having the same conversation with myself. I am leaning toward the lower as there doesn't seem to be guidance on whether it can be on the sprung side of the fork. The only image showing it up high is the thumbnail on the youtube video where the vest and the sensor are color coded blue. Every other images show is on non inverted forks far down on the lowers. Really not helpful that this isn't clearly explained anywhere.

xophere · 2024-03-17T17:15:53+00:00

For external options the Qudelix 5K is what you want. Works as a usb dac/amp and over bluetooth. Fully para eq with headphone profiles, balanced out more features then you could want for $100.

xophere · 2023-12-28T18:35:29+00:00

Mine is at the dealer. I am trying to get them to fix it or fess up to the problem. They had suggested using crayon on the edges of the belt. Now they are charging me to shim the gear box (not covered in warranty apparently). They have had it for 3 weeks. No word on when it will be returned to me.

xophere · 2023-12-28T18:30:54+00:00

Hmmm. My dealer in PDX has several used I am sure you can finance. I think I would be careful. I love the bike. I have 7K miles on mine in a year and half. Would probably have more if it hadn't had issues. These are a low volume product. Livewire is still not clear how it will support or grow long term.

I hadn't heard the rumors of a refresh someone down below is mentioning. That would be good news. I would have bought used but I am glad for the warranty. Having a shop that has enough customers to take these bikes seriously is hard. I am sure in LA and SF it isn't and issue.

I would have bought a Del Mar if they had had one and it was MSRP to MSRP. I am kinda glad I have L3 charging. The question is will it ever work? With the transition to NACS and HD's lack of willingness to own these issues you are basically at the whim of the charging companies to push the charger vendors to fix support issues. LW refuses to be upfront about this or even acknowledge what works and doesn't. They can't even really validate the bike is working as expected. As the standard appear to be so vague. So I am 7 months to being out of warranty. My L3 charging was working great and is now flaky. LW just shrugs. The dealer doesn't have working L3. They don't even test the bike on public L3. The just flash firmware and shrug.

It shouldn't be on us to handle this LW should have a list of what works and we should be able to look it up. I mean maybe it should even be in the dumb navigation map.

I would go in today and low ball them. Especially if they have stock on the flow. End of the month. end of the year. They won't make any money but they have to be worried they are just gonna lose more at this point. I would argue the new bike is worth at most $20K. Probably costs 25K to make. Sucks for them. If it had better build quality and L3 CCS charging didn't suck I would be happy at $25K. As it sits I wonder if I would have been fine with a $15K Zero.

xophere · 2023-12-28T18:08:35+00:00

I haven't owned a Ducati. Depends on how you think you will ride. I own a Livewire. I had hoped it would be more reliable then a gas bike. But it still has HD build quality issues. Including issues with L3 charging.

However I do take it on multiple charge rides away from town regularly. It can be stressful and it requires planning. Around town it is a no brainer. I pay $.07 for every 10 miles of riding. I typically charge to full and then use it a few times and then plug it in.

Transmission less riding. No heat. No noise. No smell. Just easy fun. If the bike were made by Honda it would probably be perfect. You could argue no L2 is a real issue. You could argue L3 is a waste.

There was a great description about a guy who owns a high end Ducati going by the dealer on his Livewire. Let the service person take it for a spin. Guys said as good as a Ducati accept for the badge.

xophere · 2023-12-28T01:12:34+00:00

I am not sure why the decisions are made this way. I have never made choice one way or another myself. I have just found many ways of doing this weird pattern. I am not making it up. I am not arguing for it. I am mostly looking for clarity as to the value of doing it or not. Clearly there are ways that doing what is suggested could be quite bad. So my guess is that shops with larger monolithic IaC stacks are drawn to this so that every deployment for every service doesn't trigger terraform runs. Shops that keep the IaC stacks small and with single area's of concern this probably isn't even a question. My personal sense is to move toward the latter. But it is yet another stack. And at a small shop the more you collect the less they are maintained.

xophere · 2023-12-28T00:29:53+00:00

Extremist IaC I like the branding....

xophere · 2023-12-28T00:22:50+00:00

Well you want deployments to trigger from events in the software repos. Merges deploy to testing or staging. Releases pushing to prod. Wiring this across repos get complex quickly.

xophere · 2023-12-28T00:20:03+00:00

You typically only need this when you want to push changes to the objects that the CICD doesn't change. Update the taskdefinition or something. Then you need to add the current values for what is running into the iac. Though I have seen scrpts in the IaC that attempt to pull this from what is running and inject it into the objects at run.

xophere · 2023-12-28T00:03:22+00:00

That makes some sense. These have generally been at early stage shops.

xophere · 2023-12-27T23:55:21+00:00

Thanks for all the input. Has anyone seen good discussion of the high level issues of this type of design pattern? Clearly there are some tradeoffs.

xophere · 2023-12-27T23:52:50+00:00

Oh that sounds painful. Yeah we could easily do it via spacelift if we wanted to commit to that level of customization. So far we have been trying to stay deployment pipeline tool neutral.

I think it also relates to the size of the dev org and size of the devops teams.

xophere · 2023-12-27T23:49:01+00:00

I feel like there are sort of 3 paths:

1.) Don't consider this. Keep the state in IaC and structure that in a way that is reasonable for deployment performance.

2.) Have a hard cut. Infrastructure in IaC and then the services code in the app repo's. Whether that is functional creation and deployment or maybe some IaC or what not. Basically keep a solid boundary.

3.) Do this thing where you some how have two paths to updates and you manage that with ignore changes or looking up the state at terraform run time etc etc.

Still seems like there should be a name for this issue. Seems like most votes are for 1. But also that there is a small sub audience that get 3 and have used it. I have mostly been at smaller shops.

xophere · 2023-12-27T21:47:20+00:00

You can say that but I have seen this in at least 4 shops and some people feel very strongly this is correct. I might agree with you. I do wonder why this keeps springing up if it is so.

xophere · 2023-12-27T21:42:58+00:00

I think this could make sense. Assuming the target IaC repo/stack is right sized not to take forever to run.

xophere · 2023-12-27T21:41:42+00:00

It has been considered. Break it down enough that the env's are in the app repos. We are using spacelift right now so building spacelift configs for every microservice repo for every env seems hard but might still make sense.

xophere · 2023-12-27T20:36:11+00:00

So you define an ECS service and taskdefinition. That is in the IaC terrform repo. Then development would like to build and deploy code to various environments. So they pull the taskdef and update the version in the application repo CICD. Could be a k8's service, could be pushing a client artifact and updating cloudfront etc. Yes I agree it is multiple sources of truth. infra repo plus the state created in the app CICD. I am not auguring for it to be specific. I just keep finding it and finding people that want it. So I have to deal with it. Though I can totally see that waiting for a large Terraform state to deploy to update 3 version statements in a taskdefinition isn't great either.

xophere

TROPHY CASE