epeus

Is Peter Thiel's opposition to Women's Suffrage still policy at Facebook? https://www.huffpost.com/entry/peter-thiel-women-democracy_n...

The Microsoft trigger was `text-justify: newspaper` and intended for fully-justified narrow columns. I don't think it made it to Edge.

That reminds me of this classic 1990s internet description http://stuartcheshire.org/rants/InfoHighway.html

Tumblr supports them as of May https://changes.tumblr.com/post/683524731509653505/friday-ma...

More useful information at https://indieweb.org/Webmention-faq

Indeed - every silo wants you to use their own specific markup, but even then they choose what to show. I made a post a while back that gave a different summary on every silo platform https://www.kevinmarks.com/partialsilos.html Of course, since then some of the silos have died or given up on their own systems, but microformats remains useful if you want to co-operate.

Both Mastodon and Tumblr have microformats support built in. Twitter and Facebook used to, but they decided they'd rather be silos than protocols

That's not exactly accurate. The wiki has been edited recently, and change discussions are now done through github issues before updating the wiki, as that is more convenient than inline chat in many cases https://github.com/microformats Also a lot of the practical discussion of microformats use is at the indieweb wiki - see https://indieweb.org/posts#Types_of_Posts for h-entry for example

Hi Clay, Kevin Marks here. I an help you scrape it out of wordpress into a static site if you like, I've done similar for Dan Gilmor and other old bloggers. Ping me - kevinmarks@gmail.com

Read the post - previously deleted tweets showed the blockquote fallback. Now they get a useless injected blank iframe, removing the blockquote from the dom.

You're wrong. The tweet embeds decorate a blockquote of the tweet - read the article. The now code removes that blockquote from the DOM.

And the documentation for the embed api on their website https://developer.twitter.com/en/docs/twitter-for-websites/e...

We trusted them because they were committed to being part of the wider web, and as you can see from Ben Ward's tweet at the time, took that seriously.

If they want to change this, they can have a new version of the widgets script that makes it clear that it will edit your site, and switch to that in future embed links from the site. Changing the existing one is leaving holes all over the web. Buzzfeed is decimated.

It's not a dogma so much as a warning from experience. If you post to your own site first you do retain control. If you rely on the silos' api to extract it back to your site you are dependent on them remaining committed to their api. That has not been a good bet in the last decade.

It's not so much that they take ownership, more that they choose who can see it, and can remove it arbitrarily from the web.

Refusing to use attributes in this kind of *ML and using <param> instead makes this a mess to parse safely. I imagine this will be read as HTML and the params will show up in the document oddly.

The specific reference to email was based on frustration with endless mailing list bikeshedding, especially on 'standards' mailing lists. Building a community around irc, wikis and posting on our own sites was a deliberate alternative.

It is a very ugly term; 'eat what you cook' is clearer. The point is that rather than theorising about 'what people want' you should build tools that solve your own problems, and practice with your own site first. This was important early on in Indieweb as there are a lot of people proposing that online social networks should work in a specific way, and demanding others change; building something you use daily yourself is a better basis for discussion.

For an action oriented list, try https://indiewebify.me/

Indieauth uses OAuth; there's also tools to delegate auth to silos via RelMeAuth https://indieweb.org/RelMeAuth

It's a very informal organisation - you are part of the indieweb if you have your own site. If you want to talk about it, there's https://chat.indieweb.org/ (which bridges to IRC, Matrix and Slack). You can sign into the wiki with your own website, and add yourself to the list of people here https://indieweb.org/chat-names

That's a start, but having your own domain means that you can choose to host elsewhere later. There is a quick start github project https://github.com/indieweb/blank-gh-site

If you have your own website, you are indieweb. Having your own domain name is better as then you can decide to change hosting later. After that there are a series of protocols you can adopt to fit in with other indieweb people. Have a look at https://indiewebify.me/ for an interactive way to try these out.

Not centralized, this is a tool to enable it for static sites. See other alternatives at https://indieweb.org/Webmention#Publisher_Services

BTW, there's a pretty good discussion of pingback compared to webmention here, including how to bridge between them and some of the spam problems too https://indieweb.org/pingback

Marty writes up some of the variety of implementations here https://martymcgui.re/2020/07/15/what-we-talk-about-when-wer... (which I saw because he webmentioned my in it).

I've had them on my sites for a few years now, and even with bridgy passing tweet replies through the spam hasn't been too bad, but certainly adding an allow-list makes sense too. Having built Technorati that effectively did this at scale, I do appreciate the spam problem, but decentralising implementations has so far worked out OK.

I think this previous rebuttal to pg's pretence of broad mindedness still applies https://medium.com/@girlziplocked/paul-graham-is-still-askin...

I did a comparison here a while back: Simpler, more terse, use class rather than extra properties or giant json blobs. http://www.kevinmarks.com/microformatschema.html