In the language of Polandball comics, it means "give land/territory".
"Gib" is taken from the German imperative for "give!"
Best theory is that "clay" as "land" originates from a bad machine translation.
It seems somene created a Wiki that covers these terms: https://www.polandballwiki.com/wiki/Terminology#Clay
You actually get a say in how that money is spent, whereas if you donate to developers directly then they decide …
You get to be involved in a "steering committee" of sorts for that project,
The project itself always decides, unless you fork the project and do your own thing. You can wave a carrot in front of them (if you do X then you get $Y), but the relevant factor is going to be the size of the carrot $Y, not directly the "collective bargaining" via that platform. How would your platform facilitate finding a stronger negotiation position?
this membership organization is incorporated as a non-profit, whereas the software project you're supporting may not be
It sounds like you may have discovered the "fiscal sponsor" concept. There are a couple of nonprofits already offering such services, such as the Software Freedom Conservancy or OpenCollective. The foundations like Linux Foundation, Apache Foundation, or Eclipse Foundation also come to mind.
However, for all of these the project decides to join a host. Foundations can't just annex projects.
On the other hand, the GDPR's concept of "personal data" is extremely broad, much more so than the US concept of PII. Personal data is any information relating to an identifiable person. Pseudonymous info is still personal under this definition. Online usernames or social media handles are identifiers, and any linked info (e.g. posts, comments, likes) is personal data as well.
So Lemmy and other Fediverse stuff is well within the GDPR's material scope.
However, the GDPR's "right to erasure /to be forgotten" is more nuanced. It doesn't quite always apply (though usually does). OP very likely has the right to request deletion from individual instances.
Posts have been published through federation. The GDPR anticipates this (I think in Art 17(2)): if personal data has been made public by the data controller, and erasure is requested, then the data controller is obliged to take reasonable steps to notify other controllers of this.
The ActivityPub protocol has built-in support for sending out such deletion notifications, and last time I checked Lemmy implements this. Of course the receiving instance might not honor this, but that's outside of the responsibility of the initial data controller.
While I'm not entirely convinced that everything here is 100% compliant, federation is less of a compliance issue than it might seem.
Synology's DSM has built-in MFA support, though it also has some features for external identity management. I don't think Keycloak and so on would be compatible though.
C++ does have the problem that references are not objects, which introduces many subtle issues. For example, you cannot use a type like std::vector<int&>, so that templated code will often have to invoke std::remove_reference<T> and so on. Rust opts for a more consistent data model, but then introduces auto-deref (and the Deref trait) to get about the same usability C++ has with references and operator->. Note that C++ will implicitly chain operator-> calls until a plain pointer is reached, whereas Rust will stop dereferencing once a type with a matching method/field is found. Having deep knowledge of both languages, I'm not convinced that C++ features "straightforward consistency" here…
Well, it's about Peter Thiel, who also founded the Palantir surveillance technology company. As a source for his involvement with Brave, Wikipedia cites this TechCrunch article, which mentions funding from Thiel's "Founders Fund".
I'd rather criticize Brave for other reasons though, like being led by Brendan Eich or supporting crypto.