nickodd, geoffo, KartikPrabhu, wagle, gRegorLove, cweiske, [tantek], vika_nezrimaya, moppy, [Murray] and [KevinMarks] joined the channel; nickodd left the channel
#[itsjustk]its not so much bad, as it is...pretty useless, its basically a reddit designed especially for recruiters to wax lyrical about themselves 😛
#[itsjustk]actually more facebook then reddit actually
#[itsjustk]But its basically supposed to be this big jobs platform
[KevinMarks] joined the channel
#[KevinMarks]it was originally a social network to ask for referrals to people through intermediaries, but now it's a recruiter funded resume silo
#[KevinMarks]you can still big up your connections through it
#[KevinMarks]one thing it does have is verified historic employer emails, so it knows that I have in the past had email addresses at Apple and Google (even though I don't any more)
#[KevinMarks]( I was one of the first 100 users of it, so it has me connected to the founders)
ketudb, mlncn9, MrHyde_, [Ana_Rodrigues], dckc, [Jose_Leiva] and [tantek] joined the channel
#jmacAm I correct that "utility" posts like RSVPs and Bookmarks and such tend to lack `e-content` microformats?
[schmarty] joined the channel
#[schmarty]jmac: you'd have to look at examples, but i feel pretty confident that RSVPs usually have content.
#[schmarty]and bookmarks may have content snippets or comments.
#jmacI'll admit I was just looking at wiki examples
#jmacMy reason to ask is tuning Whim's "send webmentions to everything at [given URL] that looks deserving" feature. It currently extracts all links from the first h-entry's e/p-content, and does nothing if it can't find one. I am under the impression that just using al links found under the h-entry might be more correct behavior.
#jmac(This is assuming that this feature is even a good idea at all, of course...)
#jmac(More to the point I talked about this a bit at a recent meetup at GWG suggested I needed to cast that net a bit wider)
[snarfed] joined the channel
#[snarfed]yeah, generally you want a good reason to do anything other than "all links on the page," minus maybe header, footer, other common template links
#[snarfed]out of curiosity, why try to prune down the links to send wms too? i'm guessing not load
#jmacExactly, I explicitly want to not send wms to one's own navbar and such
#jmacContaining it to the content of h-entry sounds like the best idea? A post of any flavor is generally always contained in one, yeah?
#[snarfed]wms are expected to be idempotent, there's generally no harm in sending/resending them too widely
#[snarfed]esp since anyone in the wild can send one to/from your site too
#jmacThe failure I'm envisioning: I do this with a post on my own blog, which has a "ten recent posts" sidebar, resulting in all those posts getting webmentions, which they all happily confirm and display, meaninglessly
#[snarfed]right. as the site owner, you get to handle that however you want. just remember that it's technically possible for a random third party to send a wm from your home page to those posts too. unlikely though, you can probably ignore that until/if it happens the first time
#jmacIs there prior art about conditionally checking for "benign cruft" webmentions like this? Stuff that is from legit sources, and not spam, but not meaningful and not worth display?
#jmacMaybe I *should* skip self-wms... it'd be easy enough (and it would test Whim's blocklist feature, so hey). I kinda don't want to because I like the purely accidental "related posts" feature that self-wms otherwise create!
#[schmarty]jmac: this is an interesting webmention-handling case! webmention-the-spec only requires that the source page link to the target page, but whether the target system should actually do something about that is very complicated and i would argue very under-documented.
[KevinMarks] joined the channel
#[KevinMarks]if someone sends a webmention to every link on a tag page, that could be annoying
#jmacI mean the community consensus right now seems to be "If it's valid and we're not blocking the source domain, scan the source content for microformats and then display it as best we can, the end"
#jmacI'd be interested to learn of more complex deployments than that
#[manton]Thought some of y’all would be interested in this… We are working on a rewrite of our photo app Sunlit. It supports Micropub and will be completely open source. Hope to wrap up a few things and make the code public soon. https://www.manton.org/2020/07/13/sneak-peek-at.html
b3u, KartikPrabhu, justache, [grantcodes], geoffo, [KevinMarks] and [tantek] joined the channel; nickodd left the channel
#[tantek]Snarfed, I got a report that explicit linking of GitHub @-names in an issue, e.g. as I did in https://tantek.com/2020/191/b2/ when POSSEd to GitHub via Bridgy, does not provide any of the usual @-mention UX, e.g.: (1) disables github's normal UI for usernames and (2) more importantly, disables the notification and email filtering behavior of mentioning someone by name (my POSSE copy of that issue has been subsequently edited to remove the
#Loqi[tantek] #872 Bridgy publish to GitHub should turn profile URL links into mentions
#[tantek]technically it's a GitHub bug (shouldn't matter *how* an author made an @-mention link, it should work the same), however it's something we could work around.
#[tantek]Thanks for the GitHub issue reminder, yes that would be one workaround
#[snarfed]feel free to revise or file another if you know how it should work! (sounds like we're maybe not quite there yet though?)
#[tantek]I may try a plain "@-mention" next to see if GitHub has fixed not autolinking those
#[tantek]if not then that issue 872 is still the best workaround we have so far
#jackytbh I think GitHub's right here. It's treating plain-text as Markdown, their internal format of choice versus allowing arbitrary linkage to something else. Like with the format you've given, you could make it look like it linked to @jalcine but send it to https://github.com/totally-not-jalcine when the link's clicked since it keeps it as a link