Topic: [APPROVED] Holiday aliases

Posted under Tag Alias and Implication Suggestions

The bulk update request #7511 is active.

create alias easter2024 (2) -> easter (4559)
create alias easter_2024 (3) -> easter (4559)
create alias valentinesday2024 (1) -> valentine's_day (5565)
create alias valentine's_day_2024 (4) -> valentine's_day (5565)
create alias christmas_2024 (1) -> christmas (33761)
create alias christmas_2023 (2) -> christmas (33761)
create alias inktober2023 (0) -> inktober (1643)
create alias halloween_2023 (0) -> halloween (24205)

Reason: Unnecessary year specific holiday/etc tags.

EDIT: The bulk update request #7511 (forum #400246) has been approved by @Cinder.

Updated by auto moderator

coffeeco said:
But doesn't "year + event" work exactly the same when searching?

from topic #34866

faucet said:
I'm not really sure if I'd want multiple tags for every possible new year, but searching new_year 2023 is going to produce a mixed bag of results for:
1) actual 2023 new year, at the start of the year
2) new year 2024, posted at the end of 2023 before the year changed
3) posts from any previous new year that were posted late, backlogged posts, etc.

The question to me is: does any of the above actually matter?

They're definitely not the same - but the real question is do we care?

CoffeeCo

Privileged

faucet said:
from topic #34866

They're definitely not the same - but the real question is do we care?

I personally don't. But the existence of those tags probably means some people care.

Creating holiday_[year] tags that can be combined with a specific holiday might be a good compromise. It minimizes the amount of tags, still allows for searching a specific instance of a holiday, and is more favorable to obscure holidays like pi_day or vore_day

I think new_year_[year] could be useful and worth keeping for the reasons Faucet gave. Not the others though, since any holiday except new year would be searchable with the holiday + the year tag ex. halloween 2023

  • 1