if your choice of api route directly affects your auth flow something is very wrong.

just use a make file like a civilised human being

why gitea instead of forgejo?

if it wasn’t for the webui, a bare git repo would suffice. any repo can be a remote. it’s distributed, after all.

forgejo is the most popular choice right now.

if you wanna be extra you can host git-pr

dependent on where you are, they are textbook skirting the law. uber got crushed when they launched in sweden because taxi drivers need to do basically the same training as bus drivers. it’s an extra letter on your license, with all that entails of age limits, theory and practical tests, x amount of time driven a year etc.

nowadays ubers in sweden are just taxis, which hilariously means that they by law have to have a price list on the cars. which basically kneecaps their entire business model.

or it’s, y’know, crypto

no, it’s literally all in service of sending notifications. but there’s a lot involved. android doesn’t have a way to receive them natively for example, you need to go through google’s services. so ntfy has to emulate the firebase api. then there’s the “exactly once” requirement, which is basically the two generals problem turned up to eleven because every platform syncs differently and you need some way to store messages that are in the process of transmitting. then there’s the matter of punching through NAT, so you need a STUN/TURN setup on the server.

and that’s on top of the fact that every platform requires different build options, manifests, certificates, etc.

if you want to send one notification from your desktop to your phone, it’s easy. but from any device to (m)any other, with guaranteed delivery and no doubles? shit gets complicated.

yup

i think it’s pronounced “butter” actually

omfg

yeah not a good look to have pictures of space nazi soldiers on your chest

one of my favorite notes in the linked article is that the guy playing damar constantly got sugar highs from actually drinking the corn syrup they used in the kanar props.

yeah there’s a lot of regex in there so i definitely get wanting some compiled parts.

interesting! it should be equal since it’s always just a pointer to that same table.

the key does stop existing, insofar as referring to any name that is not defined in lua results in nil. which includes variables, since they are defined in a global table. i don’t actually know what happens internally.

yeah that’s probably when you should drop down to C.

i think the most interesting design detail of lua tables is just glossed over as “nil-holes” in this article. namely, that nil values do not exist. there is no table.delete(key) method, you just zero out the value and the key stops existing. the same thing is true for any variable, if you set it to nil it ceases to be. i find that implementation fascinating.

a class can be inherited from, a struct can not.

for some, yeah. depends on your use case.