#Loqi[Tantek Çelik] #Twitter #developers heads-up:@Twitter just changed their backend & display auto-linkers (but not posting UI!) to link pathless ccTLD domains, when previously it did not.The API counts ttk.me as 23 (vs 6 before),but tweet UI does not!
#LoqiA permashortlink (abbreviated PSL) is a URL using a short-domain that expands to a permalink; on the IndieWeb, PSLs use personal short domains to expand to the same person's personal domain, thus minimizing the fragility often associated with shortlinks https://indieweb.org/PSL
#LoqiA permashortcitation (or permashortid), abbreviated as PSC is a short non-hyperlinked citation to a post permalink, in contrast to a permashortlink which does hyperlink to a post https://indieweb.org/psc
#j12tLooks like something's wrong with https://indiewebify.me/ "Web Sign In'. sdepolo failed to get it to pass for her site, although she links to and from Twitter. And it does not validate for me either, claiming that I'm not linking back from Twitter, but I do: twitter.com/Johannes_Ernst points to https://t.co/kcd30NSNtT which redirects to https://upon2020.com/ which redirects to https://upon2020.com/blog/ which has my rel=me
#@rmondelloiOS 11.3 and macOS 10.13.4 include Service Workers — a powerful specification that allows background scripts to power offline web applications. iOS 11.3 also consults Web App Manifest when adding web apps to the home screen. (twitter.com/_/status/956256845311590400)
#sknebelkeeping a list of bad IPs for defense purporses is different from keeping logs of all your visitors
#ZegnatI find the IP adress-as-personal-information thing obvious on one hand, annoying on the other. Not sure how this would be for e.g. ban lists.
#sknebel(It's obviously also one of those "who's gonna sue you for it if you aren't a government or big company, if they have no idea if the court is going to agree this time" things)
#petermolnarthe ban list is exactly what we're talking about
#sknebelI'd expect a ban list to be treated differently, since a) you as an operator have a clear reason why you need to keep it, b) normal users should not appear on it without reason, c) you collect very little auxillary data.
#petermolnarok, but if you don't have the auxillary data, you can't tell why the ip is banned
#[tantek]This is how and why we the indieweb can and will catch up and surpass the silos in terms of UX and innovation
#sknebelfrom the second one I found "Google has become 100% competitor-focused rather than customer focused." a good point
#[tantek]1. Our innovation is fundamental distributed and decentralized. Despite that yes we have a community, it’s all opt-in by the minute, everyone chooses to be here or not.
#[tantek]Nearly zero cost to staying/leaving/returning so you do you and innovate as it works best for your site.
#[tantek]2. We are constantly adding new innovators. New devs are showing up pretty much every week with their own perspectives and priorities. And we encourage everyone to document their own priorities publicly with Itches lists etc per /wikify
#[tantek]3. We focus any “centralization” work (read: standards) on the minimum necessary to make our actual innovations (UX, user features) interoperate.
#[tantek]This gets to something I’ve said several times when people want a new microformat for x or a new eel value for y - what is the usecase?
#[tantek]But really, what is the *interop* usecase? Without an interop usecase, no need to standardize.
#[tantek]“Interop usecase” is a broader way of saying what is both the publishing use case and consuming code usecase - you need both. Interop is why.
#[tantek]All of the above is also a good reason and driver to minimize feature sets of standards themselves. To prefer smaller standards. Minimum viable building blocks. Each of which provides utility on its own, and hopefully when combined provides new utility that by themselves they did not.
#[tantek]Lastly, by keeping the innovation as distributed as possible, it makes it less and less possible (read: more expensive, unworldly, and too weird looking to convince checkwriters) to “acquihire” or “acquishutdown” the indieweb. Another advantage over monocultures.
#[tantek]Which is also why we must keep growing, mentoring, and embracing having more and more different thinking innovators. Makes it much harder to acquihire individuals as a way of shutting down a community (no evidence this is happening yet, unlike what happened to AS etc in mid/late 2000s with the old “social web” in crowd being hired away by Google, FB, Twitter etc)
#[tantek]Also a very good reason to avoid and discourage any kind of in-crowd vs not divisions, by doing the opposite as we do. Welcoming new folks “in” immediately and respecting and even empowering new/different opinions (even if imperfectly so, self included) as sources of breadth & strength for the community.
#[tantek]The flip side of that is that yes, just like the meta seeming contradiction but consistent in practice of not tolerating intolerance (per code-of-conduct), not tolerating monoculture attitudes, sales pitches, appeals to tradition, or worse appeals to “if you dont do it my old way then why do you hate me”.
#[tantek]Yes any of us can innovate on our own sites differently than anyone else, and no it does not mean we hate nor does it take away from other approaches. It means we are innovating with our UX and user features in a way the makes the most sense and importance to ourselves (self dog food). That exploration of diversity by implementing and using (show rather than tell), strengthens the community and frankly makes it increasingly more fun and intere
#schmarty^ tantek: this seems very on-topic and probably would make a very good post!
#voxpelliTogether looks really neat, nice to see good progress in that space since I last was around :)
#Loqivoxpelli: tantek left you a message on 2017-09-26 at 9:48pm UTC: I'm experimenting with a "follow" webaction on my homepage - take a look and let me know if you think /indie-config needs any changes to support handling "follow" and passing it to your website to handle
#KartikPrabhu[cleverdevil]: seems to be borrowing Google's aesthetic
#[cleverdevil]@KartikPrabhu yeah, Together uses a Google Material Design style/theme.
#KartikPrabhu[cleverdevil]: yeah it was a minor point. The "circle with the +" always reminds me of Google products. But I am sure that can be changed once Together is more mature
#@_am1tExperimentation continues with IndieWeb projects – over to Webmentions. It is a really wonderful concept which enables responses to a post to be written on one’s own websit. As Jeremy Keith wrote in one of his posts:
Basically, it’s an equivalent to pingback. Let’s say I wr… (twitter.com/_/status/956619521279844352)
EmreSokullu and [cleverdevil] joined the channel
#[cleverdevil]So, debugging an issue with manton on his new Sunlit 2.0 iOS app.
#[cleverdevil]When his app attempts to publish to my Known instance via Micropub, for some reason the HTML is getting escaped rather than accepted as the raw content.
#[cleverdevil]I've got a simple test script that publishes HTML via Micropub and I am seeing the same thing.
#[cleverdevil]Not sure if its a bug in Known, or if we're *both* doing something silly.
snarfed, j4y_funabashi, KartikPrabhu, chrisaldrich, j12t and j12t_ joined the channel
#www.boffosocko.comedited /Webmention (+2132) "moved publishing software and services from wm-developer page (reduced duplicates); fixed TOC table depth for publishing software section" (view diff)
#www.boffosocko.comedited /Webmention-developer () "(-3178) moved publishing software and services to main wm page (and reduced the duplicates); tweaked TOC level for Libraries section" (view diff)
[manton] joined the channel
#[manton]This Micropub plain text vs. HTML issue is kind of similar to a discussion we had here about supporting or requiring Markdown. In other words, should a server be able to limit the formats it accepts.
#Loqi[manton]: gRegorLove left you a message 2 weeks, 1 day ago: Where can we file bugs for micro.blog?
#[manton]I don't really see anything in the spec that says HTML isn't allowed in form-encoded POSTs.
#KartikPrabhu[manton]: sure. but the server is then free to interpret them as plain-text
#KartikPrabhuin a form-encoded POST request there is no way for the server to distinguish between plain text and markup
#[manton]That's true. I'm just trying to understand what is in the spec vs. what is an implementation detail, like Known not accepting HTML.
#sknebelit's indirectly in the spec by saying that it follows mf2 semantics, where unescaped html only happen in that nested form
#sknebelso all other text is assumed to be plain text
#sknebel(you are right though, the spec could call that out clearer. guess that was "too obvious" at some point?)
#[manton]It's not clear to me. I think having 2 forms complicates things a little... As one example, the spec says a Micropub client that creates posts _must_ support sending form requests. But what if a client has to send HTML?
#[manton]If I switch to sending JSON, then technically my client won't be conforming anymore.
[cleverdevil] joined the channel
#[cleverdevil]It would be nice to be able to send HTML via the form-encoded method.
#sknebelyou'd have to ask one of the people involved with the spec-making process about the "conforming" bit (e.g. aaronpk)
#sknebelthe form-encoded form is the simpler one that from what I understand intentionally doesn't support all cases since it got to complicated otherwise
#[manton]Maybe if there was a way to query the server for whether it preferred or supported form-encoded vs. JSON, that would help. Not sure... We don't need to debate it now, necessarily, but I do want my apps to be more compatible.
#sknebelI think the most common behaviour for newly written clients that try to be compatible is to use form-encoded where possible and switch to JSON when it's not
KartikPrabhu joined the channel
#sknebelon the other hand, I have no overview how large the set of servers that don't support JSON is, I *think* the ones that are not just private projects largely do JSON
#aaronpkIt'll get really messy if we try to make the formencoded content anything except plain text.
#aaronpkYou *could* have a server that interprets the content as markdown, since markdown is close to plain text, but only if it returns the markdown source when queried, and only if you're okay with some clients showing the markdown source when editing
#aaronpkIf you look at my text notes with bullet lists, I actually author those by typing * but my server renders them with •
#aaronpkThe form encoded request is meant to be the simple version just to get started, but as soon as you want to do any "fancy" stuff like posting checkins or dealing with html content then JSON lets us be more explicit about the request
#[cleverdevil]Fair enough. Its definitely still simple. Just not *as* simple.
#[cleverdevil]One piece of feedback on the spec: it could use a lot more fully-defined examples with MF2 JSON.
#[cleverdevil]In fact, if there could be an example that exhibits every single property for every single type of content that can be created, that would be amazing.
#[eddie]eddie mentioned a file: Image uploaded from iOS.jpg.
[manton] joined the channel
#[manton]eddie Let me know if there's anything I need to look at. Looks like the feed is correct on first glance.
#[eddie]Thanks manton. I’m guessing it’s just deciding whether the decoding happens in a Microsub Server or a reader interface. I think, as you said, the feed is probably fine