Ellie Algase

Another suggestion: implement an automatic, and idiot proof, updater (automatically downloads update from GitHub, installs it, and relaunches the program.

@Fabian42 Yes. The movie is encrypted with some sort of DRM. A good movie to try is [https://www.youtube.com/watch?v=s7_qI6_mIXc](https://www.youtube.com/watch?v=s7_qI6_mIXc), as it is free to watch.

Doesn't appear to be much research. It should probably be easy to reverse engineer though.

Unfortunately, nope, that's the same experience everyone faces here.

Understandable, but I think most people would want this feature. At least, incoming `like` objects should be accepted (and added to posts as `announce` objects are) instead of being ignored.

If likes are `as:Public`, like they currently are, they should go into the outbox and be properly federated.

It's requesting two things: * Handle incoming `Like` objects targeting remote posts by attaching them, not discarding them * Send `Like` objects on public posts to all of a user's...

> frankly it's not anyone's business what i choose to Like, except for the person who owns the object. Then why is it labelled `as:Public`?

Favorite a public post. That `like` is `as:Public`, anyone on your server or the server where the post originated can see it.

That might work, having the instance's silences be added to that list as "default hidden domains" or the like.