Show titles should contain the leading digits in 'hpr0023' in the show id #119

New Issue

davmo · 2023-06-15T22:59:56Z

davmo commented

2023-06-15 22:59:56 +00:00

Potential confusion between show 'hpr0023' and 'hpr23' and similar

It was possible with the old HPR system to type an URL that ended as .../eps.php?id=23 which would have the leading zeroes added to arrive at hpr0023 behind the scenes. This may not have been a good idea!

Now, the URL https://hackerpublicradio.org/eps/hpr23/index.html fails, reasonably enough. The show identifier hpr0023 is not a number.

The shows are represented by identities on archive.org like hpr0023, and nothing else is acceptable.

So, it seems confusing when addressing https://hackerpublicradio.org/eps/hpr0023/index.html to see hpr23 in the title!

Example: hpr23 :: Software Review: K e e P a s s

#### Potential confusion between show 'hpr0023' and 'hpr23' and similar It was possible with the old HPR system to type an URL that ended as `.../eps.php?id=23` which would have the leading zeroes added to arrive at `hpr0023` behind the scenes. This may not have been a good idea! Now, the URL `https://hackerpublicradio.org/eps/hpr23/index.html` fails, reasonably enough. The show identifier `hpr0023` is not a number. The shows are represented by identities on archive.org like `hpr0023`, and nothing else is acceptable. So, it seems confusing when addressing `https://hackerpublicradio.org/eps/hpr0023/index.html` to see `hpr23` in the title! Example: `hpr23 :: Software Review: K e e P a s s`

ken_fallon commented

2023-06-17 18:33:20 +00:00

I know we discussed the padding before but should we drop it ?

rho_n commented

2023-06-18 10:25:32 +00:00

From a discoverability POV, Dave's suggestion makes great sense. Plus it would resolve our own upcoming Y2K problem or as the case may be S10K (show 10000) problem.

For me, the nice thing about the padding is when looking through the directories when do development. Show directories line up nicely, and you don't have to figure out how to tell your OS to sort numerically.

Overall, it is probably better to drop the padding.

From a discoverability POV, Dave's suggestion makes great sense. Plus it would resolve our own upcoming Y2K problem or as the case may be S10K (show 10000) problem. For me, the nice thing about the padding is when looking through the directories when do development. Show directories line up nicely, and you don't have to figure out how to tell your OS to sort numerically. Overall, it is probably better to drop the padding.

davmo commented

2023-06-19 10:19:43 +00:00

From a discoverability POV, Dave's suggestion makes great sense. Plus it would resolve our own upcoming Y2K problem or as the case may be S10K (show 10000) problem.

For me, the nice thing about the padding is when looking through the directories when do development. Show directories line up nicely, and you don't have to figure out how to tell your OS to sort numerically.

Overall, it is probably better to drop the padding.

Sorry, I don't understand the conclusion to drop the padding, especially given the above points.

The show number is just a number, but we use it in a text string hpr23/hpr0023, so in that context it's more than a simple integer
If we are consistent with the leading zeroes we cause less confusion especially since hpr23 on the static site (if we agree to no padding) is not the same as hpr0023 on the IA
Yes, perhaps we'd have been better to use a 5 digit numerical part in hpr<number> so we're ready for episode 1000, but that didn't happen.
If people hate typing https://hackerpublicradio.org/eps/hpr0023/index.html and want to use hpr23 then we could convert the one into the other (though that'd presumably need webserver rewrite rules to achieve).

My conclusion is: keep leading zeroes for consistency.

> From a discoverability POV, Dave's suggestion makes great sense. Plus it would resolve our own upcoming Y2K problem or as the case may be S10K (show 10000) problem. > > For me, the nice thing about the padding is when looking through the directories when do development. Show directories line up nicely, and you don't have to figure out how to tell your OS to sort numerically. > > Overall, it is probably better to drop the padding. Sorry, I don't understand the conclusion to drop the padding, especially given the above points. * The show number is just a number, but we use it in a text string `hpr23`/`hpr0023`, so in that context it's more than a simple integer * If we are consistent with the leading zeroes we cause less confusion especially since `hpr23` on the static site (if we agree to no padding) is not the same as `hpr0023` on the IA * Yes, perhaps we'd have been better to use a 5 digit numerical part in `hpr<number>` so we're ready for episode 1000, but that didn't happen. * If people hate typing `https://hackerpublicradio.org/eps/hpr0023/index.html` and want to use `hpr23` then we *could* convert the one into the other (though that'd presumably need webserver rewrite rules to achieve). My conclusion is: **keep leading zeroes for consistency**.

ken_fallon commented

2023-06-22 09:16:58 +00:00

The padding is a pain. There are two good reasons to keep it though, the sorting in a directory and the fact that the IA has them stored with the padded version.

Out of interest can we rename the IA sets ?

The padding is a pain. There are two good reasons to keep it though, the sorting in a directory and the fact that the IA has them stored with the padded version. Out of interest can we rename the IA sets ?

davmo self-assigned this 2023-07-23 15:39:06 +00:00

davmo referenced this issue

2023-07-23 15:52:39 +00:00

Various bug fixes #145

davmo added a new dependency 2023-07-23 15:55:45 +00:00

#145 Various bug fixes

davmo commented

2023-07-31 10:44:52 +00:00

This was done as part of the updates for issue #145

This issue can be closed.

This was done as part of the updates for issue #145 This issue can be closed.

ken_fallon closed this issue