Replied
Replies
Replied
Replied
Feel free to use or contribute to http://examples.tpxl.io - it sounds pretty similar to what you're taking about.
Replied
Gutenberg compatibility would be killer. All the tools are there in Gutenberg to make awesome IndieWeb friendly posts, but might be difficult to get it to play nice with the current plugins & themes.
Replied
You have hit upon one of the great conundrums of the IndieWeb - everyone loves static sites until they want to do something dynamic 😄
I know you already moved off Next.js but I use that now, and it can actually be a mix of statically generated and dynamic content which works great for me.
The other thing to look into is basically fancy build steps. I don't really know if it is common in Jekyll, but in things like Gatsby and 11ty it is quite common to have a build step that pulls data from external sources, then new builds can be fired by webhooks.
Replied
Tried wsl2 yet? I've found it works with pretty much anything I've thrown at it. Only issue is the slow windows filesystem - but apparently it's way better if you use the specific wsl file system
Replied
This is actually pretty close to some ideas I had for a microsub "middleware".
With the way microsub is built it would be possible to generate recommendations and category feeds without a centralized server. You can create a "client" that can automatically read channels from any server and create feeds / modify existing items.
I already have a decent working example in removing like posts from a feed and sending them as a daily rollup instead at https://glitch.com/~microsub-middleware
With this middleware idea there is also no need for specialized servers and clients, it should all just kind of work (hopefully)
Replied
Yeah there might be workarounds, and there is the idea of a micropub media endpoint for that sort of thing. But it doesn't feel as nice to have one part serverless and the other part not.
Replied
People have at least thought about this, not sure if there are any working examples out there though.
A common problem people ran across was serverless functions enforcing a maximum post body size, so no real media posting.
Replied
Oh hey, you're just down the road from where I live! Enjoy!
Replied
Try bitwarden_rs instead! I've been running that for a year or so and loving it.
Replied
Looks like you've come up with a nice solution that works for you 👍
You should check out micropub it's kind of a open specification for what you've already built, then you can use any micropub client to post to your own website!
Replied
418 "I'm a teapot" of course! https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/418
Replied
Great post!
Webmentions are indeed not super straightforward to implement if you are building them yourself, but the same could be said about any comment system.
The difference is a lot of CMSs and tools have already abstracted the complexity of comments but not so much with webmentions. But I am sure that will change with increased adoption.
Replied
Yeah it's super handy! Although I sometimes find my server doesn't always generate a preview.
I actually just moved the repo this week and need to update that old one. New repo is https://github.com/alltogethernow/web
Replied
Thanks Johan! I put a bit of work into how to subscription functionality for this newer version so I'm glad you like it
Replied
Whatsapp is not nearly as bad. It doesn't need any personal details apart from a phone number and everything is end to end encrypted. I'm sure Facebook will get some tracking and ads in there at some point but they haven't yet.
Replied
Yup and my photos cannot do myself or the scenery justice. I also need to get around to posting the rest of my travel photos. I am a bit slow with those
Replied
See https://grant.codes/2017/11/23/5a172628023c9d2ae6fbbe9a for reasons why
Replied
Renting a vehicle is the best way to go if you can. And I would say most of Utah or the North Pacific Coast are probably some of the best places to visit
Replied
Good writeup! I love having my instagram feed in my reader. I did it the same way.
On your caveats:
- I manage to automatically syndicate stuff to instagram , but it uses their unofficial api and could die at any time.
- I think you discovered that you can only have once instagram cookie per browser at a time, so whenever that expires / changes is when the session is expired and you need to update granary. I don't know how long it lasts, but if you never touch instagram in the browser it is quite a while.
I can also highly recommend doing something similar for twitter via granary if you don't already have that set up.
In the future I hope to integrate granary into together in someway to make it trivial to follow public instagram and twitter accounts :)
Replied
Ah ok, I think you have RelMeAuth setup but you also need to set your authorization endpoint like: <link rel="authorization_endpoint" href="https://indieauth.com/auth">
Replied
Hmm having a look manually I can't see your authorization endpoint. How is it set up?
Replied
I've been looking for a reason to get into that sort of stuff professionally after doing some personal projects
Replied
That one has been around for years! Think it's the computer security conference
