P83 by Peter Stuifzand

Bridgy certainly could, but I don't know if it does. In my case my posts are stored as plaintext or markdown internally, and my site is the one pushing to github, not using Bridgy at all.

16 Apr 2018 at 02:27

Peter Stuifzand replied to a post on aaronparecki.com

My website converts the Markdown to HTML and Bridgy converts it back to Markdown. It's quite magical the first time it happens.

I usually drop a little function into my projects function pa($a) { echo '<pre>'.print_r($a,true).'</pre>'; } for exactly that purpose. Then you can use pa() in place of print_r().

18 Apr 2018 at 16:17

Peter Stuifzand replied to a post on aaronparecki.com

It's like var_dump($x); die(); until you have dd($x).

An IndieWeb reader: My new home on the internet https://t.co/zzPdILQD6i #indieweb

#

Peter Stuifzand liked a tweet by @aaronpk Apr 20 at 21:50

My archive page shows that writing on the new blog is much easier than writing on the old blog. Now I write almost every day.

Peter Stuifzand created a new issue for willnorris/microformats

Parsing html with an invalid url will crash Parse

The microformats parser will crash when url.Parse returns an error. The "parsed" will be nil and this will crash inside ResolveReference.

I found it while parsing: https://chat.indieweb.org/dev/2018-04-17. This will also crash when run with gomf https://chat.indieweb.org/dev/2018-04-17

https://github.com/willnorris/microformats/blob/bc552049783fddac99a36ffb65bf3c99f12b64d7/microformats.go#L226

At La Cucaracha, Zwolle Overijssel Netherlands

I have just added an image proxy between my blog and the profile pictures on the blog. In the future I will look at how to use it for the images in the posts.

Peter Stuifzand starred willnorris/imageproxy Apr 18 at 13:50

I will like to combine my old and new websites into one page. The old site is statically generated. I have been writing there since 2004. So there is quite a bit of history there. I would need to convert all that to the new backend, so I fill in the gap from 2004 to now.

I have heard of people also convert Facebook and Twitter posts into their new websites. Perhaps this is something that I should also do, especially since Facebook and Twitter, may one day stop working.

In the current situation I have some more posts and Facebook, Twitter and perhaps Github. All of it could be transported here (somehow).

What do I still need:

Public/private settings for posts
Photo album style pages
A page where I can list all the companies that are getting some of my information 😉

I still need to build a way to receive webmentions on other places than the normal posts. I need to extend the storage backend to be able to store the posts and an interface to be able to view and reply to this mentions. It's a great way to add cc to a post and message other people in the Indieweb.

Parsing html with an invalid url will crash Parse

Bio

Elsewhere