@benpate it's close enough, though. you can imagine content models as being like:
- atom:entry
- as:Activity
- html:article
and it is possible for "the same thing" to adhere to more than 1 content model
@benpate it's close enough, though. you can imagine content models as being like:
- atom:entry
- as:Activity
- html:article
and it is possible for "the same thing" to adhere to more than 1 content model
@benpate micropub is okay; its content model is mf2-based and it acts like a cms for h-entry h-card h-event and h-cite. that could be useful for powering something that maps pretty close to 1:1 onto atom entries (and h-entry is intended to be that 1:1 mapping onto atom:entry actually!) but i haven't gotten around yet to finding that useful because i do less "blog"-like work and more "wiki"-like work.
@benpate so i guess the answer i have rn is:
- build content models that make sense and are at least internally consistent
- build content formats that capture those content models naturally and with minimal effort
- build processing models for publishing and consuming that content format as easily as possible (bearing in mind easy != simple)
@benpate if all of this more or less lives inside a sort of "container" with its own "filesystem" then it becomes far more portable, which is what i'm trying to make fall out of my work naturally. you can take your outbox "around" to whatever service provider is willing to host it. with inboxes, it can be the same thing with taking your inboxes "around" to whatever provider is willing to host them. similar to how IMAP lets you both download *and* upload messages.
@benpate using activities as an example of a content model: the outbox is a collection you can POST to and publish activities. this is ~doable as a self-contained microservice, but is there an even easier or more minimal way that requires even less overhead and maintenance? what is the sum total of all requirements needed to make it actually work?
@benpate that is what i'm trying to figure out for at least myself before writing up any recommendations for others. the hardest part for me so far is actually how to organize everything, what to name things, etc -- approaches and conventions moreso than tooling or technologies. i want it to be as easy or even easier to post to my website than to post to social media. a lot of that involves figuring out workable content models!
@benpate personally my goal is to guide people from fediverse into personal websites, not the other way around ^_^;