Tag indieweb

 Reply

You can make it work with tools like https://twitter-atom.appspot.com/ or https://granary.io (from Ryan Barrett) which help convert to a feed format of choice. Those of us in the #IndieWeb are still heavily using open standards 👍🏽

 Reply

My #PersonalWebsite is https://www.jvt.me and as I'm very into owning my own data and being part of the #IndieWeb, I'm replying to this tweet from my website!

Site itself is Hugo and hosted on Netlify

 Reply

Definitely doesn't work like that. I'm posting to this site through my own website, which means I own my content, not Twitter, and definitely not you #IndieWeb

 Bookmark

I've got this set up on my own site against https://www.jvt.me/img/profile.png and it's really great. No more finding that image you want to use - it's just there. It's available automagically via my Microformats2 h-card, so it can be machine discoverable, too. But I agree with Terence, it'd be awesome to have some standardised way to pull it from all my services, though.

 Reply

Ah no - since getting involved in the #IndieWeb I've been trying to use my site as the owner for my content, wherever it's for, and then pushing it out to silos after

 Note

I interact a lot with Twitter from my website, and as such the interactions you see are i.e. "Like of @indiewebcamp's tweet" which isn't super helpful. So I've just added the ability to mark up my interactions with some context of what the post was so it's eaiser to see without navigating there.

This is using the awesome https://granary.io/ and will hopefully make reading Twitter interactions through my site much nicer!

You can see https://www.jvt.me/mf2/2020/02/ihnc5/ for an example of what it'll look like (including photos!), and https://indieweb.org/reply-context for more info from around the #indieweb

 Reply

As shared in a separate comment in the thread, there's the Microformats2 specification (see https://microformats.io) which reduces duplication seen with some of the other Semantic Web formats.

You can see an example of a parsing result at http://php.microformats.io/?url=https%3A%2F%2Fwww.jvt.me%2Fmf2%2F2020%2F01%2F2mylg%2F which produces a standardised structure for the resulting JSON, which makes interconnectivity much simpler.

Us folks in the IndieWeb (https://indieweb.org) have been using it for some time with great benefit, but it's always great to hear others reactions too!

 Reply

Tbh I'm still using Twitter, just replying from my own site where possible (to own the data) and even when not, I'm using other #IndieWeb tools so none of it is mine per se, but at least all FOSS. And definitely better ownership. I'm looking to soon import all my old tweets to my site, as well as my #Spotify data which I received today for the last decade (via https://www.jvt.me/posts/2019/12/29/spotify-wrapped-data-request/)