@Weirdmusic if it's anything like Twitter (and it seems the same playbook is being used) then the only impact will be on the creators of the 3rd party apps (both by the end of their subscription revenue and more critically people requesting refunds on existing subscriptions). The company "owns" the infrastructure containing the content so assuming the integrity of the backups isn't breached then no amount of scrubbing with remove it (although EU legislation may claim some of it). Therefore it's only a question of time before things return to "normal" and the IPO can proceed. Reputational damage is the only thing that will really have a chance of derailing it.

@IncognitoWolf

You need to look at https://codeberg.org/Kbin/kbin-core

Whether of not they are case sensitive they shouldn't be forced to lowercase as that would be an accessibility issue.

@nemrod if you on the magazine's page then the subscribe is also on the sidebar.

@nydas from a technical perspective you could need a program that could interpret the JSON and pick out the bits necessary to reformat it into a post for kbin. The question of whether this would remain as an option after the API changes is left to the reader :-)

If you were doing this solely for your own content then there probably wouldn't a problem doing that but would you have permission to also include contributions from others?

The concept seems similar to the bridges between Twitter and Mastodon and I think that was generally thought of as a bad idea, and a number of places blocked it.