Tag indieweb

What in particular are you finding difficult? I'm running a Hugo site and have quite a few #IndieWeb integrations

I'm quite heavily into the IndieWeb movement, in which we've designed a new standard Microsub which allows for a slightly better API than "regular" RSS/Atom readers, as it allows for you to use different feed formats on the backend. It also splits between the client and the server quite nicely, so I can use Indigenous for Android when on the move, and Monocle when I'm on the desktop. The best thing about the standard, aside from allowing extensible feed parsing, is that I can use different clients to read it, instead of relying on a single provider - which I believe we've seen with some of the RSS/Atom readers around currently.

The server I use is Aperture, built and run by Aaron Parecki, and I subscribe to a mix of RSS/Atom, JSON Feed and Microformats2 feeds

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 👍🏽

I can reply on my own #IndieWeb website so 🤷🏽‍♂️

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

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

I've been doing a lot of #IndieWeb things recently which allow me to own my data a lot better - such as this tweet which is actually published to my site first, then gets syndicated to Twitter - been fun for many reasons

#HomebrewWebsiteClub Nottingham is on Zoom tonight, courtesy of the wonderful #IndieWeb organisers - you can find all the events details on https://events.indieweb.org/2020/03/online-homebrew-website-club-nottingham-anniversary-edition--Rcujt5SykHv1

It's about time to demo my personal website at #IndieWebCamp London - I've got some pre-written notes about what I want to talk about on https://etherpad.indieweb.org/IWC_London_Site_demos although some of you who know me will know I can talk for ages about my site and the #IndieWeb!

#IndieWeb folks who still interact with Twitter - how do you consume it? Do you use Twitter.com and share it to your ie Micropub client? Do you subscribe to it with your Microsub / Social Reader? Or something else?

A great point from @adactio - don't resign yourself to inevitability. We can change the way that the Web works, we can take back our control, as long as we fight for it. #TechNott #IndieWeb

"Reducing complexity increases chance of mass adoption" - this is the reason that folks are seeing this content on Twitter on #TechNott rather than directly on my own blog.

But the #IndieWeb are trying to make things better - come and help us build a better Web which works for you!

I thought I spotted a rel=webmention link on the slides earlier at #TechNott 🤓 #IndieWeb

It may not be ready by the #IndieWeb newsletter tomorrow, but I'm hoping my web-based Micropub media endpoint upload client will be live this weekend - exactly what would fit for https://jlelse.blog/micro/2020/01/2020-01-01-frviz/

I want to say that some of the folks in the #IndieWeb may be able to chime in on this too, as we try to publish events to our sites where possible

#IndieWeb

I've just published the headlines of my #Spotify data for 2011-2019 on my site - https://www.jvt.me/series/music-in-review/ - organised per year, but also with a view across the whole decade! Enjoy a look into my music data #IndieWeb

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

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

There are also lots of #HomebrewWebsiteClub events across the world where you can come and build, or enhance, your personal website with something #IndieWeb related - we've got one in Nottingham! https://events.indieweb.org/tag/hwc

For anyone at #NaConf looking to learn more about owning your data and the #IndieWeb, I recently did a talk about it, with a transcript available at https://www.jvt.me/posts/2019/10/20/indieweb-talk/ which will hopefully shed more light!

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!

#IndieWeb folks using Indigenous for Android (https://indigenous.realize.be/) or at least allowing a Geo URI (geo:51.501476,-0.140634) on their #Micropub endpoint - do you attempt to remap that longitude / latitude ref to a place, or do you currently just render it as-is?

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/)