Just saw that it is back up. Thanks for getting it running again!

Ahh okay - sorry you’re having to deal with that. Have you gotten an ETA from the hosting provider for a fix?

Luckily one of the players in our game hit export the night before it went down so we didn’t lose anything, but the game is on pause rn since we didn’t know what was going on.

Where’s the evidence?

@sassnow.ski looks like utgars-chronicles.app is down if you could give it a kick

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.

Happy Python 3.14 ( #πthon ) release to all who celebrate!

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.

We are alarmed by reports that Germany is on the verge of a catastrophic about-face, reversing its longstanding and principled opposition to the EU’s Chat Control proposal which, if passed, could spell the end of the right to privacy in Europe. signal.org/blog/pdfs/ge...

typelex – An experimental TypeSpec syntax for Lexicon An experimental TypeSpec syntax for AT Protocol Lexicons. Write Lexicons in a more readable syntax using TypeSpec.

may i present to you, my weekend project

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

Even as @safety.bsky.app is staffing up - I would like to remind everyone that this is a *decentralized network*. We should not want the same level of *centralized enforcement* as others.

Yes bluesky moderation helps massively to control your experience, but it is not the only method on here.

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?

@pfrazee.com I was looking at news.ycombinator.com/item?id=4208... and it looks to be just the PDS — what would be the complexity of truly running *all* of BlueSky/atproto on a offline/private network?

It all appears to be licensed MIT, just trying to gauge the feasibility of an internal instance.

Sooners involved in a premature land rush? Where have I seen this before?

BOOMER SOONER!!!

*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...

I do want to say that I don’t blame you for having issues here - the Python ecosystem is very fragmented (like JS in a way) and it takes a bit to learn which pieces to use to solve the common problems (like node vs bun vs deno). Happy to help if you have any other questions about why it’s like this.