History

Daniel Holmgren 38656e71ff

* sketching out label sequencer

* refactor sequencer

* sequencer tests

* tests

* add query labels endpoint & tests

* add pagination

* fix label formatting on temp

* tidy

* format labels

* make use listen/notify for sequencer

* ensure sig on all outgoing labels from ozone

* fixing up tests

* fix sequencer tests

* fix hanging server test

* add log on failure to update label

* update description for sig

* add expiration to labels

* fix test

* use bytes for label sigs

* fix tests

* add ver to labels

* tidy up background queue

* store signing keys as ids

* fix sequencer teest

2024-03-08 19:48:45 -06:00

bin

Feature: Appview v2 (#1924 )

2024-02-27 15:22:55 -05:00

proto

Feature - 3rd party labelers (#2032 )

2024-03-06 17:56:34 -06:00

src

Label expiration (#2241 )

2024-03-08 19:48:45 -06:00

tests

Feature - 3rd party labelers (#2032 )

2024-03-06 17:56:34 -06:00

babel.config.js

Bsky app view (#716 )

2023-04-06 18:47:46 -04:00

buf.gen.yaml

Appview v1 generating and ingesting mute ops w/ bsync (#2067 )

2024-01-22 15:48:31 -05:00

build.js

Feature: Appview v2 (#1924 )

2024-02-27 15:22:55 -05:00

CHANGELOG.md

Version packages (#2282 )

2024-03-06 16:58:19 +00:00

jest.config.js

Bsky app view (#716 )

2023-04-06 18:47:46 -04:00

package.json

Version packages (#2282 )

2024-03-06 16:58:19 +00:00

README.md

Update atproto source license to MIT/Apache2 (#1788 )

2023-11-02 00:45:13 -07:00

test.env

Bsky app view (#716 )

2023-04-06 18:47:46 -04:00

tsconfig.build.json

Bsky app view (#716 )

2023-04-06 18:47:46 -04:00

tsconfig.json

Feature: Appview v2 (#1924 )

2024-02-27 15:22:55 -05:00

README.md

@atproto/bsky: Bluesky AppView Service

TypeScript implementation of the app.bsky Lexicons backing the https://bsky.app microblogging application.

License

This project is dual-licensed under MIT and Apache 2.0 terms:

MIT license (LICENSE-MIT.txt or http://opensource.org/licenses/MIT)
Apache License, Version 2.0, (LICENSE-APACHE.txt or http://www.apache.org/licenses/LICENSE-2.0)

Downstream projects and end users may chose either license individually, or both together, at their discretion. The motivation for this dual-licensing is the additional software patent assurance provided by Apache 2.0.