Claire

Writing a simple C program confirms that for some reason, stdout is set to non-blocking on Ruby 3.0, but not on Ruby 2.7: ```c #include #include #include int main(void) {...

In Mastodon, we ended up checking whether we are in a transaction, if so queue the notifications, otherwise send them right away. The relevant pieces of code look like this:...

I believe the following change addresses the issue, but I have not tested this under any other version of Rails: ```diff diff --git a/lib/devise/rails/routes.rb b/lib/devise/rails/routes.rb index 004b9857..c79abb59 100644 --- a/lib/devise/rails/routes.rb...

Superseded by #927

@ShadowJonathan encrypted messages haven't been fully implemented in any client yet, and we're still missing some specifications on the format of the messages themselves, but the encryption protocol is mostly...

The easiest way to handle that information is probably as a property on the actor object being suspended, with remote instances being notified via an `Update` just like for any...

@evanp I like this idea, the recipient just have to make sure the actor is authoritative to suspend the object, and I don't think there is any specification for that.

@nightpool I really dislike this particular idea, though. It still needs to be signed by the actor (the minor drawback I was referring to), and it causes deletion of every...

@nightpool I disagree. Deleting everything is totally reasonable when getting a `Delete` Activity. Deleting an actor is also a legitimate operation. But it's really not what we want if the...

@evanp hm, is object.provider specified? I can't find it. Also, yeah, right, we could check the object, but I understood that suggestion as replacing a “suspended” property, which would have...