@julian@fietkau.social cover
@julian@fietkau.social avatar

julian

@julian@fietkau.social

Human-computer interaction #HCI, computer science & programming, home server & self-hosting, games and other fun stuff.

Increasingly into making tools for the fediverse: FediRoster, Pinhole, more to come(?). See https://fietkau.software/tag/fediverse for project info and downloads. If you do HCI-related research, check out https://directory.hci.social.

He/him. Posting mostly in English, but you might see the occasional German boost.

This profile is from a federated server and may be incomplete. For a complete list of posts, browse on the original instance.

hongminhee , to random
@hongminhee@todon.eu avatar

The max_id, since_id, and min_id parameters in 's Timeline API assume that the post ID is a sortable number. (Is this correct?) , the implementation I'm building, uses UUIDs for post IDs internally, so I'm stuck on how to implement a Mastodon-compatible API.

https://docs.joinmastodon.org/methods/timelines/

julian ,
@julian@fietkau.social avatar

@hongminhee Does it assume that? I don't see it clearly stated in the documentation that the IDs themselves need to be numerically sortable, just that, when given a specific ID, the server needs to be able to retrieve newer or older posts based on it.

Of course sortable snowflake IDs make implementing this easier on the server side.

  • All
  • Subscribed
  • Moderated
  • Favorites
  • •
  • random
  • test
  • worldmews
  • mews
  • All magazines
    •