@evan I have been in a situation where stored procedures were established by the DBA and consumers of the database used them like an API, so in that case, or if I was intending to provide this kind of "API", then yes. But if I'm developing software and I'm in control of the database, then no.
I find it's a bad code smell if a particular query occurs in more than one place in your app. So using this metric, stored procedures are an unnecessary level of indirection that can lead to obfuscation.
Mastodon server admins or other experts: What could potentially cause another instance to get a 401 error when attempting to POST to my instance's inbox?
The other instance was offline for a while, and I had subsequently "Purged" it using the option in the "Moderation/Federation" admin screen to try and correct this problem. It didn't work. The other instance seems to be federating normally with other instances -- just not mine.
@gotosocial Is there any way to convert a single-user Mastodon instance into a GoToSocial instance? Like, migrate the database, and use the existing key pair so I could use the same domain name and fediverse handle?
I set up my Mastodon before I knew about go to social, and I would love to have a less-resource-intensive instance.
@evan If, by "celebrating", you mean heading to the in-laws' cottage for probably the last time this year (kids' school and other commitments are now getting in the way), then hell yes. Otherwise, I guess it's just another long weekend.
I have an instance of go-to-social that has been off for a long time and had been "expired" by most other instances. Even my own Mastodon instance doesn't recognize it (can't even search for my account on it).
Is there any way to salvage it, or is it just done?
Haligonian, dad, software developer, home-automation enthusiast, cyclist, coffee lover, nerd#fedi22 so I can be indexed on https://fediverse.infohttps://justmytoots.com/@steve@social.dinn.ca