But why not use a proper builder pattern in that case?

But a scope adds a nesting level which adds a lot more visual clutter.

The first one won’t work either for private fields.

Why not just a let app = app; line after the let mut app = ...; one?

In 99% of those cases you would want it to resolve .. components though.

Especially when all the workarounds to make it barely usable from Mastodon spill over into Lemmy in the form of bots posting weird hashtags or headlines being full of hashtags,…

It is about as common as using a database server for content though to use something like ES, Solr or similar software for search.

I don’t really see the point in forking a project like Mastodon unless you are already deeply involved with its development. It doesn’t do enough that you couldn’t rewrite it better (as in in a way you understand better and with lessons from the original taken into account) in the time it would take you to fully understand all the details of the existing code base.

You included the . at the end of the sentence in the URL so it doesn’t work properly.

Seems quite reasonable to remove illegal communities given how Lemmy works with the caching of all content locally. There is just a significant legal risk for the instance operators involved here.

!article_interop@lemmy.ml

We here on Lemmy don’t have great interoperability with the microblog side of the fediverse, so we’re less likely to see Threads activity.

I for one would be fine with just defederating from the entire microblogging world, Fediverse or otherwise. In fact, just cut them out of the internet completely. They are essentially the text equivalent of the sound bite and actively harm public discourse.

The proposal fails to sufficiently motivate why existing protocols like OpenId Connect can’t be used given that trusting the user’s home instance seems necessary with this protocol too. The name also is confusingly close to WebAuthn.

Does Box<[T]> have the relevant trait implementations to be used in all the places where people misuse Vec?

It might be interesting to analyse which of the Hetzner IPs are in which data center.

I understood its suggestion as limiting the new notification only to people who interacted with the original post.

I am not sure this will work as intended since part of the problem is that most of the lurkers who read the original and never interacted with it beyond that have already moved on to something entirely different by the time any mistake admitting, forgiveness,… happens.

I would add that factually wrong or misleading posts (e.g. that one the other day with an inflation percentage that didn’t even match the other numbers in the same graph) are a good reason for downvotes too.

It requires the information who upvoted and downvoted what, I don’t think that is available to the client, is it?

A lot of legal issues get worse though if they occur as part of a paid service.