l4.pm
commits
way more complex than it deserves to be for three reasons:
- PR comments MUST be created through tangled appview
(pr comment records aren't wired into the tangled ingestor.
idk why, idk who i need to call to know why)
- tangled appview has its own oauth session i need to go through to get
the right cookies, its not an XRPC that goes through my PDS
(which would let me auth in some more atproto-native methods
instead of simulating a browser oauth flow, including consent)
- the tangled record doesn't assign PR numbers to pull records
(tbf it is a nontrivial problem, but i would've wished them to have
provided some sort of answer to this), which REQUIRES me to get
the PR number via scraping HTML. in a way tangled is more
using atproto for identity only, the actual PDS records don't reflect
a lot of the real appview beyond providing a loose, unrecoverable
(in terms of real URLs) backup of tangled's sqlite db at a given time
look i know its funny but its not useful im sorry to be the fun cop
way more complex than it deserves to be for three reasons:
- PR comments MUST be created through tangled appview
(pr comment records aren't wired into the tangled ingestor.
idk why, idk who i need to call to know why)
- tangled appview has its own oauth session i need to go through to get
the right cookies, its not an XRPC that goes through my PDS
(which would let me auth in some more atproto-native methods
instead of simulating a browser oauth flow, including consent)
- the tangled record doesn't assign PR numbers to pull records
(tbf it is a nontrivial problem, but i would've wished them to have
provided some sort of answer to this), which REQUIRES me to get
the PR number via scraping HTML. in a way tangled is more
using atproto for identity only, the actual PDS records don't reflect
a lot of the real appview beyond providing a loose, unrecoverable
(in terms of real URLs) backup of tangled's sqlite db at a given time