[tantek]petermolnar pretty sure I was collecting such criticism for a while (about indieweb itself rather than any particular CMS or plugin — which frankly that blog post was about the state of using WordPress for IndieWeb, e.g. none of it applied to say using micro.blog for IndieWeb)
LoqiIt looks like we don't have a page for "criticism" yet. Would you like to create it? (Or just say "criticism is ____", a sentence describing the term)
david.shanske.comcreated /2018/Nuremberg/notifications (+2016) "Created page with " ---- IndieWebCamp Nürnberg 2018 Session: notifications When: 2018-10-20 15:05 ---- == Participants == * All the people at the event :o == Notes == What do you want to get..."" (view diff)
@autiomaaGood article about the future of web authentication methods, together with implementation details.
"IndieAuth is a spiritual successor to OpenID, developed and maintained by the IndieWeb community and based on OAuth 2." (twitter.com/_/status/1329464376106119175)
aaronpk> It then goes on to describe "posts" as the essential building block of the site, and offers a bewildering and lengthy categorisation of the types of posts - https://indieweb.org/posts
[schmarty]there is some merit to complaints about licensing on many platforms but i agree. giving (for example) twitter a license to republish your stuff does not diminish your own rights to distribute that stuff.
aaronpkthere's definitely valid concerns with the various types of licenses you grant to various platforms by posting there. but virtually none of them even attempt to claim that you give up your own rights to the content
aaronpkas if oauth isn't actually the most prevalent mechanism out there and someone else wouldn't have chosen the same if they had chosen something on their own
petermolnarI was too focused on the opposite perspective - the controlling what can be done after licencing - to see this side; I'll keep this in mind.
aaronpkyeah that's what i mean that there's definitely a spectrum of the rights various silos *do* claim over your content, and some are particularly problematic like instagram, but that is still different than "no longer your content"
LoqiIt looks like we don't have a page for "ownership" yet. Would you like to create it? (Or just say "ownership is ____", a sentence describing the term)
Loqi[Peter Molnar] @kev sadly I can't reply with my own blog to your post any more, but the point is: you got it wrong.IndieWeb is not one thing, but many building blocks; each works serving a different purpose - hence the multiple plugins. BTW, there's nothing compli...
[schmarty]i am not sure it's in scope for the IndieWeb wiki but i think it would make sense to try and help folks focus on _figuring out what they want to do on the web_
[schmarty]i think a lot of folks find they agree with indieweb philosophies early on and then rush to find the lowest-effort solution to get the "most IndieWeb"
petermolnar(western people and their grading systems.... “In Okinawa, a belt means you don’t need a rope to hold your pants up. Daniel-san, karate is here [taps his head]. Karate is here [taps his heart]. Karate is never here [points to his belt]. Understand?”)
vilhalmerat work I've been helping forge a path for our internal docs that does the same sort of thing: organizing by goal instead of more structured tiers/whatever
[schmarty]a lot of the criticisms in this piece on gopher comes from an assumption that one needs all the features (and, corollary, that one should probably build it themselves)
[schmarty]the number and types of choices for even "simple"-sounding building blocks like "i want to support webmentions" actually can mean a world of different things.
vilhalmerafter I published my first blog post I realized there was literally nowhere I could point readers to see how a reader could use it without them doing a bunch of other up-front work to set one up
[schmarty]yeah. to be honest i almost find the h-entry stuff more useful as a first step for certain cases. like "i made a post replying to someone and i want it to show up good on their site because they have webmentions"
petermolnar[schmarty]: yes, but it's still a h-card. It helps to understand the microformats2 idea itself, it needs to exist for a h-entry, it's simple, plus is makes indieauth possible, so it makes sense as a first step.
[schmarty]maaaaybe some micropub clients? but we just wrote a replacement for that into the indieauth spec some weeks ago so i doubt we'll see much of that.
vilhalmerit may not matter if anything _actually_ uses the homepage h-card, it still provides that instant feedback that could hook someone into doing more
aaronpki think [schmarty] (and me) are saying that h-card by itself isn't a good entry point because there's not much you can actually do with it by itself
[tantek]the answer (upgrade) to /Generations is the three column layout stuff we've discussed and worked through some of the design, but it needs more dedicated work
[tantek]so I'm opposed to tearing down something where someone put in a lot of work, including community review and iteration, because people are taking potshots at it
[tantek]now I won't claim IndieMark is as "polished" as /Generations, but that's another thing that has a lot of thinking and work behind it, that can definitely continue using improvement
petermolnarwe sort of came to the conclusion that indiemark needs to be restructured around "what do you want to achieve" by topic and not numbers/scores
aaronpkgamification in the sense of "gotta catch em all" at least plays to the completionists and people who aren't completionists don't feel bad that they haven't caught them all
petermolnarthere is a page called "indiemark" with a wall of text, with a mix of tech/jargon from mutiple ideas of individual website, indieweb building blocks, all "arranged" in levels, which don't actually build on each other in their current form (see h-card vs h-entry ordering requirements above), gamified to the point where it loses all interest and fun.
vilhalmeron [tantek]'s point about it being aimed at gen 1/2 who actually do the dev, maybe it should call that out explicitly as well and point elsewhere for users who want a less code-driven process
[chrisaldrich]Part of the question for the IndieMark page is "Who is it for?" I would argue that it's meant for developers who are building from the ground up and who can build all the things for themselves. It's a reasonable structure for that, but if you're making a WordPress site as a side-hobby, it's generally useless...
[chrisaldrich]There's also the antipattern of the "checkbox comparison measure" seen in the gridded comparisons of software from the 90's... Let me make a grid of checkmarked features that my software supports that yours doesn't != my software is necessarily better than yours.
[KevinMarks]I think indiewebify.me is a better approach than indie mark as it narrates what each thing solves. It is still presented as a progression perhaps, but that could be edited. It also provides ways to check what you have done.
[chrisaldrich]Perhaps we could have a grocery store analogy with various IndieWeb wares on the shelf and you can browse the aisles to see what you'd like to "cook for yourself"? But first you need only a domain name/hosting to use as your grocery cart/carriage/basket...
tantek.comedited /IndieMark (+124) "note that current IndieMark is more about building features and thus audience is primarily for webdevs" (view diff)
[chrisaldrich]Kevin Quark's example of "leaving the indieweb" last week was really just a decision to put some things back on the shelf before he left the store, but he still "left" and had a site with a domain he controlled.