Kind replies

 Reply

Nice! If you manage to come along to #HomebrewWebsiteClub Nottingham we'd be happy to have you to come work on your site 👍 The next one (https://events.indieweb.org/2020/03/homebrew-website-club-nottingham-anniversary-edition--Rcujt5SykHv1) is likely going to be a meal out, so https://events.indieweb.org/2020/04/homebrew-website-club-nottingham-UpVd9JZeVzx6 will be the next one (but I may make it remote-only due to #coronavirus)

 Reply

On mobile too? That's interesting, I've not found it slow since I moved over a while ago, but not got any recent comparison with Chrome so may not be helpful

 Reply

I guess it's more that we have development environments to play around with, the staging environment should be treated as prod - ie treat it the same with infra, security, support policies etc.

But that's true - it's better to play in staging than prod!

 Reply

https://heyguys.cc/ is a great resource for this, and is a handy link to share others when they're not able to find the right term 👍🏽

 Reply

I'd thoroughly recommend self hosting - I use Hugo and Netlify for mine and it works really well. It's also got the bonus that because it's my own site and platform that I can use it as I want, such as replying to your tweet from my website

 Reply

Currently, the format of the tokens provided by IndieAuth.com is a signed JWT (JWS) using HS256.

If we were to update this to be RS256, we could allow clients to treat it as a JWS, not an opaque token that needs to be introspected by the token endpoint.

This could allow clients validating tokens as such to do so much more easily, locally, while reducing load on the token endpoint.

Because token revocation is not widespread at this point, it would enable clients to not need to introspect unnecessarily.

 Reply

I think of notes in terms of https://indieweb.org/post-type-discovery and them being short form content similar to a tweet (but without a size limit) without a title

 Reply

FYI in this example you can set this to happen by default https://www.jvt.me/posts/2019/09/22/git-push-matching/

 Reply

Ooh nice! I've been using https://github.com/PlaidWeb/webmention.js for my client-side webmentions and have found it really nice ☺

 Reply

I'd recommend publishing to your own site first, and then sharing links to it on sites such as Twitter and https://lobste.rs, and maybe also sharing on https://dev.to but primarily owning it yourself to build up the followers there

 Reply

Sorry to hear that - I think part of it is due to my feed including most things on my site, which I need to fix at some point - if you want to just subscribe to my blog posts, https://www.jvt.me/posts/feed.xml should do it for now!

 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

 Reply

In terms of how I get the data? I publish content to my site first, then syndicate it elsewhere afterwards https://indieweb.org/POSSE - which mostly happens automagically

I do this even for things like https://lobste.rs which doesn't have an API so I manually post it with a link back to the comment on my site