Conversation

Notices

1. Embed this notice
   HACK13 (hack13@cyberfurz.social)'s status on Monday, 26-Dec-2022 23:05:20 JST HACK13

   Since Mastodon/Pleroma/Akkoma all leverage Mastodon API I am able to pull their data with /api/v1/instance, but Misskey/Calckey uses different API standard... this is how I have gone about implementing Misskey API standards... still working through the code but this so far looks to be the way I will be handling the difference.

   • Embed this notice
     ThatOneCalculator :calcdumpy: :calckey: (thatonecalculator@stop.voring.me)'s status on Monday, 26-Dec-2022 23:05:16 JST ThatOneCalculator :calcdumpy: :calckey:

     in reply to

     @hack13@cyberfurz.social I'd do "misskey" || "calckey" in that if statement if you're getting that from nodeinfo...

   • Embed this notice
     HACK13 (hack13@cyberfurz.social)'s status on Monday, 26-Dec-2022 23:13:58 JST HACK13

     in reply to

     • ThatOneCalculator :calcdumpy: :calckey:

     @thatonecalculator Sadly because the verification step to verify the instance admin is wishing to be listed. We are going to be asking the user if their instance is using a Mastodon compatible API or Misskey compatible API. Because with the Misskey lack of "instance contact" we are going to be showing an additional field for Misskey compatible instances to put in their admin account username so we can hit the API to verify they are an admin then DM them a special link to confirm the listing.

     ThatOneCalculator :calcdumpy: :calckey: likes this.