Nick Gerakines

@ngerakines.me

he/him; Protocols, platforms, and machine learning; @lexicon.garden @lexicon.community @ohcraphey.app

has it been enough time since the last time? YUP, repost, follow all, you know the drill! for anyone new to the atmosphere and specifically the atproto dev side of things, welcome home.

Post nicht verfügbar.

PDS folks! Working on a redesign of the authentication and dashboard screens for the reference PDS, bringing in a proper component library and consistent patterns across the UI. One notable change: customizable light/dark backgrounds on the auth screens. Let us know what you think! #atproto

pds sign in screenpds sign in screen focused on the password inputpds sign in screen with an illustrated background of people playing in a park at nightpds account dashboard

hey bluesky, i've been unemployed since i graduated. i'm proficient in typescript and python, and can learn new stuff fairly quick. also familiar with using LLMs in various ways. Please hire me.

Hey interoperability nerds: I need a word for actors in distributed social media systems that provide content moderation services. Blockparty is an example. Bluesky labelers and algorithm providers are examples. Blacksky is an example because of its content rules (but having a PDS doesn't matter).

ANNOUNCEMENT: I’ve been working on putting together something between a retreat and a hackathon for #atproto builders for the past several weeks. I’ve been in discussion with potential funders and some funding has become available to make this a reality. now, I need your help!! KEEP READING 👇🏽

Seventh in the atproto permissioned-data series: notifications. One self-keyed space per identity, every app writing through a create-only grant, and a reader you choose doing the triage. The self shape returns, direction flipped.

Permissioned Data Shapes: Notifications

A self-keyed space gives notifications a home you control: every app gets an append-only sink to write into, you pick the reader that turns them into pushes and emails, and allowing or revoking an app is an access control you already have.

ngerakines.leaflet.pub

🧵 Blacksky is looking to buy a server for $30k USD. We'd like the following specs or better: - 384 GB RAM - 80 TB NVMe; ZFS RAIDZ2 in 2 vdevs - 1 Gbps + 10 Gpbs burstable - at least 84 threads for the CPU(s) - Ideally somewhere in the eastern half of North America but open to North America and EU

There are many things being built on atproto. Many of them won’t get adopted or thrive. And yes, many are built without user research. It’s OK? Don’t use things you don’t want to. Promote things you like. And build something yourself if you feel like it. Do it the way YOU want it to be.

Seventh in the atproto permissioned-data series: notifications. One self-keyed space per identity, every app writing through a create-only grant, and a reader you choose doing the triage. The self shape returns, direction flipped.

Permissioned Data Shapes: Notifications

A self-keyed space gives notifications a home you control: every app gets an append-only sink to write into, you pick the reader that turns them into pushes and emails, and allowing or revoking an app is an access control you already have.

ngerakines.leaflet.pub