Oh I’ve looked at it - I think a place like that (with the working groups, committees, etc) makes sense once different ideas have been tried out.

Just like we try out application-level lexicons before standardization, I think there is space to do the same with network-level lexicons.

Yes - doesn’t have to be its own PDS if someone is the permanent owner/host of the publication.

The glue lexicons for this kind of stuff interests me - may give it a go in the next few days. Picked up lexicon.work a couple days ago to have a place to play around with “enabler” items like this.

Reasoning is that you need both confirmation that the publication approves the user to publish and that the user actually confirms their involvement (vs false attribution). Regardless of in which PDS the article lives, confirming entries from all other parties is critical.

On the technical side, a shared publication should likely live in its own PDS with a few custom lexicons on the publication side to identify approved users/roles paired with an item in the user’s side accepting the invite. Users would publish claiming the publication and the publication validates.

This is wonderful & don’t listen to anyone saying otherwise.

You are building decentralized tech and are the stewards of @atproto.com - that matters more than any of this and needs strong leadership who don’t want to be in the business of “editorial” decisions.

Keep building the solid foundation.

WAFFLES

Okay - that makes sense. Thank you for entertaining my questions

Okay - was just making sure there weren’t any issues on 3.13.

Fwiw, I believe uv will default to a preexisting Python install if a compatible one is found? @crmarsh.com

Thank you - I’ll check that out more!

Last one haha

Any quick way to enable basic hjkl vim motions to scroll? Loaded up the demo and did it instinctively since I was in a terminal.

Any reason for specifying 3.12 on the 1.0 release tweet versus 3.13?

I do a lot of work in closed environments - any pointers or things to keep in mind when using Textual without an internet connection? Any way to self host textual-web apps on an internal network instead of textual-web.io?

There is support for secondary labelers, block lists, etc that allow you to actively shape your network as you see fit.

I understand they are under pressure right now, but I don’t want to see the default moderation settings creating an “echo chamber” when it is so easy add further moderation on top

Great graphics - but it is unclear to me how you are describing bluesky/atproto as “private”… it is explicitly not private. Even “blocking” someone is just a front end feature.

There is no actual protection of the unencrypted data, and *anyone* can data collect as much as they want — correct?

*fall to the side

I personally cannot wait for conda to fall the side for Python

It had a place in the ecosystem for many years, but is now just a non-standards compliant alternative with a lot of baggage. It can go.

Of course. I think it is hard because of the fragmentation. There are just so many ways to do deployment w/ Python that it takes being in the ecosystem for a bit before you know what tools work best for you. Similar to how I’d not really know where I’d start if I needed to work a typescript project.

Oh and since you mentioned Docker, you might want to checkout some of @hynek.me’s work on this

bsky.app/profile/hyne...