after a month of svelte+kit, there is still this desire to do a solid.js rewrite. can't even point to an overly specific reason, except personal taste in how reactivity is expressed.

ol‘ zuck is getting dril back onto atproto

love: discovery of shared sacredness, collective agency, shared purposes

"Like with open source, open social is a compounding effort. Every mildly successful open social app lifts all open social apps. Every piece of shared infrastructure can benefit somebody else. At some point, open is bound to win."

"We don't talk about politics at work" Imagine dedicating your life to something and not even daring to dream that your work could have a political impact Looking deep into the innermost part of your soul and there's giant glowing letters there spelling out "B2B SaaS"

a web framework with kdl for markup and gleam for scripting would fix me.

excited to share that we are following through on our earlier commitments and putting together an independent+neutral organization to house the DID PLC system, includes the directory service

omg, this looks so nice

hot take: pds on a pi in a box with an admin app is a product that mainly appeals to the homelab demographic, that rather has fun with deploying a container on their own hardware.

we should not, under any circumstance, compare a new protocol that we are looking to make accessible to less technical people, to fucking SMTP

lexicons not having a nice upgrade path and no versioning except chucking in a specifier for that into the nsid, leads me more often than not to over generalizing and premature future proofing. choice paralysis, hooray…

horizontal scaling strategy for atproto infrastructure

encoding data in the collection name, yea or nay? contrived e.g. i have list records and entry records. besides other structuring and aggregation options, one could create a list specific entry collection (com.example.[$listId].entry). #atdev

yo @deno.land, your new request limits for deploy ea w/o a credit card get eaten up by wordpress exploit bots alone. this deployment is used only for dev purposes currently and wouldnt make it till the end of the month.

ah yes, the collectionCollectionBuilder, receiving a repo and a collection as params. naming things is so easy, i should tackle cache invalidation next.

well, at least consensus reality breakdown has a kick-ass soundtrack

Conversations around decentralisation and the open social web have gotten fairly unproductive, resulting in a letter calling for mutual respect Im signing it, and with that, I have thoughts regarding discourse, decentralisation and why this space matters. connectedplaces.online/on-discourse...

wanna push through and get this project to a state where i can do a preview release, but also starting to feel a bit of exhaustion/burn out after dealing with some particularly stupid bugs the last days.

A piece of advice for all ATmospheric travellers:

looking at other projects lexicons for reference, I often can't shake the feeling of "that seems kinda over engineered and prematurely optimised" #atdev

remembered the password of my first bluesky account and damn, never knew that i was *that* early.

still convinced that a bluesky post should be called a breeze, instead of skeet

it's a Hutzelbude & code night music.apple.com/de/playlist/...

Recently there has been a lot of dividing & heated discourse about ActivityPub and AT Protocol. Yesterday at the Social Web CG meeting, I proposed releasing a statement on this discourse, you can read the full statement here: github.com/swicg/genera... #activitypub #atprotocol #atproto #SocialWeb

Im doing everything I can to keep the internet a wonderful place what the fuck are you doing

nah, it's totally fine to have a 21 character long handle. regretting nothing at all here.

This is totally the selling point. It's actually one of two: the other selling point is helping to solve the cold start problem. They're not Bluesky's users, they're members of the atmosphere.

regarding the upcoming bookmarks and its implementation as yet another appview feature. #atdev

delete linkedin, hit the atproto docs, network up

"This social media app might seem ordinary, even underdeveloped, to your typical user. But it hides a nifty architecture under a react native frontend. Let's explore it through the magic of downloading two of them…"

I cant log off for too long. I worry about you all

by the power of atproto, obama is a @tangled.sh user

considering adding annoying mechanical keyboard sounds on hover and click

always fun to observe the bots bashing against a fresh deployment

„okay, now we are getting somewhere“ words spoken mere minutes before i started ripping out the complete styling solution of this project.

atproto in one post

atproto keeps winning

also on @stream.place, for the non-us folks: stream.place/thelotradio....

"And although our users’ accounts and data are on our server, they can seamlessly interact with any Bluesky user, and vice-versa. Borders in AT Protocol cyberspace are just like borders in the real world — imaginary. When you cross a border in real life, you wouldn't even notice without signs."

The network's zeitgeist currently reflects a strong anti-capitalist and anti-authoritarian sentiment. This is not a monolithic ideology, but a complex tapestry woven from diverse threads: critiques of worker alienation, anxieties about climate change, and a rejection of mainstream consumer culture.

verification and the limitations on which verifiers developers choose to show in their appview, should not be seen as a sign of privilege or royalty, but more in the sense of a key signing party for groups with a high risk of impersonation.

take a sec to imagine what webdev calls a meta framework, but for this ecosystem. batteries included with default cache and backfill strategies, good looking components, low setup auth, pwa by default, friendly guides, approachable for beginners. tools that grow with you and your ambitions.

hetztodon/FreistaatBavaryPub

„99.everyone% of atproto users are hosted on a bsky pbc pds“ is a common take coming through the bridges. but how’s the split looking in the fediverse by now? it’s not the same dynamic, but doesn’t the (afaik) mostly defederated meta threads be a huge factor there?

talked with @groove.museum about how screen sharing from the native @stream.place app would be a killer feature for artists on atproto. hyped for this pull request to land. 👀

man, modern technology is dangerous. just walked head first into a glass door, while thinking about my stupid appview project.

i can see the atmosphere from up here!

the @lexicon.community discourse login via atproto worked flawlessly… except that it cut off my handle a little bit to short. discrimination against people with way to long domains! (yeah, its probably the forum software, but still a tragedy)

i can see the atmosphere from up here!