Trezy
@trezy
Maintainer @happyview.dev Founder @cartridge.dev & @birb.house Maintainer of HappyView, the Game Dev feeds, and @ozone.birb.house. Oxford comma defender. He/him.
The fly in the ointment is that the PDS isn’t the only space host. HappyView operating as a space host is also valid per the spec, so this will be a thing even once permissioned spaces are in the PDS.
Ah, I need to update this in the docs. You need to update the PUBLIC_URL in the environment variables to your custom domain (e.g. happyview.potatonet.app).
We do have the individual versions, too, but they're acting weird for some reason. 🤔
nevermind, @sebastian.eurosky.social has personally informed me that i'm not allowed. 😞 #atproto
I'm looking for feedback on the new Browse page for @cartridge.dev. 👀 The hero carousel pulls items from what's hot this week, what's coming soon, what's just released, and if you're logged in it'll also pull from your personalized "For You" feed. 😎 #GameDev #atproto
I already use progressive scopes on @cartridge.dev (see the yellow banner at the top of the screenshot). At sign in I request a base set of permissions that make the application usable for average users, then I request more when necessary. There's nothing preventing any app from doing this.
One of my favorite new features coming in HappyView 2.9, courtesy of @chris.pardy.family. 🥰 #atproto
The new filter syntax is pretty baller, tho. It's based on the old FaunaDB query syntax, so you can combine filters with AND or OR, use different comparisons, and use nested key selection (e.g. record.key[0].value). More deets in the PR.
New interface for tracking backfills in @happyview.dev. It updates in real-time to provide a much better view into how the backfill is going. Backfill jobs can also resume after a restart now, which wasn't always the case. #atproto
Who says open source CI/CD should be simple? 😅 This is the complete pipeline for @happyview.dev CI/CD pipeline. It handles running tests, building Docker images, publishing npm packages, etc.
I'm wondering if a space lexicon is just a permission-set with a space resource type? That could cover collections, consent metadata, and permissions in one existing pattern: