[tantek]aaronpk, sknebel, have to disagree "can be used by a user" is absolutely insufficient to consider something not jargon. Everything "can be used by a user" in conversation, whether they understand it or not.
aaronpkwebmention is "just" plumbing, except that people now talk about wanting to set up webmentions when they are not actually talking about the plumbing
[tantek]there's a natural tendency for folks to hype buzzwords (including jargon) as if it makes them sounds smarter and we must absolutely fight that because it is NOT inclusive at all in conversations
[tantek]jacky no, IndieWeb was specifically defined as a user-centric term, a quickly relatable shorthand that journalists have quoted from our homepage
aaronpki might actually want to weight the jargon detector by who is speaking too. like if I start in on a dev conversation i should get jumped on faster than someone brand new to the chat
aaronpkthe other thing to tweak is the text that Loqi says. for example maybe there's a way to include the explanation of why a term is considered jargon in the message
[tantek](and also a great reminder of how (at least for me) the creative "braindump a bunch of content (or code) to fill something out / get something out there" activity is a very different "mental mode" than the review, see, and fix errors mode)
sebselthe legal aspect he's pointing out? that might be a thing. But I do agree: the point that, if a silo goes away, it was all for nothing... that's just not valid.
sebselSo to quote the wiki: "The concept of a Generation allows us to group the experience of a group into a cluster that we can build tools for and create language to encourage growth."
petermolnarthis is really not the first time we want to do something about /generations, but soon [tantek] will show up, and tell us about the three column idea that still didn't present itself.
petermolnarso the question is: should the generations page stay because it's better, than nothing, or should it go, because it makes more harm, than good, in it's current form, regardless a replacement?
sebselbut he goes on to stating that there aren't really tutorials on how to do stuff, that most of the IndieWeb is just Gen1 creating things for themselves. (if I may summarize it like that)
LoqiIt looks like we don't have a page for "story behind generations, why did it came to be" yet. Would you like to create it? (Or just say "story behind generations, why did it came to be is ____", a sentence describing the term)
LoqiGenerations was a 2014-era summary of a spectrum of potential IndieWeb adopters (beyond the oversimplified developer/user dichotomy) in a series of clusters that were expected to progressively adopt the IndieWeb for themselves and help onboard others; subsequently the community grew, both across generations & in other ways, and is working on replacing the now obsolete generations model with something more inclusive and up to date https://indieweb.org/generations
[tantek]does this capture the essence of some of the critique while preserving it as a historical artifact of the community (it served its purpose at the time, and it's ok that it's no longer representative)
[tantek]thanks gRegorLove. I tried to incorporate what seemed to be the rough consensus of folks here in the community. if there's any particular aspect of essential criticism etc. missing, I'm still open to adding more. Or if it's a criticism detail, anyone can add to https://indieweb.org/generations#Criticism as well
@andrewtjâŠī¸ Thanks for sharing that. I do wonder whether the IndieWeb can move beyond its webdev bias.
Just on domain names, there was a time when free reg was more available. Maybe that's something to revisit. (Free in the style of http://lorikeet.id.au, not freenom or the like.) (twitter.com/_/status/1359274532435988482)