Kind replies

I've been self hosting #Matomo for several years now, and haven't found it too much work, as I've got a really hacky database backup script and otherwise it handles things well - I'd recommend giving it a go again!

I know we've talked about it in the past, but how do you feel about possibly setting up a #HomebrewWebsiteClub in Lincoln? I've found there's very little organisation required for mine in Notts - generally just turn up and do stuff 🤓

If you want to build / enhance your personal website, #HomebrewWebsiteClub Nottingham is a great place to get involved, next one is the February 5th https://events.indieweb.org/2020/02/homebrew-website-club-nottingham-8IgcYeAQhIKX

Awesome to see the first event posted! In case you've not seen Aaron's post there's now a new IndieWeb events site https://events.indieweb.org/ you're more than welcome to still publish the event on eventbrite but would you also be able to publish to there as well, for IndieWeb folks to discover the event, too? Much appreciated!

Agree that some users won't want to get stuck into it - they're likely also the users who won't be writing raw HTML for their sites.

So what we're doing for them is getting Microformats2 support directly into the themes for WordPress, Jekyll, Hugo, etc, so anyone using it can benefit without necessarily doing any work!

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!

Thanks! Maybe "this project is source available, not Open Source. Utilising any code within this project is forbidden." or stating "this project is proprietary, despite the source being available. You may not use it for any reason"

Hey as an FYI, from your README:

No license.

This repository is open sourced

Without a license for it, it's not technically Open Source, therefore is proprietary and not usable by anyone. It may be worth being explicit!

The only thing keeping me going is knowing I'll be back to my laptop soon 😉😂

Also check out https://twitter.com/scienceshitpost for the twitter version!

I'm sorry for your loss 😭 that's so horrible!

That's such a great t-shirt you're wearing!

Southern Tenerife, it's lovely here!

Unfortunately it's only 18 degrees, so not roasting, but quite nice and warm compared to the UK this last week!

I've written about how I added it to my own site www.jvt.me at https://www.jvt.me/posts/2019/08/26/setting-up-micropub/ if you'd like more info on how you'd go about it - as my site is built around Git as the source of truth, I simply need to get it committing the changes for me and that's it!

Re:

TLDR: Nearly everyone who wants micropub support writes their own library, endpoint, or whole cms or blog engine.

I believe part of this is because Micropub requires intimate knowledge of how your own site is set up, so unfortunately can't be written as a generic solution, because most folks won't have things set up the same way, even on ie WordPress using common IndieWeb plugins

It's still a good point that maybe we need to look at creating an out-of-the-box Micropub endpoint for some of the common tech stacks.

My preferred photo always sits at https://www.jvt.me/img/profile.png which makes it super easy as I always know where it is, for this exact reason!

I'd be interested to hear an answer if you find out - I have a similar post that only seems to come via the same URL

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

Technically my reply to this tweet is the latest thing on my blog (see the link at the end) but https://www.jvt.me/posts/2020/01/14/ruby-parse-unix-epoch/ is the last, super short #blogumentation blog post

#npm allows you to do things like this, with other people's code (in a good way):

Is there any way to get one of those awesome stickers otherwise? 🙀

The tweet above you has an even better alternative for breakfast 😂💊

I was wondering how you were finding time to write so many good posts! I've been enjoying it 🤓

That is, ~4 minutes later due to the time it takes to publish the site and then syndicate the content to other platforms - so not quite as realtime

I'm definitely a Hugo person since moving from Jekyll last year - I'd be happy to share any experiences you'd like.

Not sure anyone has linked you to https://www.staticgen.com/ btw, for all the known static site generators

Haha thanks! I wish I could take credit for it - I'm not sure who in the IndieWeb community made it, but it is pretty awesome

It does! This post is coming straight from my website using brid.gy publish!

You can certainly come join us for a place to work with others, that'd be alright :)

As I published this to my site first, it makes more sense to tag her URL, but I need to get some rewriting for Twitter syndication so it tags her Twitter account - all in good time!

This is an interesting one, because I've recently been very frustrated with Firefox and captive portals, as it attempts HTTPS first, then ends up retaining HSTS - it's a difficult one to get right though, and I agree that attempting HTTPS first is a better idea.

I found that writing short blog posts as a form of documentation https://www.jvt.me/posts/2017/06/25/blogumentation/ helps lots with reducing the barrier to blogging, as well as writing one post a day for Nablopomo https://www.jvt.me/posts/2019/11/01/national-blog-post-month/

Yeah I'd say unfortunately that's then removing the effectiveness of using a CDN. I've seen issues when using two CDNs as it can make cache invalidation etc a bit harder

Also doing NaBloPoMo (https://www.jvt.me/posts/2019/11/01/national-blog-post-month/ ) helped lots as I got used to publishing pretty quickly, which was kinda the point of it, for me at least

I used to refine things lots, but it meant spending hours on a post that took 5 minutes to read. Long posts I do still refine over time, but generally want them done at most a few days after it's finished being written.

If it's a Blogumentation post (https://www.jvt.me/posts/2017/06/25/blogumentation/ ) then I'll actively not refine it too much as a long post as the point is that it's for me in the future so if its not as readable I'll just edit it then

This is a great idea! I'm planning on doing a similar thing to this based on the "Week Notes" that Ton does ie https://www.zylstra.org/blog/2019/12/week-notes-1952/ as a visible way of recounting weekly achievements / what kept you busy

In the last couple of days, I've also added media support for my Micropub server, and have encountered the same issue.

Thankfully the changes to Indigenous are soon going live, but I was surprised not being able to use it elsewhere.

I believe https://quill.p3k.io supports it, as long as you're posting it with a note?

Glad to hear it! I've been toying with the idea for a few years but have never found the guts to do it

In 2018 I wrote 60 posts (92k words) but in 2019 I wrote 159 posts (107k words). Of those, 41 and 73 posts respectively were under the term "Blogumentation" https://www.jvt.me/posts/2017/06/25/blogumentation/ which I am a huge fan of.

Don't write for anyone else - just yourself!

I mean, I said that an hour or so ago, but that was before the site had deployed... Turns out https://www.jvt.me/posts/2019/11/11/gotcha-netlify-lowercase/ caught me out again and isn't fixed until https://gitlab.com/jamietanna/jvt.me/merge_requests/638 is in (although I've done a temporary deploy from my local machine to get the site up).

Very annoying!

This is really great stuff!

I've raised an issue on the https://brid.gy repo at https://github.com/snarfed/bridgy/issues/905 as I feel this could be a great fit for the project, as it'd handle that syndication for you, instead of you needing to set it up yourself.

It may not be needed by the community, but if it is, there's hopefully a good fit there.

If you want inspiration / don't want to write your own - https://indigenous.realize.be is great. I use it daily and it's a great Microsub client.

If so I've definitely been doing my Christmases wrong! Can't even think when the last time I saw it was

Out of interest where are you moving to?

Because GitHub is willing to work with ICE https://techcrunch.com/2019/11/13/github-faces-more-resignations-in-light-of-ice-contract/ but at least GitLab are being up front about their politics?

Although yes I agree they're not amazing

All my code hosting is on https://gitlab.com/jamietanna

Static site hosting is on https://netlify.com and VPS hosting is on https://hetzner.cloud

Although some things that I contribute back to are on https://github.com

Huge congrats Shaun!

Ah fair enough. Have you blogged about it before? Would be quite cool to read about it!

Nice! That sounds like a it's worth a blog post explaining how you did it?

I guess, that's a fair point. Would still be good if we can improve the usability of password managers for not-as-technical folks

I work on Open Banking APIs for a UK credit card provider.

A large reason I see that the data isn't made directly available to the customer is because if the customer were to accidentally leak / lose their own data, the provider (HSBC, Barclays etc) would be liable, not you. That means lots of hefty fines.

You'd also likely be touching some PCI data, so you'd need to be cleared / set up to handle that safely (or having some way to filter it before you received it).

Also, it requires a fair bit of extra setup and the use of certificate-based authentication (MTLS + signing request objects) means that as it currently sits you'd be need one of those, which aren't cheap as they're all EV certs.

Its a shame, because the customer should get their data. But you may be able to work with intermediaries that may provide an interface for that data, who can do the hard work for you, ie https://www.openwrks.com/