Conversation

Notices

1. Embed this notice
    (mint@ryona.agency)'s status on Wednesday, 24-Aug-2022 05:52:02 JST 

   • Alex Gleason
   @alex are you going to fully rewrite software name in nodeinfo in your Soapbox/Rebased? I know Akkoma tranny did this and it broke compatibility with certain applications, so I'm hopeful you'd be more considerate on such matters.
   • Marcin Mikołajczak likes this.
   • Embed this notice
     Alex Gleason (alex@gleasonator.com)'s status on Wednesday, 24-Aug-2022 05:52:00 JST Alex Gleason

     in reply to
     No.
     Marcin Mikołajczak likes this.
   • Embed this notice
     Marcin Mikołajczak (mkljczk@pl.fediverse.pl)'s status on Friday, 26-Aug-2022 02:28:48 JST Marcin Mikołajczak

     in reply to

     • Alex Gleason
     Well… it got changed in api/v1/instance and it breaks compatibility with soapbox-fe
   • Embed this notice
     Alex Gleason (alex@gleasonator.com)'s status on Friday, 26-Aug-2022 03:54:24 JST Alex Gleason

     in reply to

     • Marcin Mikołajczak
     Oh shit, that was not intentional.
     Marcin Mikołajczak likes this.
   • Embed this notice
     Alex Gleason (alex@gleasonator.com)'s status on Friday, 26-Aug-2022 04:04:04 JST Alex Gleason

     in reply to

     • Alex Gleason
     • Marcin Mikołajczak
     Plz review: https://gitlab.com/soapbox-pub/rebased/-/merge_requests/167
   • Embed this notice
     Marcin Mikołajczak (mkljczk@pl.fediverse.pl)'s status on Friday, 26-Aug-2022 05:47:27 JST Marcin Mikołajczak

     in reply to

     • ew
     • Alex Gleason

     Why would you fix it on soapbox side if it’s akkoma intentionally breaking compatibility? I think you should submit a PR to akkoma

     Alex Gleason likes this.
   • Embed this notice
     ew (e@masochi.st)'s status on Friday, 26-Aug-2022 05:47:29 JST ew

     in reply to

     • Alex Gleason
     • Marcin Mikołajczak
     @mkljczk @alex @mint I made a PR to fix that awhile back for akkoma
   • Embed this notice
      (mint@ryona.agency)'s status on Friday, 26-Aug-2022 10:05:25 JST 

     in reply to

     • ew
     • Alex Gleason
     • Marcin Mikołajczak
     @mkljczk @alex @e Akkoma devs would just refuse communication since everyone outside their hugbox is le problematic. Plus I'm under the impression Soapbox is supposed to be more or less MastoAPI compatible, and not having to depend on software strings might be good for compatibility with other servers like GoToSocial and whatever Ew and Moon are developing right now.
     Alex Gleason likes this.
   • Embed this notice
     Alex Gleason (alex@gleasonator.com)'s status on Friday, 26-Aug-2022 10:10:48 JST Alex Gleason

     in reply to

     • ew
     • Marcin Mikołajczak

     Instance versions are like user-agents. Chrome’s looks like this:

     Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/72.0.3626.121 Safari/537.36

     If you’re really Pleroma-compatible, write that in the version strong. But for a new backend, most likely you aren’t.

     So if you make your own backend from scratch, we’ll add it to Soapbox. What Akkoma did is either an ego thing or an oversight (I made the same mistake by accident).

     Marcin Mikołajczak likes this.
   • Embed this notice
     ew (e@masochi.st)'s status on Friday, 26-Aug-2022 10:10:50 JST ew

     in reply to

     • Alex Gleason
     • Marcin Mikołajczak
     @mkljczk @alex @mint soapbox-fe already supports feature flagging for truth-social, mastodon, and a number of other backends. I personally think it's fine for akkoma to rewrite their nodeinfo/instance info.
     
     I'm making my own backend from scratch, do I have to write pleroma as the nodeinfo descriptor?