|
Top-level
 I define IndieWeb-style federation as a federation that is based on the following: 1. Pull-based. So, you check for the new stuff, instead of being notified of the new stuff. 2. Microformat-based. So, you parse HTML a lot. All of this allows for less intensive federation, while also letting static federating sites to exist. 8 comments
 @bouncepaw @neauoire @inscript I've seen that before, but it hasn't felt very actionable. How do you imagine people interacting with your new site once they create it? @akkartik @neauoire @inscript I want to build a federation of Betulae and Mycorrhizae, so they can interlink and transclude each others' content. For example, I have a category named Cats on my Betula. And you do, but it's named Felines. On my Betula, I say: βHey, there's this page out there which also has cats! Federate with it!β. Then my Betula GETs your Felines, parses it, and shows them nearby my Cats. Data updated once a day. @bouncepaw @neauoire @inscript Oh I see. I'm familiar with https://wiki.c2.com/?SisterSites. Which of those microformats helps with this? @akkartik @neauoire @inscript re: sister sites. I once experimented with Bill Seitz's twin pages system: https://melanocarpa.lesarbr.es/hypha/bill_seitz_twin_pages I'm part of the system, though I don't really see it often. > Looking at adoption in the first few months feels premature. I've never said I'm not on with the adoption of merv.news. The adoption is alright. I'm just pointing out, that I'm actually using it. |
Gregory's Server
@bouncepaw @neauoire @inscript Interesting, is there a link where I can learn more about how to pull, and the microformats involved?