HN user

clusmore

710 karma
Posts6
Comments282
View on HN

I'd love to see you try serving the exact same file for both but the trick is that you need to return different Content-Type headers depending on what is requested. When the browser requests /favicon from a navigation event it will use Accept: text/html etc, you return the file with Content-Type: text/html and inside the response you have a <link rel="favicon" href="/favicon" type="img/png"> literally the same resource but the browser will now likely fetch with Accept: image/... and you could return the same file with Content-Type: image/png and the same resource will get used for both. Unless the browser caches the response, I feel like this would work.

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.

What is the value prop to the package owner? Is it just that you expect this to be cheaper than existing options because random people who are already going somewhere anyway can make a few extra bucks by taking a parcel with them?

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.

The issue is that the investors will want a return on that $17M at some point, so they're going to need to charge money for something eventually. If the revenue model is not obvious now, that only means they'll be pressured into something non-obvious later.

I also think that modern car seats are one of the main factors driving the adoption of unnecessarily large cars, which have far worse safety outcomes in crashes for everybody except the people inside them.

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.

I am an Australian Instagram user in my 30s. When setting up my profile a few years ago I set the birthday to some fake date near my real age. At no point, including when the ban went live, was I ever asked to prove my age through any means. Nobody I know has either (noting that everyone I've asked is an adult).

I suppose both companies are well known for confidently stating absolute nonsense as fact, so it's a match made in heaven.

A lot of companies have started doing this because a compromised account can be used to attack the service (logged in sessions avoid rate limits) or other users (spam). They aren't necessarily trying to protect you.

The growth mindset is incredible for expanding when your product is in its early ages. But there should be a "sustain" mindset at some point. First you push to grow the market, or your market share. When returns on your efforts become diminishing, you push to improve how much you earn of each customer/each sale. At some point there should be a mindset that our company is worth X dollars, and we should sustain that.

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.

[1] https://youtu.be/YGhS8VQpS6s

Note that an integer offset is insufficient. For example, Australian Central Standard time is +9:30 and Australian Central Western Standard Time is +8:45. I have a Seiko watch with a similar feature to this and I don't think it would work well in either of these timezones.

https://blog.codinghorror.com/quantity-always-trumps-quality...

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.

Have you tried turning animations off? The setting should be in the Accessibility section somewhere. When you open an app from the app drawer, there is that little animation where the app icon grows, the screen fades to white/black, and then the app display fades into view, which all adds up to about 100-500ms. If you disable the animation it should open almost instantly.

I like Joel on Software's reading lists. Basically tags but only for a very small subset of posts which are very good, hand-curated with purpose.

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.

You've left the door open for a product management finder solution implementer. You figure out what problem to solve but you must use AI/Blockchain/Kubernetes to solve it.

To clarify my point, especially in politics there is a good chance that the post with the highest score might not even have support from a majority of people who voted (it could be 45+/15=/40-, so 45% support), might not even be voted on by a majority of the people who see it (10% of views vote, so that's 4.5% of viewers support), might not even be viewed by a majority of users (10% of all users view the post, so 0.45% of all users support), and a majority of electors are not users of your app (generously 10% market penetration is now 0.045% of electors support). I'm not sure decision makers would take these numbers seriously until you get huge market share and huge engagement/participation. I would suggest starting in much smaller markets where you can increase those percentages dramatically, and then expand from there.

It is _extremely_ unlikely that the highest ranked post will get even a majority of users having upvoted it, much less a majority of people - first past the post voting rarely achieves a majority even with only a handful of candidates to choose from. If you're curious about this as an experiment, my suggestion is to start much smaller and less divisive than world politics with infinitesimally small market penetration. Try your neighborhood, school or organization where you have a hope of double digit market penetration and some hope of getting buy-in from the decision makers you are trying to influence.

I like the idea. I actually set up something kinda similar to this at work, a sort of bookclub where once a week somebody posts a short video/blog/article for the group to consume and discuss, with the hidden goal of getting at least myself to churn out a blog post each week based on the discussion. We are currently in the third week but first post still because despite getting a dozen or so sign-ups, the follow-through has been low and feedback has been that more time is needed.

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.