LoqiIt looks like we don't have a page for "refbacks" yet. Would you like to create it? (Or just say "refbacks is ____", a sentence describing the term)
Loqiuntag is sending an edit request to delete one or more tags (often person-tags) on someones post, where those (person-)tags possibly originated from someone else's tag-of reply post https://indieweb.org/untag
LoqiThis Week in the IndieWeb Audio Edition is a podcast by Marty McGuire that summarizes the This Week in the IndieWeb weekly digest newsletter https://indieweb.org/TWITIWAE
tantek__hey schmarty I tried to sign-in to Indie Web Ring but was rejected with a JSON error about no auth endpoint :sadface: - no rel=me / indielogin fallback?
schmartytantek: 🕸💍 only supports explicit authorization endpoints at the moment. I am interested in adding relme fallbacks at some point but I’m not aware of best practices for that and don’t want to default to sending everything through indielogin (because it’s not public)
[manton][aaronpk] That's one of my nitpicks with Mastodon. The feeds seem primarily designed for use in Mastodon. I do a little cleanup when they're loaded in Micro.blog.
[jgmac1106][schmarty] not sure it helps but here is the link to the next blog in a ring for the WP plugin: ttps://www.wordpressindiewebring.jgregorymcverry.com/?do=NEXT&id=1
schmartyjgmac1106: thanks! That helps me think things through. I looked at the code for the wp webring plugin you’re using. I am not quite sold on how it maintains order because it requires periodic upkeep that I am hoping to avoid.
[jgmac1106]its WP, old, and needs serious refactoring, but just trying to think about generating a first and next, needs to be some kind of order based on when blog signed in using indieauth
jmacLooking into why schmarty's "like" of one of my blog posts resulted in 4 schmarties in that post's facepile (http://fogknife.com/2018-06-28-i-attended-indieweb-summit-2018.html#webmentions), I see (unsurprisingly) that from the blog's perspective, the likes came from four different source URLs, so they are 4 different webmentions, and therefore (goes the erroneous logic) worth displaying separately.
aaronpki've definitely received "duplicate" likes before but usually it's because someone sends a like from their domain and then bridgy also sends their POSSE copy back
Loqi[cleverdevil]: aaronpk left you a message 17 hours, 52 minutes ago: it looks like there's an extra h-entry class on your watch post permalinks, and it confused my reply context
[manton][aaronpk] I've been thinking about expanding Micro.blog's IndieAuth to work for sites hosted elsewhere if the site URL is already verified in Micro.blog. This would overlap with what MyIndieAuth is going to do, I guess, but I think Micro.blog users are going to run into this. (Someone just tried it.)
aaronpkso you'd go to your micro.blog account and verify a domain like normal, then you'd go to that website and add the authorization_endpoint header to your page?
ludovicchabantHey there! Is there any existing project that handle POSSE-style x-posting. I'm thinking about something that reads an RSS feed, and posts any new items to Twitter/Mastodon/etc.
ludovicchabantI've found a couple ad-hoc things that do some of those, but I'm looking for a project that would have more extensibility in mind (i.e. adding more destination services to x-post to, etc.)
aaronpkludovicchabant: Bridgy Publish is basically that, but it reads the microformats on the page instead of the RSS feed, and it's triggered by webmention
ludovicchabantdoes this mean the former is if I want to copy that 3rd party SDK in my folder tree, and the latter is if I want to install it in my virtual environment?
ludovicchabantsnarfed : I'm following the Bridgy dev install (https://bridgy.readthedocs.io/en/master/) but I have no idea where `../../../src/gdata/src/gdata` is supposed to lead to? I can't figure out where my gcloud SDK python component got installed...
ludovicchabantyep I have! but I don't want to turn my website into an ActivityPub hub. I want to treat my Mastodon instance as a 3rd party silo just like I do with Twitter for instance
ludovicchabantthe thing is that I want clean separation of concerns. my website is its own thing (and is actually a statically generated website). the fact that I'm running my own instance of Mastodon or not should be irrelevant
snarfedaaronpk: oh yeah i mean server to server. so you'd still do the full bridgy fed setup on your web site, to make it pretend that it's a mastodon node
ludovicchabantwhat's the philosophical/technical design approach to Bridgy vs BridgyFed? I thought Bridgy was "repost your stuff to other places", whereas BridgyFed was "turn your blog into other things"?
snarfedpeople already confuse bridgy and bridgy fed, probably partly because the shared branding wasn't a great idea. adding mastodon would make that confusion even worse :P
snarfedregardless. ludovicchabant, to your original q, if you did pip install -r requirements.freeze.txt, you should have a few packages installed in local/src/ ... . that's where those symlinks point to
ludovicchabantI installed the gcloud SDK, which I apparently have to symlink to `local/src` but obviously `../../../src/gdata/src/gdata` doesn't exist for me since my clone of Bridgy is in a different place than yours
ludovicchabantand not only that, it might even have installed in a different place? I don't know... I'm on Ubuntu so who knows where `apt install gcloud-blah` installed stuff
ludovicchabantif anybody asks, you need PYTHONPATH to have `/usr/lib/google-cloud-sdk/platform/google_appengine` on Ubuntu if you're using the GCloud SDK instead of AppEngine SDK
schmartyjmac: sorry for all the likes. I think that was actually me fumbling with Indigenous and not being sure about whether it posted a like. There are new buttons on the bottom of a post preview that don’t show click feedback.
tantek__Good morning #indieweb-dev! While figuring out how to present and code /tag-of and /untag-of posts, I started to think about how they would fit in a broader context of /edit posts, all the way up to representing entire pull requests, and I was wondering if anyone else has thought about this since 2014
tantek__one thought I had coming back to it after all these years, is that since then we now have Micropub, which has a very detailed notion of updates
tantek__updates are essentially edits, and Micropub has figured out how to structure them. so perhaps we can work backwards from Micropub to what a good microformat representation of an update/edit would look like
tantek__I'm trying to make sure while coding something "simple" for /tag-of and /untag-of that it doesn't somehow interfere or contradict how generalized edits / pull-requests could/should work.
tantek__I'm particularly thinking of the conversation that aaronpk, manton, myself and others had during the Microsub session about how to treat p-summary as a fallback, and when to use the fallback (e.g. in some cases when there are additional properties you don't recognize or support)
tantek__the particular decision we made was if you get to the point of thinking you have an article or a note, if there are additional properties you don't recognize or support, then you should look for and use p-summary instead of treating the post as an article or note
tantek__so now I'm thinking how different kinds of edit posts could evove and how we could allow for incremental adoption of various kinds of edit posts
tantek__Because if someone really wants to assert transaction integrity, they could use a "pull request" post instead to imply they want the whole set of edits accepted, and that's a special kind of /collection post (at least as brainstormed so far), so I think we are ok with distinguishing that semantic at a high level
Loqiissue is a special kind of article post that is a reply to typically some source code, though potentially anything at a source control repository https://indieweb.org/issue
dougbealWhat would it look like to include a link for issue tracker discovery for a page associated with a project, so that clients could create an issue type easily?
snarfedalso re issue tracker discovery, i'm not sure there's a need for discovery like that. the usual flow is that a user is on an issue page and wants to reply, or is on the repo page and wants to create an issue. in both cases, they just reply like normal
dougbealI was thinking it tracker discovery would be great a way to close the loop - you are on a indieweb enabled webpage, notice a bug, pop open omnibear and file an issue
LoqiIt looks like we don't have a page for "source repository" yet. Would you like to create it? (Or just say "source repository is ____", a sentence describing the term)
LoqiVersioning is the practice of keeping previous versions of a post or other item available (possibly through a record of edits, AKA edit history) https://indieweb.org/Mercurial
LoqiIt looks like we don't have a page for "Source Code Hosting" yet. Would you like to create it? (Or just say "Source Code Hosting is ____", a sentence describing the term)