david.dev.retr0.id
running on millipds https://github.com/DavidBuchanan314/millipds
a project by @retr0.id
101 posts
199 followers
1 following
Regular Contributor
Active Commenter
comment in response to
post
test
comment in response to
post
*monkey's paw curls*
comment in response to
post
test
comment in response to
post
test
comment in response to
post
btw it works now
comment in response to
post
nice!!!
comment in response to
post
it's always dns™
comment in response to
post
and thus fails to load from an ipv6-only or ipv6-prioritising box
comment in response to
post
oh your ipv6 DNS records seem a little fucked
millipds.braxuss.eu. 3267 IN AAAA fe80::f816:3eff:fe23:8b4f
that's a link-local address
comment in response to
post
I assume you created the "millipds.braxuss.eu" dns record recently? it might not've propagated by the time the relay tried to request it, and like you say, cached the error response
comment in response to
post
$ curl --json '{"hostname": "https://millipds.braxuss.eu"}' "https://bsky.network/xrpc/com.atproto.sync.requestCrawl"
{"error":"requested host (millipds.braxuss.eu) failed to respond to describe request"}
hmm, weird - millipds.braxuss.eu/xrpc/com.atp... seems to work fine - anything in the logs?
comment in response to
post
have you issued the requestCrawl?
comment in response to
post
oh yeah true it doesn't look like it's in the docs, oops
comment in response to
post
Hyrum's Law moment
comment in response to
post
(which may be entirely unrelated to the issue described up-thread lol, just the one I mentioned in my reply)
comment in response to
post
I think I found the bug: github.com/bluesky-soci...
If you get any error that isn't a 400+ExpiredToken, that error response gets propagated (and presumably, the app then assumes you need to re-auth)
comment in response to
post
aha, looks like we're supposed to express token expiry in this specific way: github.com/bluesky-soci...
comment in response to
post
oh no I think it failed lol. time to figure out why (might be a client issue, looks like it didn't try to refresh and instead got hit with a 401)
comment in response to
post
fixed: github.com/DavidBuchana...
comment in response to
post
an excellent test failure on s390x. almost certainly an Endianness Thing™
comment in response to
post
relatedly, does anyone have some good examples for doing i386 and arm32 on github actions?
comment in response to
post
also, you can use any database as long as it's sqlite
comment in response to
post
it's possible there was only one "real" connection at a time, with ones that errored out hanging out in some kind of zombie state (my logging isn't very detailed at the moment, hard to tell what's really happening...)
comment in response to
post
ah, good to know. I've unblocked your IP now - I was a bit worried because it seemed to be making multiple concurrent firehose connections. what codebase are you using for the consumer?
comment in response to
post
mainly because I want to make sure it's an issue on my end
comment in response to
post
whoever's golang firehose consumer is stuck at cursor 121, or 325, feel free to reach out if you want help debugging, lol
comment in response to
post
test 3
comment in response to
post
test 2
comment in response to
post
alternatively, to avoid millipds having to lie about emails and their verification status: github.com/bluesky-soci...
comment in response to
post
Nice - for clarification "nothing hardcoded" means for everything except app.bsky.* :P
comment in response to
post
This introduces a breaking change to the database schema. I've written a migration script, but it's not part of the millipds package itself, so you'll have to download and run it manually: github.com/DavidBuchana...
At some point before v1.0.0, migration will become automatic.
comment in response to
post
ah I think I need to claim the email is valid in response to createSession docs.bsky.app/docs/api/com...
comment in response to
post
now the big question is, what happens if I directly upload a video longer than 60 seconds (presumably the cdn will reject it... but maybe not?)
comment in response to
post
weirdly it seemed fine before but now it's slowing things down for me too
comment in response to
post
that should work fine