Data wants to be dirty.
Duplicated data wants to skew.
A while back, I wrote up a design for bridging Microsub clients to traditional feed reader backends. Fast forward to a few weeks ago: I hacked together a bare bones prototype at IndieWebCamp 2018. Fast forward to now: I’m launching Baffle!
Right now, it only supports viewing channels and timelines. If there’s enough interest and usage, I can add channel management, muting, and blocking. I’d also consider adding Feedly if I hear enough desire.
But there was no corresponding sunshine in Bertram Wooster’s soul and no answering Twitter in his heart as he sat up in bed…
- PG Wodehouse, Right Ho, Jeeves
Tree, trunk, branch, crown
Climbing up and sitting down
Morning sun becomes noon-blue
All the world is old and new
Road, street, track, path
Ship, boat, wooden raft
Nest, bird, feather, fly
All the world has got its sky
Spreading shadows, setting sun
Crickets, curtains, day is done
A fire takes away the chill
All the world can hold quite still
Beautiful homespun poem, and my favorite book to read to Brooke, bar none. Happy Fathers Day.
I announced recently that Bridgy Publish for Facebook would shut down soon. Facebook’s moves to restrict its API to improve privacy and security are laudable, and arguably the right idea, but also mean that users can no longer use third party apps like Bridgy to create posts.
I didn’t realize it at first, but similar API restrictions hit the backfeed (aka listen) feature, which sends comments and likes back to your web site. Bridgy can still see comments and likes by Bridgy users, but that’s a tiny fraction of the Facebook comments and likes that it used to see.
I spent a while looking for a workaround, and even looked into scraping HTML, but you have to be logged into Facebook to see even public posts, on both www and m, so no luck there. [Insert silo snark here.]
So with a heavy heart, I’m shutting down Facebook on Bridgy entirely. Publish will still work until August 1, but listen largely stopped working on May 24, so I turned it off altogether and disabled new user signup a few days ago.
Emacs now provides a limited form of concurrency with Lisp threads.