Mixed feedback on my post about X, mostly good. I’m going to hold the rollout another week so I can consider everything. No deployments yet.
Also there’s some confusion about whether all paid Micro.blog subscriptions send money to X. Nope, this would be a change only for users who want to use X.
@scripting.com They charge $0.015 per tweet. So if someone wanted to enable this feature, we’d essentially use a small part of their subscription to pay for it, with a limit on the number of tweets per month. This keeps things simple. Users who ignore the feature are not affected.
@manton I don’t understand. You’re not literally going to have a separate account for everyone who wants to tweet. So the payments to X will come out of your general operating funds. Which means they aren’t available for anything else. I hope I’ve got that wrong.
@jeremycherfas The important thing to me was that if someone doesn’t enable it, they know that none of their subscription will be used for X. Tweet counts are tracked per month, per user. If literally no one enables it, there’s no cost. Similar to if someone disables AI on their account, their account is never used to rack up charges to an AI provider. The only cleaner way to handle it would be to charge each user a variable amount per month extra, which seems too complicated for everyone.
