IndieWeb

On a lot of IndieWeb sites, I noticed that profile images of webmentions get directly embedded from their original source. For example, Twitter profile images are loaded directly from Twitter servers (pbs.twimg.com) or even my profile image is directly embedded from my site. However you should consider enabling Content Security Policy (CSP) headers and only allow embedded content from trusted sites (your own domains). It could always happen that a site gets hacked and malware injected or a domain expires and some spammers register it again, that will also affect your website's visitors.
I finally did what I thought about a few months ago: I finally deleted my Twitter account (or rather deactivated it, it will be deleted if I do not log in for another 30 days). I am done with Twitter. I realized that I often only open Twitter when I want to be distracted or procrastinate. I typed “twitter.com” in the address bar of my browser, just to scroll a little and then close the tab again.

This is a chicken-and-egg problem. Until enough websites are using Indieweb standards to publish content, it will remain a niche.

This makes the Indieweb necessarily a fairly tech-centric space. However, I don't believe that this makes it less valuable. The Indieweb is a new technology, though it happens to be built on top of some very old ones. New technologies are always inhabited by tech types at the beginning.

I think it's not a problem for non-IndieWeb users to read IndieWeb pages though. Most often they won't even notice it's an IndieWeb site, when they come there by accident (e.g. a search or link from somewhere else).

After thinking about it, I finally figured out how to PESOS from Pocket to my own site using IFTTT. I tried to do it in a similar way to how Charlotte Allen did this. The first step was to retrieve an IndieAuth access token using the tool Gimme a token. Then I created a IFTTT applet with the a new favorite item on Pocket as the trigger and a Webhook to execute.

The first things I did this year was to create a media endpoint for my Micropub server. It works by uploading files to BunnyCDN via their storage API (great service and easy API!). However, now that I have this endpoint, I would also like to use it. It seems that there is a lack of clients that support uploading media to the media endpoint and then returning me the correct URL. I can use Indigenous to upload photos from my phone, but it seems like other file formats aren't supported. How am I supposed to create posts with audio or other files? Also Micropublish (the client I usually use on PCs) doesn't seem to support media at all.

Can someone please give me a tip, which client I should use or do I need to develop my own? Thanks!

Please also remind: My operating system are Linux, Windows and Android. Clients for macOS or iOS are pretty useless to me.

Update: Kristof De Jaeger replied to this post and promised some new features for Indigenous on Android. Thanks a lot! I'm still in search for a desktop solution though. I thought a bit about it and will probably create a basic web interface that allows me to upload any file until there's better support in other Micropub clients.

Update 2: It seems like Jamie Tanna is in a similar situation. He gave the tip to look at Quill.

I should definitely checkout how to PESOS for Pocket. I use Pocket quite often, but don't publish all links on my blog. For that I still need to improve bookmark support and than use something like IFTTT to publish recommended or starred articles to a bookmarks section.

Self-hosting my blog and the related services not only gives me the independence from third-party-services, it also gives me the option to customize things to my liking. In my opinion, this is even more important. I moved domains several times, merged blogs etc. and to keep links working there are a lot of redirects in place. That wouldn't be possible with a service like micro.blog or at least not with its current features.

Thanks for your tip to take a look at the post by Steve Layton! Unfortunately I'm not using micro.blog currently and rather want my setup to be self-hosted as much as possible. To do that I recently also started receiving webmentions myself instead of relying on webmention.io. It's not that I don't like these services, it's more that I strive for full control over my setup.

My IndieWeb setup is continuing to evolve. I just added support for syndication (this post should appear on IndieNews) and JSON-posting to my Hugo backend and theme. Unfortunately, adding support for more IndieWeb features to this setup requires a lot of documentation reading, reverse engineering and looking at how other people have done that (of course in other programming languages, one has not much knowledge in). All this effort is redundant, because there's already WordPress with all its IndieWeb plugins.
Jan-Lukas Else
20 years old student who writes about everything he cares about.