MagicalVagina

I'm only using the hosted version, it works. I do have a separate gitlab-runner in GCP at the moment though that is working fine.
If something doesn't work for you I suggest creating a ticket?

All of what you said seems completely doable to me.

Primarily I want it to comment/annotate changes so peer review focusses on logic and warnings are clear.

You can. See https://docs.gitlab.com/ee/ci/variables/predefined_variables.html

CI_PIPELINE_SOURCE

How the pipeline was triggered. Can be push, web, schedule, api, external, chat, webide, merge_request_event, external_pull_request_event, parent_pipeline, trigger, or pipeline

You have full access to the API and can do whatever you want in the MR too.

I want the ability to specify multiple reusable pipelines, in a central place. This is not possible in cloud.

You can, with CI templates. Templates can be in a completely different repository

Lastly I would like to have multiple potential pipelines in a repository (e.g. smoke test and release).

I do have different pipelines for staging and production in my projects with no issue.

For example I think GitLabs CI is the worst on the market but if you integrate another CI you don't have a means to feedback information into Gitlab.

You can do almost everything with the Gitlab API so I'm curious what issue you had.
I'm also not sure why "Gitlab CI is the worst on the market"? I really like in particular that I can have my own gitlab-runner on any machine.

In term of privacy this is pretty bad though. From the upvotes/downvotes activity you can very easily build a whole graph of stuff you like/dislike. For advertisers that's juicy data.

This is not just Reddit imho. Look at Twitter, everyone is mad all the time over there. I'm not sure how to explain what is happening but it's all over the board imho. People get offended for everything, they seem to fail at empathy, they love to hate, it makes them feel good about themselves, every topic is somehow black or white too.

It has been mentioned, but this is not a search. It is a way to list all local magazines of an instance. Does not go through the fediverse as far as I know.

Thanks. So there isn't really a search, you have to list all the magazines and do the search yourself it seems. Also calling https://kbin.social/api/magazines would only return local magazines right. So there is a need for a service doing that crawling/indexing of all magazines from all available instances regularly.

Isn't this violating the GDPR? At least for European citizens.

Not sure what you mean. Sure you can buy any domain and put it behind. But ultimately you are much easier to doxx. Between whois, server IP etc. Then there is the issue of the security on that server too, but that's another story. What would be better is to have a way to put this behind TOR/I2p, that would make things a bit better.
On a centralized website the issue is less present as only the admins of the server can see the details about you, ip etc (maybe mods can too on reddit, not sure), here everyone can see everything, it's a lot more invasive imho. Everytime you upvote/downvote something, your account handle is saved on the post as upvoter/downvoter. This is very juicy data to build profiles and analytics on people.

The main issue I see with that is the privacy issue. You can host your kbin instance with your own domain yes, but then everyone can see your domain after your username. And it becomes quite easy to doxx you then...

Between this and the requirement for email address at registration I find the lack of privacy on kbin/fediverse a bit curious. I don't see why such a feature brings value, but at the same time I guess it's more for a technical reason. The list of users who upvoted need to be saved anyway and as it's decentralized anyway anyone can read it. Just wished it was hashed instead, or replaced by some digital signature.

My understanding is no. You would need account migration. And at the moment kbin or lemmy does not support it?
Only Mastodon seem to support that.

https://joinfediverse.wiki/Moving_instances

For me this is still a big issue to solve. But hopefully will happen at some point.