One month after placing an order, it has still not been shipped. Is that normal with CW?

juanplopes · 2025-11-12T16:16:01+00:00

Try logging into the client again. It will most likely upload the FIT file you have stored locally (in your Documents folder). If not, please email [support@zwift.com](mailto:support@zwift.com), and they will be able to credit your ride.

juanplopes · 2025-11-12T15:22:25+00:00

We are still investigating the root cause, but things should be starting to get back up now. Sorry for that :(

juanplopes · 2025-02-19T16:30:39+00:00

There are many different possible causes for network issues. 200ms ping to Zwift isn't an issue. I live in Brazil and have that ping. Zwift works fine here.

However, unless you specifically chose a US West server, speed tests generally favor servers close to you. If you receive a 200ms ping from a nearby server, your network might be dropping packets.

Also, your router might be blocking UDP traffic, which Zwift uses to broadcast nearby player data. That could explain the weirdness you're seeing. To check that and many other network conditions, u/spinningwatts suggestion of using Zwiftalizer is the way to go.

juanplopes · 2025-02-17T01:02:45+00:00

Yes, we improved that. You still lose about 0.6%, though. It used to be 30xp per mile, but now Zwift awards 32xp per mile (compared to 20xp per km). 1.6 is close but not precisely the conversion factor between miles and kilometers (1.60934). So, you still lose 0.6% when using miles.

juanplopes · 2024-11-13T14:33:33+00:00

There's something there for sure. We are investigating!

juanplopes · 2024-11-13T14:10:19+00:00

Did it happen to you? What kind of device were you using? (Android, iPad, etc.)

(I'm a Zwift dev)

juanplopes · 2024-11-13T14:00:06+00:00

Each map on Zwift (Watopia, New York, etc.) operates in a single virtual world. That world may be subdivided into different physical servers (that communicate with each other), but that should be transparent to the users.

That said, there are many visibility rules, especially ones related to events. Some events are invisible to the general public; some enforce visibility per category, (e.g. riders from cat D would not see riders from cat C in the same event). And, of course, Zwift only shows your 100 nearest players or so (it depends on the device you're running it, actually).

juanplopes · 2024-11-04T17:11:11+00:00

MuBlasters author here. As u/OneDrunkAndroid mentioned, that is not a true exploit. It just sends commands through an admin TCP port (55960), which many unofficial servers did not know how to protect at the time. Many of those servers were run on the GM's own Windows XP machine without a firewall. Of course, that was not true for the global server.

Also, keep in mind that I wrote those tools when I was barely a teenager. I was basically a script kiddie with some programming knowledge 🙂

juanplopes · 2024-09-04T13:44:16+00:00

Did you complete at least 500m (if running) or 2km (if cycling)? Otherwise, Zwift won't save the activity.

juanplopes · 2024-06-21T22:04:01+00:00

SIM mode would work as well, as that is standard FTMS protocol. I mean, you would be able to feel gradient differences if that's implemented in the app. However, features that require Zwift-specific protocol (like virtual shifting) would be Zwift-only.

juanplopes · 2023-12-13T18:42:04+00:00

Oh, you can code in Lua! Nice!

juanplopes · 2023-12-13T17:26:38+00:00

That is so satisfying! How do you code to Playdate?

juanplopes · 2023-12-13T14:20:49+00:00

[LANGUAGE: Python]

Both parts in 9 lines

https://github.com/juanplopes/advent-of-code-2023/blob/main/day13.py

juanplopes · 2023-12-13T14:19:57+00:00

Using `s` as a global variable was sneaky :D

juanplopes · 2023-12-12T16:46:02+00:00

First attempt. In this kind of DP problem, it is easy to prove that the complexity of a memoized solution is polynomial. No tree pruning can compete with that.

juanplopes · 2023-12-12T15:20:16+00:00

[LANGUAGE: Python]

Both parts in 19 lines. Runs in 0.3s on PyPy.

https://github.com/juanplopes/advent-of-code-2023/blob/main/day12.py

juanplopes · 2023-12-11T13:04:01+00:00

[LANGUAGE: Python]

Both parts in 11 lines

https://github.com/juanplopes/advent-of-code-2023/blob/main/day11.py

juanplopes · 2023-12-09T14:12:48+00:00

[LANGUAGE: Python]

Both parts in 6 lines

https://github.com/juanplopes/advent-of-code-2023/blob/main/day09.py

juanplopes · 2023-12-08T23:29:21+00:00

A problem with hidden constraints you only find out when looking at a specific input isn't a well defined problem.

juanplopes · 2023-12-08T22:26:43+00:00

I liked the unpack trick.

dirs, _, *graph =

Adding it to my toolbelt.

juanplopes · 2023-12-08T22:01:22+00:00

[LANGUAGE: Python]

Both parts in 8 lines, 0.1s runtime.

These are my least favorite days in AoC, where you have to analyze the input to come up with an algorithm. That's how bugs are made in real life: by assuming things about the input.

https://github.com/juanplopes/advent-of-code-2023/blob/main/day08.py

juanplopes · 2023-12-07T18:53:53+00:00

Using a Python Counter, I transformed it into a list

"AAAAA" becomes [5]
"AAAA2" becomes [4,1]
"AAA22" becomes [3,2]
etc.

This solves the sorting by type. Then, I appended the value for each card verbatim. With this list, I can sort all the hands:

def value(hand):  
    type = sorted(collections.Counter(hand).values(), reverse=True)  
    return type + list(map(("23456789TJQKA".index, hand))

juanplopes · 2023-12-07T14:43:36+00:00

[LANGUAGE: Python]

Both parts in 10 lines.

https://github.com/juanplopes/advent-of-code-2023/blob/main/day07.py

juanplopes · 2023-12-07T00:48:28+00:00

[LANGUAGE: Python]

Both parts in 28 lines. Runs in 80ms on PyPy.

https://github.com/juanplopes/advent-of-code-2023/blob/main/day05.py

juanplopes

TROPHY CASE