[grantcodes]Uhh well it's kind of a mystery how it works tbh, I think it is chrome only for now and it needs to be installed as a pwa. But I can definitely share to it on android so it works, but I doubt it currently works on anything apart from android
[cleverdevil]Hey, I am realllly happy with what I ended up working on, but it definitely wasn't anything that I had actually planned going into the summit!
[cleverdevil][grantcodes] hmm, I just noticed that in "classic" layout in the latest Together, the "previous | next | close" bar at the bottom of the view obscures the actions (like, repost, etc.).
[tantek][cleverdevil] I too ended up working on something I had not planned to do so. It really is interesting / unpredictable how the various ideas from day 1 of summit inspire us. Or even the morning / lunch conversations at day 2!
[cleverdevil][tantek] Totally agreed, and its been true for me every single year. Two years ago, Grant and I prototyped Together on a whiteboard, and that became our project. Last year, a conversation in the hallway track with Chris Aldrich inspired me to create Indiepaper on hack day.
[jgmac1106]end of the day I was like.....oh yeah...I totally wanted to do a session on productivity and make a to-do list easier for me....ended up chasing an extra brace trying subgrid....
[jgmac1106]its strange going to miss the constraint of matching character count as a creativity tool but also will have more content time for less code at same time
[grantcodes]Hmm [cleverdevil] yeah it does look like it is fixed instead of sticky so doesn't have the needed padding. Kinda weird it doesn't work. Looks good on macos though
[tantek]My experience on hack day was quite unique from past hack days. While working on implementing displaying a richer reply context seemed like a "can do in a couple of hours, especially with consulting people for quick questions", I decided to double-check my approach to storing the information (from a flat file perspective) by first checking what others had done/built (and why).
[tantek]I think I knew [schmarty] also had a particular approach to storage so I asked the questions that I thought would reveal answers either reinforcing my approach, provide sensible alternatives, or new information questioning my assumptions.
[tantek]That led to a higher level discussion about needing to partition (quarantine) information differently depending on where it came from, how (due to your own action, or from someone else's action), and the potential complexity of it
[tantek]1 due to your own action, something you get a chance to see/preview first (before storing) - like previewing the information in a reply context
[tantek]2 due to external action (like receiving a webmention) and a simple "response" (like, repost, reacji) where the "content" is likely innocuous (at worst a random emoji)
[tantek]3 due to external, and richer information about the response like author name (could have offensive text, how big? needs sanitizing?) and author image (could be offensive image, big size etc.)
[schmarty]my project-day ended up coming out of this discussion, and the idea that you should be able to approve whatever you're about to post, including any /link-preview or /reply-context info.
LoqiIt looks like we don't have a page for "unlock protocol" yet. Would you like to create it?_x (Or just say "unlock protocol is ____", a sentence describing the term)
[tantek]Out of that discussion of where to store your own content (stuff you create), vs stuff of other's you reference, e.g. according to various quarantine levels 1-4 depending on how "bad" it could be / damage it could cause, we refocused on what were the possible problems with reply-context information that might motivate changing that information
Loqi[Tantek Çelik] #IndieWeb Summit:
reply-contexts should be user-editable in posting UIs
in-reply-to h-cite property: reason, action
* name+summary: too long, truncate
* dt-published: 1969 or future or wrong timezone, use present time
* author name: Twitter names/pro...
[tantek]as soon as "user editing" is added to the flow of information, it becomes something you want to save/own for yourself, something of your creation that you typically can't recreate by clearing a cache and rebuilding it from the web (or even archive.org)
[tantek]thus from a storage perspective, it starts to look much more like something you create rather than something you retrieved, which means for a reply-context, storing it along with your reply, rather than in a side-structure or side-file. for static storage that uses microformats, that would mean an h-cite for the reply-context, similar to the how to for publishing: https://indieweb.org/reply-context#Markup
[tantek]looping back to the start, I was (re)considering my approach to storing the [reply-context] information. With just the primary use-case of presenting reply-context information, it made more sense to store it somewhere on the side other than my posts (per the Level 1) analysis above, though other possibilities would be ok.
[jgmac1106]where do we capture everyone's project day descriptions on the wiki..or better yet where do we collect the blog posts where people reflect on their project day demos?
[tantek]Adding the use-case of editing the information changed enough about the nature of what is being stored that it now became important to store it along with the posts! This was my original plan "save that reply-context info inside post storage alongside links to POSSE copies" but for insufficient reasons (convenience of implementation) that ignored the challenge of information from other sources, which was why I wanted to question that plan by ta
[tantek]I bring this up in dev because ultimately I'm thinking through the challenges of "how to store stuff from other people's sites" which is a key underpinning of handling all sorts of protocols like Webmention and also all the peer to peer user interaction scenarios
Loqiaaronpk: sknebel left you a message 1 day, 10 hours ago: we have new AutoAuth issues, would love feedback on those / if you have time for a virtual session on AutoAuth e.g. on one of the next few weekends I'd be interested in running one
[tantek]including the more challenging scenarios like dealing with abuse etc. which I think need to be thought through all the way down to the storage level
[tantek]how we partition the storage of things makes a big difference about how it can scale, prioritizing what you back-up (since nothing is "instant") etc.
[schmarty]heh, we have been talking recently at adafruit about ways to share data between our sites like the shop (buy stuff) and learn (docs and howtos) and i have been pushing mf2
[schmarty]so i told him there's an alternative, as long as we use a parser that supports it (the use of `property` that we discussed and that somebody integrated at 2018 Berlin)
[tantek]it predated the current JS-JS-JS trendiness among programmers but comes from the same place. ew, mixing data in markup which is "just" a print output for display
[tantek]systems that are storing actual content in opaque JS-accessed databases are likely to have that data disappear over time, leaving nothing but those aforementioned JSON-island summaries for people to try to discern WTH a page was about
GWGRe the external content subject... I store them in the post as h-cites,. but I have been thinking of storing them in a linked data structure for better querying
[tantek]GWG, in general, consider avoiding the phrase "linked data" and the term "semantic" (especially when uppercase "Semantic") unless you're deliberately trying to refer to RDFisms
[tantek]wow the Google dfn kinda nailed it: "a custom, principle, or belief distinguishing a particular class or group of people, especially a long-standing one regarded as outmoded or no longer important."
[tantek]I'm also considering the case of not wanting to store *any* reply-context information beyond the URL because all of the specific info is not something I want in my storage / archives. E.g. confrontational replies to bad actors
Loqi301 (301 Moved Permanently) is an HTTP status code returned from a web server to indicate the URL is permanently redirected to another URL https://indieweb.org/301
chrisaldrichDo we have a more generic web-specific page for redirect? Surely amidst all the CMS changes folks have gone through, there would be more documentation than ^^
chrisaldrichI just got an email from Pixabay.com asking me to fix a URL on my site to redirect, presumably because they changed their URL design (or CMS)...
chrisaldrichThey actually wrote "Updating to the new URL avoids broken links, which can be a bad user experience and also harmful to your site's relationship with Google."
jgmac1106[m]But wonder if a Micropub client could be created drop in url, select dt-published range. Parse post for reply, the reply for a reply, etc publish one h-entry with child h-entries
[aaronpk]i also forgot to describe the actually cool part of that at summit, it's more than just lazy-loaded, it's only loaded if the image comes on screen
[aaronpk]yeah! also cause it can be smarter about loading them just before they become visible instead of the way mine works with triggering as soon as they become visible