Conversation

Notices

1. tateisu​ :force:​:r_9a: (tateisu@mastodon.juggler.jp)'s status on Wednesday, 16-Jan-2019 14:24:32 JST tateisu​ :force:​:r_9a:

   • Vale@ganbara.nai

   @valerauko do you think these has AP object id? notification,favourite,boost,etc…
   each FSNS has internal ids. mastodon uses 64bit int, Misskey uses MongoDB's Object ID.

   • tateisu​ :force:​:r_9a: (tateisu@mastodon.juggler.jp)'s status on Wednesday, 16-Jan-2019 14:33:25 JST tateisu​ :force:​:r_9a:

     • Vale@ganbara.nai

     @valerauko Internal ID is unique in each server, so its handling is not equivalent to URI. URI is unique in all server.

   • tateisu​ :force:​:r_9a: (tateisu@mastodon.juggler.jp)'s status on Wednesday, 16-Jan-2019 15:14:11 JST tateisu​ :force:​:r_9a:

     • Vale@ganbara.nai

     @valerauko pleroma said mastodon compatible in early development. but they will drop it without acknowledgement to app devs. most mastodon client parse id as number because mastodon uses numeric sort order.
     Misskey uses it own api that use string id and string sort order.

   • tateisu​ :force:​:r_9a: (tateisu@mastodon.juggler.jp)'s status on Wednesday, 16-Jan-2019 16:07:15 JST tateisu​ :force:​:r_9a:

     • Vale@ganbara.nai

     @valerauko it's workaround for JSON's long presision. it is long int and the sort order is numeric.