Last Updated
Map
Part of this is an opportunity to improve audio post presentation on my website, so you will see audio posts improve over time.
Show Notes
The originating articles that kicked off the Facebook/Cambridge Analytica issue:
- 3/16/18: Facebook’s Newsroom: Suspending Cambridge Analytica and SCL Group from Facebook by Paul Grewal Protecting people’s information is at the heart of everything we do.
- 3/17/18: The Guardian: Revealed: 50 million Facebook profiles harvested for Cambridge Analytica in major data breach https://www.theguardian.com/news/2018/mar/17/cambridge-analytica-facebook-influence-us-election
- 3/17/18: New York Times: “How Trump Consultants Exploited the Facebook data of Millions”: https://www.nytimes.com/2018/03/17/us/politics/cambridge-analytica-trump-campaign.html
Other related articles:
- Anil Dash: Article bringing the Facebook issue back around to regaining the good parts of the “old” web” https://medium.com/@anildash/the-missing-building-blocks-of-the-web-3fa490ae5cbc
- How To Change Your Facebook Settings To Opt Out of Platform API Sharing (Electronic Frontier Foundation) https://www.eff.org/deeplinks/2018/03/how-change-your-facebook-settings-opt-out-platform-api-sharing
- 3/24/18: Ars Technica: Facebook scraped call, text message data for years from Android phones
Recent Documented Facebook Quitters:
Jonathan LaCour: https://cleverdevil.io/2018/ive-officially-deleted-my-facebook-account-and
Eddie Hinkle: https://eddiehinkle.com/2018/03/22/5/article/
Natalie Wolchover: https://twitter.com/nattyover/status/975711260221362177
New York Times Profile of multiple quitters: https://www.nytimes.com/2018/03/21/technology/users-abandon-facebook.html
IndieWeb Wiki related pages of interest here:
- https://indieweb.org/why
- https://indieweb.org/principles
- https://indieweb.org/Facebook
- https://indieweb.org/silo-quits
- https://github.com/tootsuite/mastodon/issues/6074
Potential simple places to move to when leaving Facebook
- Micro.blog for $5/month (or bring your own web site for free)
- Mastodon
- WordPress.com
- Tumblr.com
- WithKnown (Paid service or host your own)
- WordPress.org (self-hosted or managed)
- Other possible projects/options: https://indieweb.org/projects
Sebastian Greger’s Privacy policy: https://sebastiangreger.net/privacy-policy/
Mastodon not supporting Webmention specification: https://github.com/tootsuite/mastodon/issues/6074#issuecomment-378452136
WordPress Plugin for IndieAuth
Related IndieWeb Wiki Pages
Micropub Apps Mentioned in the episode
PESOS – Post Elsewhere, Syndicate to your Own Site
POSSE – Post on your Own Site, Syndicate Elsewhere
Closing discussion of IndieWeb Readers and MicroSub Pieces
The current podcast feed on this site can be found in a variety of ways.
- Audio Posts on this Site – This is a feed of all my audio posts.
- An Indieweb Podcast – I have something called Series on my site, so this is the feed for this as a series. I probably should have a feed called Podcast.
Co-Host: Chris Aldrich of Boffosocko.com
Show Notes
Facebook has announced ending publishing by API…and David is thinking about what it means for the community and his current project.
- Facebook is ending posting via API on August 1, 2018 https://developers.facebook.com/blog/post/2018/04/24/new-facebook-platform-product-changes-policy-updates/
- Bridgy Announces the coming changes: https://snarfed.org/2018-04-26_bridgy-publish-for-facebook-shuts-down-in-august
- Buffer responds, but then checks itself: https://twitter.com/buffer/status/988915108620505088
- I’m done with Syndication. Let’s help people be themselves on the web. By Ben Werdmuller https://werd.io/2018/im-done-with-syndication-lets-help-people-be-themselves-on
- Deprecating and Replacing Bridgy Publish for WordPress by David Shanske https://david.shanske.com/2018/04/28/deprecating-and-replacing-bridgy-publish-for-wordpress/
History:
ThinkUP from Anil Dash and Gina Trapani ultimately died trying to fight the API wars with various social silos. They spent all their time trying to keep up with no guarantee that the silos would cooperate. All their engineering resources were spent trying to keep up instead of innovating on a stable platform.
Related IndieWeb wiki pages
- crossposting
- POSSE
- PESOS
- Manual until it hurts
- Brid.gy Publish
WordPress Plugins:
With the GDPR regulations coming into effect in Europe May 25th, privacy seems to be on everyone’s mind. This week, we tackle what webmentions are, using them for backfeed, and the privacy implications.
- The Indieweb Privacy Challenge: https://sebastiangreger.net/2018/05/indieweb-privacy-challenge-webmentions-backfeeds-gdpr/
- Webmention Specification http://webmention.net
Related IndieWeb wiki pages
- Principles https://indieweb.org/principles
- Webmention https://indieweb.org/webmention
- Privacy https://indieweb.org/privacy
- GDPR https://indieweb.org/GDPR
Links
- Do I know anyone interested in building #indieweb tech or federated services? I’m having trouble conceptualizing some things without having people to bounce ideas off of. https://twitter.com/davidlaietta/status/995485455675162626 That’s what this is all about! I have always been an outsider to that community and want to find good ways to enter and get involved, but I am also trying to find ways to make ActivityPub based projects more accessible to the average web user.
- IndieWeb Summit https://2018.indieweb.org/
While this is very WordPress centric, there are a lot of discussions here relevant to a broader Indieweb audience about adding new types of posts to your site, trying to design things flexibly(although a developer’s guide is probably needed), etc.
We’re both looking forward to seeing those of you who can join us in Portland.
In this week’s episode, we discussed new developments in WordPress and what I’ve wanted to accomplish for all these years in the Indieweb community. The ability to read something on my phone, store it on my website to either share or just save, as appropriate.
We discussed recent projects I’d worked on, such as the Micropub plugin, client discovery in IndieAuth, Post Kinds, etc.
Thoughts About Assertion Workflows
Scenario 1: Individual creates criteria and wants to assert that other individual has achieved said criteria. Example: Professor wants to certify students completed coursework.
- Professor Posts Criteria for Each Achievement as a unique page (A).
- Student completes assignment as a post (B).
- Professor Posts Badge/Assertion/Endorsement post on their website as an h-review, with a p-item property to student’s URL (B). Would need a new or existing property to represent the relationship to the original assertion (A).
Suggest u-assert and u-assert-of?j Can use u-in-reply-to possibly.
Scenario 2: Individual creates assertion post and solicits others to endorse that statement as factual.
- Individual makes a post to their site(h-resume for references on a resume, not sure what to request endorsement of a statement? p-assert with a nested h-item?) and invites other individuals(using existing invitee property used for RSVPs?) to endorse or assert it. Criteria might be included for achievement.
- Others create ‘assertion’ posts on their site(
assert-of) and send webmentions, which would cause the post to be updated to note that it had been achieved.
Existing microformats for h-resume and h-review seem to allow additional context.
- Education
- Experience
- Skill
- Rating
- Best
- Worst
Brainstorming on the Indieweb wiki under assertion.