Zicklag

https://mastodon.social/@zicklag

Software engineer and problem solver with a passion for producing high quality solutions to real-world problems. I strive to make great things that people can use and enjoy, all to the glory of God.

Blog: https://zicklag.katharos.group
GitHub: https://github.com/zicklag

Public Key

npub1z53xkqmz905j6mp6sl7q7ddtedyh4ppxkz6n2xl3ek0kkfr6rghsduevsh

NIP-05 Address

zicklag_at_mastodon.social@momostr.pink

Profile Code

nprofile1qqsp2gntqd3zh6fddsag0lq0xk4ukjt6ssntpdf4r0cum8mty3ap5tcpz3mhxue69uhhyetvv9ujuerpd46hxtnfduqs6amnwvaz7tmwdaejumr0dsupyfzj

Publishing to

relay.damus.io

nos.lol

Author Public Key

npub1z53xkqmz905j6mp6sl7q7ddtedyh4ppxkz6n2xl3ek0kkfr6rghsduevsh

Show more details

Last Notes

2024-07-16 23:45:00

- reply

That said, interoperability with ActivityPub is something we are very interested in.
I think there is a lot of opportunity for 2-way communication between ActivityPub and our data model.
---
Just for reference, this post might serve as a useful background for some of the ideas we're considering. Note that this was written before the idea of using an Entity-Component model:
https://zicklag.katharos.group/blog/how-to-federate/
2/2

2024-07-16 23:41:13

- reply

I talked to some more ActivityPub savvy colleagues and it does look like you could technically accomplish lots of our goals with ActivityPub, if combined with Iroh for storage.
But ActivityPub is also largely underspecified, and would require extensions that many AP servers don't support.
We prefer to make a very precise protocol specification to give tight interoperability at it's core, but allow component data and schemas to develop independently for extension.
1/2

2024-07-16 19:03:42

- reply

Yeah, we're quite familiar with ActivityPub.
There are lots of things that go into it not being sufficient for what we're imagining, but one of the most basic limitations is that when you use actual URLs for entities, you are dependent on DNS and servers, which defeats many local-first use-cases.