LoqiIt looks like we don't have a page for "content warnings" yet. Would you like to create it? (Or just say "content warnings is ____", a sentence describing the term)
Loqicontent warning is a feature of a post create UI where an author can hide by default some or all of the primary content of a post due to some concern about the nature of the content https://indieweb.org/content_warning
LoqiIt looks like we don't have a page for "content warnings" yet. Would you like to create it? (Or just say "content warnings is ____", a sentence describing the term)
sivyi’m at the point where i’m trying to make sure i have individual function tests done before I start trying to write the main “does this blargh of HTML return the right data object”
gRegorLoveI'm working on making the first-time indiebookclub sign in more user friendly and adding delete scope as an option. Thoughts on this? https://imgur.com/sfxhAj1
@grantcodes#100days 60 - Made a small but long overdue change to my site, so that it only sends me notifications about new webmentions. My notifications were filling up with duplicate mentions because of people sending them every time they build their site (which is totally fine) (twitter.com/_/status/1278250750930489347)
KartikPrabhu, [jgmac1106], [itsjustk], [Ana_Rodrigues], hs0ucy, [fluffy], [KevinMarks], Zegnat and Kaja_ joined the channel
@mcintyre321↩️ We should all switch to self hosted blogs, with WebMention based 'following' widgets, and RSS reader driven off those. i.e. replicate a friend list / feed using open standards (twitter.com/_/status/1278296178665324544)
[jgmac1106], [itsjustk], sknebel, Zegnat, [jeremycherfas], hs0ucy and geoffo joined the channel
[tantek]I feel there are some important lessons here that we can pre-emptively learn from both for individual projects and IndieWeb dev stuff in general.
[tantek]I’m wondering if we can perhaps develop a proactively anti-bullying “how to contribute code to IndieWeb” kinda guide for developers perhaps that has all the developer-specific stuff that we don’t need to confuse the general code of conduct with
[tantek]Exactly cjw6k, it's awkward messy unobvious stuff that if we were to help with even minimal guidelines, it would helps set more positive defaults, so that at least folks that want to do the right thing but aren't sure how would have some guidance they could use.
[tantek]interesting insight that perhaps the aggressive bully is Torvalds himself, and in that case a good warning against BDFL-style governance in general
Loqi[gRegorLove] I'm working on making the first-time indiebookclub sign in more user friendly and adding delete scope as an option. Thoughts on this? https://imgur.com/sfxhAj1
swentelhmm, never looked at this from that perspective. I just send all scopes, but then I assume that the user is able to untoggle the asked scopes on their authorize form.
[tantek]or consider progressive scoping? that is start with only create scope, and then if/when a user tries to delete something on indiebookclub, then and only then ask for the delete scope (since then it's tied to an immediate user-expressed need/task)
Loqiincremental authorization is the practice, even pattern, of only requesting permissions when they are needed for the current user-action, for example, when requesting OAuth authorization, read, write, delete permission, or similarly with Micropub https://indieweb.org/incremental_authorization
[tantek]when I first used Twitter auth for RelMeAuth sign-in, I started with just ID-only auth, then provided a flow for users to upgrade to posting access
[snarfed]re incremental authorization, bridgy does a very coarse version of this, initially just read permissions for backfeed, later upgradeable to write for publish
[chrisaldrich][gRegorLove] I like the look of it, but you might want to use a word other than "scopes" which seems more dev and less user-friendly. Maybe something like "access to"...
gRegorLoveYeah, first time someone clicks "delete" they'll see something similar to that screenshot, but with "indiebookclub needs permission to delete posts on your site." and the authorize button again.