We'll now throw errors when doing POST /api/v1/push/subscription if the endpoint is an invalid URL, or if the keys values can't be used to encrypt a message.
That prevents you from registering a push subscription that just wouldn't work. We previously lacked input validation here.
@newsmast is the Social Media Feed (@socialmedia) just boosting everything under the mastodon hashtag?
It might be wise to filter out posts also tagged with #MastoDev and #MastoAPI since these are intended for developer audiences rather than the general public.
Question: a desktop software that queries the public Mastodon API to provide an overview of an instance (about page, rules, admin account, user count, moderated instances) – would that have any scraping / block circumventing concerns?
This would be without access token and such, so authorised fetch, disallow public API access, etc. would prevent fetching any information. And all of this is publicly available information that can be queried from /api/v1/instance without requiring authorization (by default). Basically, nothing you couldn't find by going to instance.example/about.
I wonder how hard it would be to write a simple #MastoAPI boost bot? 🤔
You'd basically just need an API token for your user, and a way to target a specific account you're following. Upon seeing a new status from that account, your own account would boost it.
If this gets added in, this will bring in Misskey (and #Sharkey too!) a lot more compatible third-party clients.. :gyate_patchouli_wow: Thus the issue of lack of clients in Misskey is workarounded and we may not need the #Mastodon#API (aka #MastoAPI) after all... :sagume_think:
This also AFAIK makes Misskey the first mainstream #fediverse software out there to support Micropub; earlier than Mastodon! :SuikaWOW: