julianfstrugee: I just noticed the pump.io homepage seems to lack any mention of being a system based on protocols, APIs, diversity of implementations, etc. Then I noticed the github page is similar but adds a link to the wiki, and there some of that good stuff can be found.
julianfAck. Just wanted to mention it, because I think getting that overview focused on the architecture is key, even for a reader like me who knows about it and is actively looking for the details. (A diagram would be awesome!) Thanks!
tantekinteresting way that FB seems to limit reposts: "Who can see this? / When someone shares something you posted, who can see your post doesn't change. Your post can only be seen by the people you originally shared it with. Learn more."
petermolnarI understand why this happens to self-made material; but if it's a publicly available something you share and others are trying to re-share it in order to make it reach more people, this will suppress those efforts
tantekbut perhaps if we figure out the indieweb equivalent to a limited ACL repost, we can make the webmention interpretation of that stick with requiring maintaining of the original ACL (somehow)
KartikPrabhu, awolf, jmelesky, snarfed, snarfed1, mlncn and gavinc joined the channel
sl007aaronpk: Did not thought it is so much work to do everything right in indieauth-node, however: it comes to caching - what it does is putting a session id in a secure cookie and storing the verify results in the serversession [and anybody using it can simply plug in REDIS or any of https://github.com/expressjs/session#compatible-session-stores] - QUESTION : shouldn't we cache only successful providers? If either a provider is unreach
gRegorLove"that should be its own blog post, because Twitter’s horrendous chronological formatting design is meant to maul and strangle content to the point that it’s unrecognizable."
marcthiele, wolftune and julianf joined the channel
tantekinteresting abuse of event posts I'm seeing on FB, a public event which isn't actual physical event, but rather a start date / end date of when tickets are on sale for an actual event
tantekI'm leaning towards classifying this as spam, that is, merely unsolicited advertisement to buy something that is deceptively presented (since it's not actually an event you can attend and participate in)
tantekby providing a broad date range, e.g. November 28 – December 5, once someone has invited you to it, it causes the "event" to stay at the top of your "upcoming events" on your fb.com/events page for many days in a row
tantekI'm sure someone somewhere thought it was a clever marketing technique they came up with. As did the people innovating with unsolicited email to sell stuff.
bignosecharitably: it shows a flaw in the feature. where one can't specify related date ranges (e.g. when do ticket sales open/close) for an actual event.
bignoseso, while I agree there's a good chance the post is motivated by the marketing (get it in front of more people more often), it's also the case that *even if* someone isn't motivated by that, there appears to be no good way to encode that information in the event feature.
tantekand for some events, e.g. concerts which sell out, people do very much put on their calendar when the tickets go on sale so they can be ready by their computers to *participate* in real time in the ticket purchasing event