petermolnarmy semi-static abomination generator has reached 4.0: I bought into webmention.io, I generate PHP from Python/Jinja2, and I finally do ugly Python with nested classes.
petermolnarsknebel: turned out search is tricky. I wanted to go "full static" and looked into js search solutions, but the smallest index I could come up with was 7+MB. So in the end, I kept the sqlite approach: the sqlite db itself is populated by python at build, and an extremely simple PHP will parse the query and query the db in read-only mode, avoiding the lock issue php usually have with sqlite.
jgmac1106my feeds don’t refresh on Indigenous for Android. Still just have blank screen. Do need to connect my Apeture account in anyway? I still get a 401 error if I click “refresh syndication links” not sure if that is connected, what web based social reader should I play with?
ZachOglesby[m][eddie]: together has a setting to syndicate automatically likes replies and more. Is that something you have thought about? Should I create an issue for it? (I have not looked yet to see if was already a ticket). The share sheet has no option for syndication so I think that kind of thing would be helpful.
[eddie]ZachOglesby[m] Yeah I think that's a great idea. I (think) I have an issue for that in my feature tracker, but I'll check and if not, I'll add it in.
[eddie]!tell [chrisaldrich] Your h-event seems to be embedded within your h-entry, which means xray and quill sees your event as an entry, and I can't RSVP easily 😞
@HelloNaamio↩️ Fully open source under MIT License, and aiming for full standards compliance for compatibility between any and all projects supporting #ActivityPub and #Webmention. We don't want to lock anyone in, or out. (twitter.com/_/status/1021427801545682961)
@HelloNaamio@jaywink Fully open source under MIT License, and aiming for full standards compliance for compatibility between any and all projects supporting #ActivityPub and #Webmention. We don't want to lock anyone in, or out. (twitter.com/_/status/1021427801545682961)
[chrisaldrich]I get a success screen [cleverdevil] (which kind of surprised me given some of the recent pickiness and my inability to get things on the microsub side working when I tried last week)
boffosocko.comedited /book (+820) "Kathleen Fitzpatrick, James Shelley examples; see also links for personal library, samizdat, and education; move TOC" (view diff)
[eddie]!tell aaronpk Does webmention.io have any support for Salmention or to start enabling that should I fetch the page contents whenever I get an updated Webmention ping from webmention.io?
[eddie]Webmention.io processes webmention pings and delivers fat pings with the webmention info. If it included salmention support, that would mean that there was some way to retrieve the downstream webmentions through the webmention pings
Loqisnarfed: [eddie] left you a message 21 minutes ago: currently I have just done nothing on it. API seems like a good solution though, I’ll look into that 🙂 Thanks
schmartymayo: i think you hit on the way people are currently using mp-destination. a micropub client sends a request to your singular micropub endpoint, and that endpoint interprets mp-destination and what to do with it
mayoschmarty: right ok. So if I were using Aperture (which supports endpoint per channel, with extra headers), I'd have to theoretically poppulate my micropub endpoint mp-destination config with each microsub channel's micrppub url, and then internally append the right headers when making those requests.
schmartymayo: right, your micropub endpoint would be acting as a proxy to those endpoints, keeping track of whatever info it needed to successfully pass the messages along.
mayoschmarty: hmm ok. feels like microsub should eventually have a sane way of exposing this, otherwise it's lot of manual work. especially for people with less tech inclination
sknebelA nonce is in cryptography a code that's only used once, e.g. to protect authentication flows against replay attacks or to be used as a token to protect against Cross-Site Request Forgery.
tantek__wow this: "The dev team heard about some exciting challenges they could work on…. and a slew of boring, basic features they couldn’t be bothered to test properly or care about."
tantek__and this: "People who are bred, selected and compensated to find complicated solutions do not have an incentive to implement simplified ones. — Taleb"
mayosknebel: sortof. I'm not actually using Aperture. I found one other microsub server that does something similar. But I'm implementing my own. But yes, I want to publish to multiple sub channels + my site.
mayosknebel: that's right, I don't want to login/logout for each post. Also, lost of services use rel=microsub, so it'd be hard to switch the URLs for different posts
mayosknebel: indiepaper.io solves it by just asking for URL+auth header, which works, but just doens't feel like the right approach. But it works, until something more general is worked out
sknebelok, so mp-destination sounds like it'd fit, but I guess if this becomes a common feature it could make sense to have some standard to find the microsub servers micropub endpoint
mayosknebel: the way aperture does it is it uses different Auth headers as channel "API keys", which it uses in place of the auth header. I see how that has drawbacks if I were to use this with mp-destination, but I should also ask Aaron why that solution was chosen, as opposed to other ways of doing it...
Loqiaaronpk: [eddie] left you a message 2 hours, 9 minutes ago: Does webmention.io have any support for Salmention or to start enabling that should I fetch the page contents whenever I get an updated Webmention ping from webmention.io?
sknebelI'd guess because not every client supports mp-destination, so endpoint and auth header are the two variables to switch on. It also means you can easily connect one client to one channel, which for automated tools like indiepaper makes sense
mayounrelated question... I've seen some micropub implementation that ask for token server URL in configuration. Is there any reason why they wouldn't extract "me" out of the token and grab the token endpoint from the URL?
aaronpkI added a Micropub endpoint per Aperture channel because it was immediately useful to me, and could be done without touching the Microsub spec, but I've waited to try to standardize any of that until there are more actual use cases documented
mayoaaronpk: the other question came out of: I already have micropub endpoint. Lot of tools discover micropub from rel=micropub on the site, and don't let me specify my own. If I also have microsub (let's say Aperture), which exposes micropub endpoint to post into channels, I can't easily tell other tools to use that instead of what's in rel=micropub.
snarfedmaybe one of the main q's here is, is microsub the appropriate tool to manage arbitrary user-managed lists of items? or is it better off focusing on reading feeds, like traditional feed readers?
aaronpk> log into indiebookclub.biz and want to post "want to read" to one of my microsub channels, followed up my a "finished reading" post to my site.
tantek__"which in the process of doing that actually adds the article to the reader" nothing special is needed there if you actually post a "want to read" post to your own site, and your site is subscribed in your reader?
snarfedan alternative solution would be to post the "want to read" post to your site too, and include those posts in a feed that you then subscribe to in microsub
snarfedthe argument for it is portability. that's one of the big reasons to use a standard, but if it's an important part of your workflow, and it's not in the standard, you're not portable
[cleverdevil]Well, in the case of Indiepaper, you can IndieAuth with any Micropub-compatible service, and save articles to it. That includes Aperture, where it'll publish to a channel, and Micro.blog, where it'll publish to a special feed for you to subscribe to in a reader.
aaronpkSo for example I have little scripts in various places that push data into Aperture channels. These are things like the twitter search script, or notifications from my home automation systems, etc.
mayoaaronpk: Right. I was hoping to find a solution (or start a discussion) to make it more seamless than "enter url + auth header". I'm not saying the standard needs to be changed or improved, but being able to say "these are the channels you can post into" and discover and consume them easily (and interoperably) would be nice to have. The ability to add new items into microsub channels ems in addition to just consuming feeds seems like a very natural w
mayobah, that got cut off... The ability to add new items into microsub channels in addition to just consuming feeds seems like a very natural way of using channels.
mayoI think about it just like adding things to "read later" category in any feed reader. I'm not making the posts public, I'm keeping a list for later. Once I read the post, I can choose to post about it.
gRegorLovemayo: There is a request for visibility setting on indiebookclub that I plan to implement, so the posts could be private or unlisted on your site.