Commit Graph
9 Commits
Author SHA1 Message Date
Xyphyn f493f19c60 misc: add settings pages 2023-08-13 13:00:00 -07:00
Xyphyn 7e76b1684c feat: add community creation 2023-08-13 12:09:53 -07:00
Xyphyn 85a405b91f fix: community avatar shrinking 2023-08-09 16:22:25 -07:00
Xyphyn 87612d6507 feat: switch to a string instead of enum 2023-08-02 14:22:27 -07:00
Xyphyn 2da415b670 feat: switch to new account system 2023-08-01 13:00:06 -07:00
Xyphyn 13a4b06e41 misc: add buttons for 0 communities 2023-07-31 13:21:33 -07:00
Xyphyn 62baf475b6 design: tweak design 2023-07-30 14:44:43 -07:00
Thomas J Faughnan Jr 34c712c01c fix: parse date strings as UTC
For posts, comments, and other objects, the `published` attribute is a
string containing an ISO 8601 timestamp. This timestamp is UTC, though
it is not explicit in the string's contents. When the `Date` constructor
is used on such strings, they are parsed as though they are local
timestamps. According to [1]:

> When the time zone offset is absent, date-only forms are
> interpreted as a UTC time and date-time forms are interpreted as local
> time. This is due to a historical spec error that was not consistent
> with ISO 8601 but could not be changed due to web
> compatibility.

This patch explicitly appends a 'Z' to the `published` string when it is
used as the argument to the `Date` constructor.

[1]: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Date
2023-07-28 20:02:01 -04:00
Xyphyn 1dd179d636 feat: Add search function 2023-07-26 11:39:54 -07:00