#aaronpki've been stuck implementing new stuff on it because of how old some of the codebase is, specifically the DB wrapper
#aaronpki should really make a list of all the things i want to do with it, then figure out whether to incrementally swap out bits or basically start over
#[snarfed]ugh, no easy answers there, that way lie dragons
#[snarfed]tricky though. wm.io is very clearly plumbing as a service right now. readers are user facing applications. very different use cases and audiences
#[snarfed]not that you're wrong, just...sounds complicated to get right
#aaronpktechnically aperture is also plumbing right now since it requires a reader app to be useful
#[snarfed]sure! so then personal architecture decision, where on the monolith/microservice spectrum do you want to be
#capjamesg[d]I decided to keep things separate to make it easier for me to manage everything.
#capjamesg[d]Also I built everything separately and at the time of building my webmention sender/receiver I didn't really know social readers existed as a concept.
#capjamesg[d]I can see a reader acting both as a reader and a webmention service.
#capjamesg[d]And it would give people one less thing to set up.
#capjamesg[d]But I don't know how that applies to webmention.io since it is such an established service and known for doing one thing really well.
#[schmarty]love this avatar issue and solution because it's yet another example is image proxies as a building block
#LoqiAn image proxy is a service that fetches and re-serves images from a new URL, used by IndieWeb sites to provide better performance, fidelity, and/or reliability of images embedded in posts https://indieweb.org/image_proxy
#[tantek]I still have too much distrust of random avatars to display them. the pixelation approach (I forget who proposed that) has some appeal, like maybe even down to 3x3 grid
#LoqiIt looks like we don't have a page for "pixelation" yet. Would you like to create it? (Or just say "pixelation is ____", a sentence describing the term)
#[manton]Curious if anyone else has looked at for IndieWeb (or WordPress block editor) implications.
neceve joined the channel
#@aswathWeb 1.01 - Indieauth, all the goodness of the three schemes and then some.
By the way, a Wallet in essence {Username, assword} and then a Password manager. Agree? (twitter.com/_/status/1486774754354810888)
#jackyI was definitely looking at it from the code side (how to convert a few paragraphs with /tags,/contacts and some sort of /reply-context and make that into something presentable)
#jackyI think the thing that's tripping me up is the need for it to be associated to an account
#jackywhich makes it more like a constant polling game
#jackyI do think that, in the same vein of something like /indieconfig, some sort of Web-based editor that's a bit WYIWYG-esque, can help people compose things for their site
#[manton]I think the challenge I’m running into is I don’t really understand what Hash actually is. 🙂 And so it’s not clear how tightly Block Protocol is part of its Hash roots or whether it’s actually something that would be useful as a component embedding thing for any platform.
#[manton]Probably should ignore this for a while. The name collision with hCore, etc. is funny, though, [jacky]. Hope they don’t make an hFeed.
#[tantek]on a positive note: does anyone have a /linktree page on their site (top level like that) that re-engineers the default styling of linktree using only HTML+CSS, no JS? (or consider it a "simple" IndieWeb hack project)
#[tantek]of course the goal would be to open source it as a standalone static one-pager that others could clone and edit the link/text contents
gRegor joined the channel
#[tantek]I’m asking because I’m considering doing it for my own site, and then linking from single-profile-URL silos with it that don't otherwise support rel=me