💬 Comment on

Nice to read about your Indieweb implementations.

[…] I only build my blog hourly, [which] means webmentions can take up to an hour to appear on the site after being sent. Is that really bad UX? Do people really expect their webmentions to show up quickly on the target website?

I struggled with that, too, but I’ve settled for the static approach. I like to embrace the philosophy of slow web, so webmentions are only displayed once I decide to make changes to website (i.e. create new content). Wouter Groenevald (whose blog post about the Indieweb you almost certainly also read) recommended to use client side rendering, if you really need real time webmentions.

[…] the real fun will be implementing a micropub endpoint […]

That’s what I’m also planning to do. I’ll stay tuned for your results.

Pricetags indieweb

I’m beginning to forget my geospatial roots and becoming more and more a software engineer.

Recently, I tried “merging” GeoJson polygons based on a property, only to realize that this process is called “dissolving”.

I knew that at one point 🤦.


Pricetags gischat

Star 2 Likes

As a developer mom or dad, how do you skill up?

I’m about to have my 2nd child, but I’m struggling to learn new things, or even improve my development skills outside of the job. Do you have any tips?


Pricetags askfedi

Chatbubbles 5 Responses
Star 1 Like
💬 Comment on

Thanks for taking the time to read my ramblings! 😄

for “instant appearance” […] you could simply revert to client-side JS code.

I will definitely check that out and try to implement client side rendering for webmentions.

On the other hand, only rebuilding the site whenever new content is created, embraces the concept of slow web. I guess anyone taking the time to write a response could also wait until I feel the need to tell something new to show their face up on my site 😅.