abochmann
abochmann
I'm running into the same problem with my copy. As far as I can see, it doesn't fetch your version of sapper, though I couldn't say why.
Ah ok. Apparently when there is a version of sapper in the cache at `~/.cache/yarn/v6/npm-sapper-0.27.12`, it will just copy over that one instead of fetching your fork. Deleting that directory...
The documentation hasn't been updated with the correct syntax yet,
@zachflanders thanks for identifying the cause, and sorry I didn't write I was using a Chromium browser. Is it ok to close the issue?
I see the same. The timestamp goes from 24:59 to 01:00  Browser is Vivaldi (Chromium 106), and configured to use the system time format (Windows, German, GMT+1).
@ineffyble This seems to be a Chromium problem - the timestamp looks fine in Firefox on the desktop and mobile. This toot can be used as a test case (currently...
Also see #20070
> This was deliberately changed quite recently in response to user reports that the existing linking was confusing and causing accidental navigations away from their home instance. I'd again propose...
[edit] _Sorry, this post slightly deviates from the topic, but it seems these two changes - removing links from avatars and from the timestamp of a post - were driven...
I notice the behaviour is now also inconsistent between being logged in to an instance and the public web UI: When not logged in, clicking on the timestamp of a...