* wip
* first pass done
* chnage around how channels function
* bugfixing
* fix up migration & tests
* fix dev-env
* add prep migration for stream fixing
* application code changes to use new repo_event table
* dont send evts
* add outgoing_repo_seq table + sqlite migrations
* patch up down migration
* patching up a couple things
* update test
* patchup
* re-enable subscription route
* add outgoingSeq column
* updating
* accidental add
* temporarily disable stream
* resolve merge conflict
* add migration
* migration for seq
* fix test
* id -> seq
* get schema lock ids
* tidy
* fix server test
* fix up
* use bsky uniqueLockId approach
* tidy
* gh actions build
* build branch
* build branch
* tweak test
* rm constraint rename
* small bugfix
* check for seq not null
* fix up issues
* one more small change
* tidy
* no build branches
* ✨ Allow searching repo by DID
* ✨ Port over did search from pds
* ✅ Add tests for bsky implementation of admin searchRepos
* 🧹 Cleanup according to PR review
* temp disable hot-classic
* Switch labels in whats-hot to values list
* Switch labels in getPopular (legacy hot-classic) to values list
* Reenable hot-classic, switch labels to values list
* remove branch build in workflow
* nsid: reduce 'name' length from 128 chars to 63 chars
* nsid: remove 'nsid-ns' (glob pattern) from main NSID syntax validation
This special variant syntax should be handled separately. Eg, an
"nsid-ns" should not be accepted as an NSID in Lexicons looking for a
regular NSID.
* nsid: update syntax check to match domain rules
This is to be closer to actual underlying specification needs. For
example, domains are allowed to start with a digit (like 4chan.org), and
can't start *or* end with a hyphen.
Restricts the "name" part further, to be alphabetic only.
Note that starts-with-digit domains could break some lang
auto-generation variable name rules. The docs/spec strongly recommend
against such domains for use with NSID, but it seems incorrect to
restrict at the standard/lexicon level without a clear pan-language
consistent set of rules.
* did-resolver: disallow did:web with path segments
* identifier: reduce max length of DID from 8 KB to 2 KB
* identifier: add DID test with escaped ':' in identifier
* did-resolver: have prettier run on tests/
* identifier: add additional punycode test cases
* identifiers: small tweaks from review
- type in did:web comment
- include actual max DID string length in error message
* xrpc-server tests: remove digits from NSIDs
* identity: fix import and function errors
* xrpc-server tests: remove digits from NSIDs
* xrpc-server: include tests/ in prettier:fix
* xrpc-server: lint fix
* Rename getLabelsForSubjects to getLabelsForUris
* Generic method for getting profiles organized by did or aturi subject
* Batch label fetching for posts and authors in feeds and threads
* Tidy
* To avoid performing many view refreshes in a row w/ different leaders, schedule them upfront
* Apply feed threshold to with-friends and mutuals algos
* Revert increase to getRepo commit chunk size
* Alter feed threshold approach to be tighter and relative to cursor
* ✨ Allow ignoring moderation reports by subject
* 🔧 Remove unwanted package.json change
* ✨ Remove subject format specifier
* ✨ Port over ignore subject implementation to bsky package
* Revert "✨ Port over ignore subject implementation to bsky package"
This reverts commit 3c782c1805548d1ebdbbd08b68b6e92ac97fdee5.
* 🚧 Port over ignore subject implementation to bsky package
* ✨ Generate lexicons for bsky
* Temporarily skip online/valid checks for feedgens while external feedgens catch-up
* tweak algos
* hook up did resolver with cache
* Re-enable whats-hot w/ materialization
* pulling a fast one on the query optimizer
* clean up
* disable branch build
---------
Co-authored-by: Devin Ivy <devinivy@gmail.com>
* Setup whats-hot materialized view w/ params, run view maintainer in service entrypoint
* Update whats-hot to use new materialized view, tidy
* Update migration to create with no data
* Revert whats-hot migration change for no data
* Bump refresh rate for view down to 1min
* Better feedgen errors in getFeed and getFeedGenerator
* Support handler output headers in codegen
* Support handler output headers in xrpc-server
* Implement server-timing helpers and apply them to getFeed
* fix codegen issue
---------
Co-authored-by: dholms <dtholmgren@gmail.com>
This makes the whole type of bugs like #1080 impossible,
Also fixes `app.bsky.feed.defs` in the bsky package as it was now throwing errors
Co-authored-by: Daniel Holmgren <dtholmgren@gmail.com>
* move handle resolution to .well-known
* required handle on resolveHandle
* rm test
* tidy
* tidy
* fix up appview
* missing await
* atproto-handle -> atproto-did
* shift did & handle resolution to new identity package
* fix up network mocks
* fix up another test
* one more
* drop lex comment
* rm handle param
* Update packages/identity/src/handle/index.ts
Co-authored-by: devin ivy <devinivy@gmail.com>
* still temporarily support xrpc handle resolution
* typo
* ensure return value is a string
---------
Co-authored-by: devin ivy <devinivy@gmail.com>
