Conversation
Notices
-
Embed this notice
>loves fedi
>decides to write backend
>starts reading apub spec
>writes backend that adheres to spec
>tries in prod
>it doesnt work
>realizes that no fedi deployment ever follows the spec
>every implementation has too many catch-22s and gotchas
>give up
thats why you will never see theorytoe fedi backend/frontend stack ever
- Sexy Moon, narcolepsy and alcoholism :flag: and ✙ dcc :pedomustdie: :phear_slackware: like this.
-
Embed this notice
What language is it written in
-
Embed this notice
@charlie_root i have like 2 months worth of commits in my private repos
but man its so jank I dont even want to fix it
-
Embed this notice
So yer telling me this whole fediverse thing is all smoke and mirrors? Just shotty webtech held together by duct tape, rubber bands and bubblegum? 🤨
-
Embed this notice
@charlie_root always has been
-
Embed this notice
@theorytoe Fake News, Standard doesn’t even contain httpsig or webfinger
-
Embed this notice
@Moon @charlie_root
go because thats the one I am most competent with
and yes I know gotosocial is in go this was written months before I knew about that
-
Embed this notice
Go is fine.
-
Embed this notice
@lain yup :dread:
-
Embed this notice
@pro @theorytoe @charlie_root activitypub has big gaps beside just the special things you need to do to interop with mastodon. and there are other implementations that just plain do specific things wrong.
-
Embed this notice
@Moon @theorytoe @charlie_root It's a highly naive to expect specs being sufficient for network protocols. Just look at the archives of tcp-implementors list. In fact I got a taste of it 25 years ago, when I wrote a uucp-g from scratch. Not only the classic UNIX and BSD were different, but so was UUPC. And yet it was possible to create an implementation that interoperated with all of them.
-
Embed this notice
@pro @theorytoe @charlie_root I appreciate what you're saying but there's spec gaps and then there's "the spec is finished on this deadline."
-
Embed this notice
@pro @theorytoe @charlie_root I seem to recall that ACPI was partially a formalization of what Microsoft had worked out with vendors. with regard to xml it is a very clear spec but everybody was generating feeds using string appending in PHP, etc which should have been unacceptable but yeah that's the world we live in.
-
Embed this notice
@Moon @theorytoe @charlie_root Maybe I'm just jaded. But this sort of thing is all around us. I remember what kind of trouble it was to make ACPI work on laptops. Yes, there's a spec, but the real world test at OEM was to boot Windows. Or, the RSS. It's actually XML and it must start with DTD. But a bunch of generators added whitespace, which choked all library parsers. Every reader from Google Reader (rest in peace) down had to strip whitespace before parsing. I don't expect anything else from AP, especially given how open-ended it is.