@KentonVardaJesus Christ @zoom_us, you've apparently let a whole school in Chile sign up for a paid account using my e-mail address, because you never verified it. I went to create my own account, it said I had one, so I "forgot password", and now I own this school's admin account. (twitter.com/_/status/1261386443940868096)
doosbooxI had a very common surname before I got married, and my email was firstname.lastname@example.org. I still check that email now and then, and I've had invites to parent/school conferences, kid's birthday parties, reminders to pay bills, tracking info for shipped packages... All meant for someone else
[chrisaldrich]Given Google's history of killing Reader in a possible attempt to help empower their G+ product, does anyone else see their getting rid of email subscriptions from feedburner as a play at an upcoming Newsletter service/app/feature?
[chrisaldrich][jgmac1106] There's a nice little SubToMe bookmarklet that might help ease some of that friction for you https://www.subtome.com/#/settings. May not work as well for mobile, but you're right that RSS needs an improved UX for making subscribing easier.
[chrisaldrich]I really want to create a bookmarklet for WordPress' link manager to import all the basic, name, avatar, feed, etc. data into my own website to make subscribing easier. Do any of the social readers have bookmarklets for quickly adding subscriptions there?
[KevinMarks]the deeper problem, which is how we end up with algorithmic feeds, is the goldilocks problem of following, where you start with too few to have any pdates, and so follow more, and end up with too many
[tantek]newsletters are a one-way deadend. their appeal is ease of sign-up and the fact that you read them in a reader (email) without a lot of UX distractions. they're read-only though and a throwback at best.
[KevinMarks]coalescing is an algorithm too - if you look at the evolution of social feeds they went through those kinds of things, then noticed that most people don't want to do that much config and ended in automation
[tantek]jacky, agreed. a reader could dial-up / down the frequency/latency that it shows you posts from someone based on how often (or not) you respond to their posts. if it's extra clever it could detect which *kinds* of posts from which people you respond to more and dial up those more, clustering the others
jackyI do wonder how / where to store that information so people could understand what some decisions are made (we've noticed that you've reacted happily to a lot of photos recently from two people in your 'Close Friends' channel so we're showing more of those due to your "More Like This" toggle) or something
[chrisaldrich]The indiewebification of one's content definitely pose this problem. Once you aggregate all the content you've got across all platforms and put it in one place, it does become rather a lot to attempt to consume.
[aciccarello][chrisaldrich] I've been trying to think about that as I consider adding more post types to my website. Is there a wiki page discussing that? I'm considering splitting my feed up into long-form (blogs/recipes), short-form (notes/photos), and reactions (likes/bookmarks)
[schmarty](i realize that's a very plumbing-centric way to approach these things but it also feels like something that should have demos all over the place in a time of hype about serverless functions)
[aciccarello]> Providing valid, but limited interest feeds. eg, search feeds (couches for sale in Portland on Craigslist!). Also lots of custom things like combinations from Yahoo Pipes (or whatever equivalent people come up with), bookmark/favorite feeds, etc. Can lead to lots of duplicate (or near duplicate) posts, and lots of feed retrievals that very few people care about.