[tantek]^ capjamesg this is an example of the kind of conversation that keeps happening in main (#indieweb) that is discouraging to new folks who have no desire to be overwhelmed by jargon and acronyms and just want their own place on the web they can use and control instead of social media
[tantek][snarfed] [KevinMarks] to be direct, every time you mention markup (rel=me etc.) or names of feed formats your dissuading new folks who do not want to focus on technical details from participating in conversations here, and you are reinforcing a misperception that indieweb is only for developers or those who want to focus on technical details.
[tantek]Can I please encourage you both to take conversations to #indieweb-dev BEFORE you start mentioning markup or especially in response to when others do so and direct them #indieweb-dev end up reinforcing the problem by not noticing that this is not the dev channel.
[tantek][snarfed] in particular for BridgyFed it seems like most of the time support questions about BF end up in #indieweb-dev territory very quickly so perhaps consider immediately taking BridgyFed support chats to #indieweb-dev?
[snarfed]I so still hope recent topics like content moderation, context collapse, user expectations of where content flows and appears, etc belong here, because non-dev people are exactly who I want to think about and talk through/with about those
[tantek]for the specifics you mentioned [snarfed], agreed that content moderation is on topic here. "context collapse" feels borderline academic / jargony so I'd err on the side of #indieweb-dev for that. user expectations of where content flows and appears absolutely feels directly on topic.
[tantek]and let's please avoid the term/phrase 'non-dev' pre prior discussion of how that can both be othering, and in fact is inaccurate, as "not wanting to discuss / hear / focus on technical topics != not a developer". Plenty of developers also want to be able to focus on solving user problems without jumping into technical details.
[tantek]does anyone keep an *open* (like publicly accessible or perhaps web-sign-in gated) list of ideas, snippets, or even drafts of posts they are in the process of writing up, but NOT published / pushed to their main feed (or even archives)? like something that's literally a list of a sort with no individual permalinks for the specific items because they're supposed to be ephemeral
[tantek]my public use-case is that I come up with (and try to capture) many more ideas about even short notes / posts faster than I have time to write-up and post them, and yet if someone else were see them and post about them instead, I wouldn't actually mind (it would be nice to get a hat-tip or inspo or something but not required).
[tantek]my rough thinking is an open queue of such captures on my personal site that don't show up "on main" as it were. those that are curious can go dig there but nothing there gets broadcast or shows up in my post archives either.
[snarfed]your approach is the more sophisticated aaronpk style: post per idea, with an internal tag that puts them into a separate collection feed and omits them from the home page feed
[tantek]I mean, my approach today is fairly "dumb/simple" too, either it goes into a never-ending textfile (at the start or end depending on if it feels like a current-relevant or get-to-it-someday idea), or I use my /tinbox User: wiki page here to collect them at the end
[tantek]the first two of those (stored, represented) are plumbing discussions better for #indieweb-dev any way and detract from the point of the feature IMO
[tantek]yes I mean even if it were "just" literal plain text with asterisks * for list items I would be fine with that for display. the point is it is supposed to be rough and in-progress, there is no need for it to be "pretty" in anyway. just readable and copy/pasteable, that's it
[tantek][snarfed] your lists feel like they have a more semi-permanent intent to them, and thus are understandably more curated & refined for reading by others
[snarfed]some of that is probably the content. ideas are much fuzzier and less comfortable to show publicly than concrete items like books or movies or quotes
[tantek]I keep such a list offline as well, however, the longer I am doing this, the more I realize most of those to-write ideas/posts would be fine in raw form in a public lists for others to consider, pick-up, run with etc.
[0x3b0b]I have a file which I don't currently make public, in the same place where I write post drafts, that was meant to be my idea list. I've made two mistakes with it; first, it's only convenient for me to add to when I'm at home, and second, I think for me personally something a little more structured might work better. Not sure about that part though; I may have to try both ways to find out.
[tantek][snarfed] one such set of public to-do/ephemeral lists I am already keeping of "things to write/create" is my Wikipedia list of articles etc. to create: https://en.wikipedia.org/wiki/User:Tantek#articles_to_create which made total sense to me to keep there publicly since Wikipedia is a public collaborative project and if someone else decides to make one of those pages and use my notes then great! Less work for me π
[tantek]I think in general the "something a little more structured might work better" turns out to be false by way of making you waste way more time with "organizing" ideas than actually capturing, iterating, and publishing them
[tantek]see every "productivity manager" tool ever, where people spend way more time tagging, categorizing, re-ordering, rewording to-do items than actually *doing* them
gRegorI had basically copied it from Netflix years ago, since then have put in some using either IMDB links or justwatch.com links, since that works pretty well at showing which services currently are streaming a title