If you don't control the headers of your webserver (eg GitHub Pages) I would settle for a symlink favicon.png that just links back to favicon.html which I think would trick the server into returning different Content-Types.
710 karma · joined June 8, 2016
If you don't control the headers of your webserver (eg GitHub Pages) I would settle for a symlink favicon.png that just links back to favicon.html which I think would trick the server into returning different Content-Types.
You could always just take people's parcels and use an existing solution at first and eat the price difference, then once you have enough volume on the parcel supply side you can onboard some carriers.
When I was growing up in the 90s with 2 siblings we had a small hatch. When I had my second child we had to upgrade from a small hatch to an SUV because we simply couldn't fit a car seat behind the driver. Even now, I'm not sure if a third would fit.
Sure, the SUV itself and the extra padding on the car seats might make my children safe in collisions with other big cars, but if we were all still driving hatches then maybe none of that would be necessary.
We are in the stupidest arms race.
Kent Beck calls this the Explore and Extract phases (with the middle phase being Expand). I'm not sure if you had this talk in mind as you were writing your comment, but if not I think it'll resonate with you.
The key to writing good content is just writing lots of content. Some, maybe most, will be crap. That's fine, just don't promote the bad ones.
I recently read the entire Joel on Software archive and realized that the vast majority of posts are fairly uninteresting, but from over 1,000 posts he has a handful of classics and promotes those through the reading lists.
As for "older posts may still updated", I suggest don't do this, unless your site really is more like a wiki than a blog. It's annoying for readers to have to reread old posts and try to spot the difference, it means they can't bookmark a post they like and send it to friends without fear it might change. It's annoying for you because you will end up obsessively trying to perfect old posts. I prefer the approach of just writing a new post if you think you have a substantial amount of new/different information to add, and then you can also show what changed and why. This also means you can go back through your archives and see how your thoughts have changed over time.
I think once a week for Tavern should be suitable - you aren't trying to compete with Twitter or other social media sites for volume of content. I haven't signed up yet, but you might need to use email nudges to remind people to post. A streak count might be a good way to gamify persistence. Could you provide some examples on the main page of the kinds of prompts you'll be using, so I know whether I'm likely to be able to go through with it before giving up my email address? And finally, my concern with content reset at the end of each week is that if I am late to post I might only get a really small window to read other posts. Similarly, everybody else will have a small window to read _my_ post, and they might not even check the website during that time. Perhaps a couple of days grace period into the next week to read but not to post?
Edit: I just signed up, and it's awkward that you can't easily navigate back to the landing page when signed in, to remind myself of the rules.