In the era of enshittification I can't really see the logic in tying a bunch of your infrastructure/services to the likes of stripe.

Then again I also don't see the logic in asking spicy autocomplete to write code or provision services for you either.

Maybe I'm just not the target market. I guess if you're spinning up 5 new toy todo list apps a week to show off how well you can talk to a predictive text engine maybe this is actually useful.

“Spicy autocomplete” absolutely made my day. Thank you.

You're very welcome.

It probably also doesn't make much sense to me because I see external services as something to use when we have to, not as default choice.

When your application runs on VMs you control and just uses a payment gateway and an email gateway it's hardly a challenge to get the services setup.

Are you using an existing forge package (like eg Forgejo which codeberg is built on) or something custom?

Custom-built on top of libgit2.

Not trying to be dismissive/snarky... But why?

I started developing it as a slim wrapper around Git to support my own needs. At the same time, it is essential to have rich features like pull requests/code review, so I started focusing on designing a tool that strikes an appropriate balance between being minimalistic and functional. One thing that I focus on is allowing users to disable any feature they don't need.

If it's your ssh server and it's single user you don't need to use the "git@" part at all.

Just store the repo and access it with your account.

The whole git@ thing is because most "forge" software is built around a single dedicated user doing everything, rather than taking advantage of the OS users, permissions and acl system.

For a single user it's pointless. For anyone who knows how to setup filesystem permissions it's not necessary.

I prefer to be explicit about which user is connecting to ssh.

There isn't much advantage that can be taken from O/S users and perms anyway, at least as far as git is concerned. When using a shared-filesystem repository over SSH (or NFS etc.), the actually usable access levels are: full, including the abilities to rewrite history, forge commits from other users, and corrupt/erase the repo; read-only; and none.

Git was build to be decentralized with everyone having its own copy. If it's an organization someone trusted will hold the key to the canonical version. If you need to discuss and review patches, you use a communication medium (email, forums, IRC, shared folder,...)

So don't give them your phone number.

Arguing against 2FA is like arguing that they shouldn't bash your password because it means you can't see your password to help remember it.

It's an announcement that they're providing first party integrated first party services for something that until now has largely relied on third party solutions.

Not knowing about the exiting solutions to provision/manage Macs is one thing. Not knowing about them and claiming they're inferior because of what you didn't know is just bizarre.

I don't know what it is about the type of people who end up doing pc support, but an irrational dislike of Macs seems to be systemic. I worked in an IT department when Novell was still a thing, an a senior guy with years of Unix experience would make jokes about "toy operating system" while also alternating between screaming at and practically fellating windows XP.

> leads me to a point where I can see that the issue is a simple fix with a couple lines of code.

If you can see the problem, know how to fix it, and still ask spicy autocomplete to do it for you, that isn't "using a tool", it's cargo culting.

It's called a calendar entry. Not every life experience is some giant challenge waiting for a tech bro to create a dedicated fucking app.

I can't reply to your reply so in case you see this:

Yes anything booked ahead I generally put into a calendar entry. iOS/macOS makes this pretty simple (it detects most booking emails and offers to create an entry for me; in those scenarios it has a link in the calendar entry back to the mail message). For the ones I have to create manually I just put any important info (e.g. confirmation/reservation codes) into the Calendar entry's notes field.

For things like boarding passes I don't think I've ever seen them delivered by email. Airlines like Thai and Singapore offer digital boarding passes via their mobile app, and they just import straight into iOS Wallet. I would assume there is some similar integration with a wallet-like app on Android.

With the way modern development often goes this essentially means using spicy autocomplete for code is a just a fast track to the cargo culted solutions of whatever day the model was trained.

> In reality someone made a mistake.

It's never just one mistake. It's usually a chain of mistakes and bad decisions that make the final mistake possible.

I'd estimate that there were likely 77,168,458 mistakes/bad decisions made by individuals before this mistake could happen.