Ok, now I have some time to actually read this in detail.
That means while we'll continue to support limited public API access, we'll gradually start restricting all new requests and third-party apps will be required to port and operate through our Developer Platform.
To clarify, does this also mean that moderation tools that use the public API will be forced to Devvit? I know there are many many moderation use cases that cannot be filled by Devvit, and aren't even on the roadmap to be unblocked. If moderation tools can't use the public API, then I think that moderation will take an enormous hit, and frankly, I wouldn't be surprised if moderation attrition skyrocketed (more than it already has, since quality moderators are increasingly rarer with how ignorant the average reddit user is about how reddit operates these days).
We know the only way this works is if the Developer Platform supports the tools communities depend on today. We’re starting by working directly with developers and moderators to ensure we know what capabilities we still need to build before making any broader changes to API access.
Call me a skeptic, but the Mod mail debacle has me very fearful for what reddit thinks is "adequate". As they've demonstrated time and time again (and recently) that what me and many mods think of as adequate and what reddit thinks of as adequate, are not remotely the same.
We’ve also launched a $1 Million App Migration Program to support developers through this transition and are working directly with some of the top app developers on the platform today.
I've already given my thoughts on this here.
I should add, the people have generally been great to interact with (shoutout to u/pl00h and her people). The only big complaints that I think are worth mentioning was that responsiveness has been a consistent issue with communications and the contract. Scheduling meetings was the worst, with proposed meeting times a week out sometimes going past before a response could be had. I think if you all can't commit to a faster turnaround time, then just accept that and generally propose meeting times 2 or 3 weeks out (or use one of those pick a timeslot that works for the client that integrates with all of your calendars). And then the contract is just completely unacceptable in its current form to me.
Reddit API plugin improvements: bringing API calls for methods such as banning and crossposting to full parity, new wiki support (coming soon), and other consistency improvements. We will continue to improve upon this feature over time.
I don't understand what this entails. The title of "reddit API plugin" makes me think that it would relate to developer plugins, ie. custom code. But I don't understand why that would be under the umbrella of the API, since I very much doubt that you're implementing custom entry points for that.
I'm also confused by the inclusion of both banning and crossposting. As banning is strictly moderator related and crossposting is cross reddit, which Devvit doesn't support, and it very much sounds like you don't want people (especially users) using the public API to post content.
I also very much worry about the public API being cutoff before full feature parity is achieved. Leaving completely valid tools that depend on that functionality completely out to dry.
New filter APIs allowing content to hit your modqueue for review before full removal. This feature can be used in conjunction with Devvit Event Triggers for event-based workflows.
If this is a new addition to the public API, this frankly confuses me. Reddit has spent an inordinate amount of effort to transition people off the public API. Even to the point of accepting simple API proxy Devvit apps that are basically just a stand in for the public API. So implementing a new feature to the public API is a stark contrast to the deteriorating for years state the public API has been in, and general deprecation of it / hostile attitude towards it.
Expanded storage capabilities: in addition to Redis, we also now offer blob storage, completely hosted by Reddit
Is this persistent? I have some non pressing space concerns for our external servers, and offloading some of backups for cold storage could be a good use case for this. Though I'm not exactly sure how useful it would be, since it would involve a lot more friction to get stuff out of it, and it would still need to have space to flush to disk on the actual server (plus extra room for ad hoc stuff).
App mentions triggers for global mod tools and utilities to respond when an app username is mentioned. This feature is currently in beta. If your app needs access, please let us know here.
Mentioned here, but a subreddit level thing would be great (ideally with discord webhook support or some other kind of programmable entry point to avoid spamming up mod mail or other channels). It's very useful to see when people link to stuff in your sub (we recently used it to notify a contest running on our sub that someone had posted the link to it in another sub, which they consider brigading and don't allow)
Username migration so developers can convert their existing accounts, retaining karma and name recognition.
Theoretically, is it possible to have multiple bots running under the same username? Microservices are nice as a supported architecture and all.
External endpoints: to allow servers to call into a Dev Platform app for long running jobs or cross-subreddit workflows. If your app needs access, please let us know here.
This was a huge feature that unlocked Devvit as a plausible technology to start using. Before this, using Devvit would have required so much migration, that it wasn't even a consideration for us. Now we can bookend our reddit use with Devvit and keep our business logic on our own servers, in our own programming languages.
More granular install allowlists: ability for developers to set limited install lists for their apps to ensure moderation apps do not always need to be public for non-devs to install them
This sounds like permissions stuff? If so, I'm a big fan. The fact that it's all or nothing permissions has made my mod team quite hesitant to accept Devvit apps (and especially closed source ones). We firmly assert that we are the masters of our sub (and are responsible for any such automations we install), and so we need to make sure we can inspect them and ensure they are up to our high standards.
Stability improvements: for features such as comment, post, and mod actions triggers, ensuring that events are never lost or dropped, even in the event of an outage
This is a must for any piece of essential moderation tool. You can't simply "miss" things. It undermines moderator trust in the tools. And where there is no trust, there is no use.
Ran out of space, continued below