canpolat

joined 2 years ago
MODERATOR OF
 

Coming from CVS and ClearCase it took me some time to adopt to Git. The fact that it was distributed was confusing at first, for example, because I thought that would cause chaos. But the way we used it was actually not "that distributed". But once I understood how it worked, not doing DVCS was "the wrong way" immediately.

[–] canpolat@programming.dev 17 points 1 year ago* (last edited 1 year ago) (1 children)

I don't follow it very closely, but as far as I know, they are the only one implementing the open protocol they designed (which doesn't interoperate with ActivityPub). However, there seems to be some efforts for creating a bridge: https://www.docs.bsky.app/blog/feature-bridgyfed

As you said, there are some recognizable faces and that may impact the adoption. But not being compatible with ActivityPub is a real bummer.

[–] canpolat@programming.dev 3 points 1 year ago

When I joined some years ago, it automatically created a private, invite-only room named "Echo Chamber" with me being the single member. If it didn't happen to you automatically, you can create one yourself.

[–] canpolat@programming.dev 3 points 1 year ago

Sounds like a good plan, thanks!

[–] canpolat@programming.dev 4 points 1 year ago (3 children)

I would be interested in this, but I’m on this side of the pond. So good luck! Would be good if you made the recordings available afterwards.

[–] canpolat@programming.dev 9 points 1 year ago

I think single account ActivityPub implementations are addressing a weakness of the Fediverse: one's identity (handle, username) is tied to an instance they have no control over. If that instance shuts down users lose everything. With a single account instance, you take that control back. And since it doesn't need to scale the architecture can be much simpler and can be deployed to much cheaper infrastructure.

The demo was not straightforward, though. And I didn't quite get how a user can follow Mastodon users, for example.

[–] canpolat@programming.dev 1 points 1 year ago

Possibly. My point is: despite having a common subset Pkl and JSON schema doesn't seem to be solving the same problems. But, I'm just learning about it, so I may just be wrong.

[–] canpolat@programming.dev 3 points 1 year ago (5 children)

I just learned about Pkl, so take this with a grain of salt. JSON Schema and Pkl seem to have some overlap. But JSON schema is not specifically designed for handling configuration and Pkl supports other formats like YAML.

[–] canpolat@programming.dev 4 points 1 year ago

This looks really interesting. Getting type safety and editor support to configuration may change quite a bit of how things are done. I don't know if it will gain traction, but if it does, it may really help bringing some long awaited structure to all those YAML files. There appears to be examples specifically for Kubernetes (https://github.com/apple/pkl-k8s-examples).

[–] canpolat@programming.dev 6 points 1 year ago

I wasn't aware of that. I guess it was thought to be a mod driven community. Anyway... Cool question. I hope we will see some creative solutions here.

[–] canpolat@programming.dev 6 points 1 year ago (2 children)

Please also consider posting to !challenges@programming.dev

view more: ‹ prev next ›