

why gitea instead of forgejo?


why gitea instead of forgejo?
idk, it just makes me sad
this does like the opposite of what i want it to do.
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.


for some, yeah. depends on your use case.


for what it’s worth matrix has worked well for us. it’s apparently a bitch to set up though.


now do the other ones


soundn like a problem with your friends then. who doesn’t love a stoat?


you mean unlike the tools discord has replaced, such as “mumble”, “ventrilo”, “roger wilco” and “trillian”?


it’s been unchanged because http got more popular.
there is a vocal part of the indieweb that does not want encrypted communication because it increases the system requirements, and because it disincentivises sending sending any sensitive information. i don’t really agree with that assessment but i do think there is something to not sending stuff you don’t need.


gopher predates http, of course it didn’t have certificates.
yeah this project has been on github for six years and seems to have been closed source before that. it’s a graphical automation tool.
like, everything can be used with ai. github itself has “ai agent” plastered everywhere. it’s just a buzzword. doesn’t mean it’s built specifically for ai.
could be one of those cases where the product predates ai but some c-level asked an engineer “could we use this for ai” and the engineer said “i mean, technically yes” and then marketing changed every single mention of the product


i like how everyone got hooked on the cgnat thing when i gave the actual solution in the main post. but yeah there’s always the option of not doing anything until i see issues.


i’ll worry about the nat traversal when i get my bouncer back up, but it will probably be less full-featured than pangolin. previously i just used a reverse ssh setup but that was a bit too rudimentary.


that’s also a possibility, but i’m going to have to whine to my isp.


as i said i’m getting my bouncer server set back up next year after the datacenter it’s in has finished renovations, so actually getting a public address is not the biggest issue.
just use a make file like a civilised human being