Image
▖ Image ▌▖▌▖▌▖▖▌
▖ Image ▌▖▌▌▖▘▌▖
▖ Image ▌▘▖▘▖▌▖▖
▖ Image ▌▌▖▌▌▘▖▖

status

/icons/msn.webp

last log was… published 17 hours ago!

anyway, might as well take advantage of this like i always wanted to -contains media- -contains quote- (bsky)

last git activity… was 7 days ago..

[tangled] hydrant: [net] add HYDRANT_ALLOW_PRIVATE_NETWORKS for local dev stacks a stack that serves every name from loopback can't be reached through the public egress check, which drops any dns answer that isn't a public address. the switch turns that check off for the whole process and defaults to off.
[tangled] hydrant: [beads] update beads
[tangled] hydrant: [relay] answer a subscribeRepos cursor past the last seq with FutureCursor the event stream spec says a cursor higher than the current seq gets an error and a close. hydrant replayed from it, found nothing, and skipped every live event below it, so a consumer holding a cursor from another relay or from before a reset waited with no error until the seqs caught up, maybe forever. it gets a FutureCursor error frame now and the stream ends. indigo's relay goes live instead, which hides the gap, while the spec's way lets the consumer decide, and indigo's and hydrant's own consumers already handle FutureCursor from a pds. RelayStreamError has a FutureCursor variant for embedders.
[tangled] hydrant: [relay] a dropped queue's newest #account still lands a relay shard drops a did's held messages at a cap or its deadline and marks them done for the cursor. for commits that's survivable, the next one shows the gap. an #account among them was lost for good though: a takedown is usually the last thing an account sends, so nothing came after it, and relay builds have no crawler to read the status back from listRepos. hydrant kept serving and forwarding the account. the newest #account of a dropped queue now runs anyway, as if the did's lookup had failed, the way held messages replay after a failed lookup. one from a pds still has to pass the host check against the stored pds. a new account's queue has no row to land on, so its messages are dropped as before.
[tangled] hydrant: [indexer] a buffered commit that doesn't follow the car fails the drain the drain applied what was buffered during a fetch without asking whether it follows the car. each commit was checked when it came in, against the root back then, but the car can be older than that root, and the firehose can skip a commit between the two. the commit that triggered the backfill is buffered too, so after a stale car it went straight onto the old records. a buffered commit whose since or prevData doesn't match the root it would apply onto now fails the drain, which costs one refetch the way a buffered commit that can't apply does. a missing prevData isn't held against it here, the check it went through on arrival saw that.
[tangled] hydrant: [backfill] a car behind the stored root takes the root back too a pds is the authority on its repo, so a getRepo answered with a car older than what hydrant had (a replica behind, a restore) replaces the records, as it did before. the root kept the newer rev though, since rebased never moves a root back, so the next commit chained onto that root and landed on the car's records, and the commits in between stayed missing for good. when the car's rev is below the root the backfill started from, the root now goes back with the records. the next commit doesn't follow it, the repo backfills again, and by then the pds usually serves its current repo. rebased keeps its rule, the relay overlay needs it.
[tangled] hydrant: [backlinks] find links in string arrays and under any key jacquard only types a string that's an object's value, guessing from the key, so an at-uri in an array (a threadgate's hiddenReplies, a postgate's detachedEmbeddingUris) stayed a plain string and extract_links skipped it, and a did under `handle` came out as an at-identifier and was skipped too. the four links tests with a string or an array at the root failed on main for the same reason. the string decides now: one starting at:// that parses as an at-uri, or did: that parses as a did, is a link wherever it sits. records indexed before this keep their missing links until they're written again.
Image

listened to My Sputnik Sweetheart

in Come In

by Weatherday

…20 days ago

cool buttons :>

skyrina
250kb clubzero-width spacemy ownermeow_djunedddrewdenizrainblooymelysia31A05B9C's random sitenixosgodotmoonlightmembers choicedefective by designkill fascistsit/itsnot a person

feel free to send this one stuff to add here ;3

readme?

/icons/question.webp
bannerbanner
that's its angelsona ^^
my angelsona
  • trying to do stuff
  • angelrobotpuppydollthing

    it/its, 3pp preferred
    is a thing (it/she)
  • software engineer, indie game dev
  • working at tangled.org, resume here
  • in turkey (get it out)

wavey this is dawn

▖▖▖▖▘▌▌▌▖▘▘

notify this one

links!

/icons/contact.webp
development
88x31
88x31 banner 88x31 banner (midnight only) 88x31 banner (sunrise only)
Image