Oh man a tui would be amazing for development.

My Facebook is broken, I never use it, don’t join groups, have targetted ads turned off, so all my feed is just random trending videos Facebook thinks I might like. Barely even see my friends posts. I can’t spend more than 2 minutes on the homepage

I love when claude gives time estimates like week 1 do this, week 2 that…
No claude, you are doing all of it right now. Then you are going to write all the unit tests

I saw the post but didn’t want to take the bait
There’s a balance between ssr and js, i think tangled could us more js
Htmx helps with things feeling snappy but it’s under utilized imo.
Github on the other hand has been so slow for me most times i try and use it compared to tangled

Can you walk me through what you did? looks like you installed the credential-helper, tried to push, it opened the website, you logged in approved the device then the push failed?

I'm not entirely sure what went wrong other than something in the auth flow failed. re-logging at atcr.io should fix

I can check logs in a bit, but first thought would be to log out and back into the website. You didnt get added to the default hold

@ana.pds.nkp.pet you might have pushed just the manifest list with attestation and not the underlying arm64 image?
You can check if the layers make it here: pdsls.dev/at://did:web...
I might need to handle manifests lists better if this works elsewhere

tangled.snek.cc/oauth/jwks.j...
Missing token

Also a handful of ui/ux improvements around configuring new knots/spindles

I feel like my fy feed goes through waves depending on who i follow likes a bunch of the same style posts. It might be a little too sensitive to certain people just liking everything on there discover feed

At least with atproto you wont have mismatched profiles. No, black eyed peas doesn’t commit to github.

That github list doesn’t include did:web so embedded pds won’t show up. My @hold01.atcr.io isn’t there either pdsls.dev/hold01.atcr.io

Any soda
Anisota

the "holds" (aka @hold01.atcr.io ) handle the fetching presigned urls from your S3 provider for downloads/uploads. They have their own PDS and user, and are independent #atproto entities. All they need is a service token signed by your PDS to verify you are able to access their data.

In the case of @atcr.io manifests/tags stored in your PDS are cached in a database on the appview side so I don't have to fetch them every time. They get periodically backfilled, and I listen to jetstream to handle new events (and deletes)

This is now complete:

Developers can use scoped permissions now, they aren’t really documented, but i am using them in my app. I am finding some quirks with using them however.

PRs and issues are lexicons. Could start with that