Difference between revisions of "Talk:Hashiversary achievement"
imported>Ekorren (Not reached vs. Did not attempt) |
imported>Robyn (Because you've seen what happens when people interpret ambiguous area fro themselves.) |
||
Line 16: | Line 16: | ||
Maybe a honorable mention could be for going within of one week after the correct day, just like people often celebrate their birthday not on the exact date but a few days later, and almost never before. Whatever a honorable mention would be for, or whether there will be one at all, I think the true achievement should only be valid on the true day, and in this variant I ''support'' it. If you can't go then, or the coordinates are just crap, it's bad luck. You have another chance a year later. There are so many achievements you'll never get a chance, no matter how long you wait, anyway. --[[User:Ekorren|Ekorren]] 10:55, 25 May 2009 (UTC) | Maybe a honorable mention could be for going within of one week after the correct day, just like people often celebrate their birthday not on the exact date but a few days later, and almost never before. Whatever a honorable mention would be for, or whether there will be one at all, I think the true achievement should only be valid on the true day, and in this variant I ''support'' it. If you can't go then, or the coordinates are just crap, it's bad luck. You have another chance a year later. There are so many achievements you'll never get a chance, no matter how long you wait, anyway. --[[User:Ekorren|Ekorren]] 10:55, 25 May 2009 (UTC) | ||
− | :I agree with the "there are some achievements that never get a chance" argument and that it should have to be on the exact date. My February 29th comment was mainly intended as a way of saying "address the non-obvious cases", which that discussion has brought out. I think the description could make it more crystal clear that neither the original nor the anniversary attempt has to succeed, and you'll need to define "go geohashing" in this case. If I look up the coordinates and look longingly in that direction, I probably don't get the ribbon, but what if I walk 8 km towards coordinates that are 50 | + | :I agree with the "there are some achievements that never get a chance" argument and that it should have to be on the exact date. My February 29th comment was mainly intended as a way of saying "address the non-obvious cases", which that discussion has brought out. I think the description could make it more crystal clear that neither the original nor the anniversary attempt has to succeed, and you'll need to define "go geohashing" in this case. If I look up the coordinates and look longingly in that direction, I probably don't get the ribbon, but what if I walk 8 km towards coordinates that are 50 km away, and then come home to bed? (Something that is likely to be my only way to geohash on my hashiversary next week). What if I go to an alternate instead? I'm sure it doesn't have to be in the same graticule. Basially answer every question that could come up so there aren't arguments later. -[[User:Robyn|Robyn]] 14:26, 26 May 2009 (UTC) |
::When defining the hashcard achievement, I used the wording: ''You can earn this achievement without reaching the coordinates, but not without seriously trying to get as near as possible'', complete with an example of an expedition which was doomed to not reach the coordinates from the beginning. This could well also work here, and for a number or other achievements. I hesitate to call visiting alternate coordinates a geohashing expedition in general, and would strongly prefer that they don't count. Of course the graticule should be of no concern. --[[User:Ekorren|Ekorren]] 14:39, 26 May 2009 (UTC) | ::When defining the hashcard achievement, I used the wording: ''You can earn this achievement without reaching the coordinates, but not without seriously trying to get as near as possible'', complete with an example of an expedition which was doomed to not reach the coordinates from the beginning. This could well also work here, and for a number or other achievements. I hesitate to call visiting alternate coordinates a geohashing expedition in general, and would strongly prefer that they don't count. Of course the graticule should be of no concern. --[[User:Ekorren|Ekorren]] 14:39, 26 May 2009 (UTC) | ||
+ | |||
+ | :::In other words, because I've left this unsaid, this is a good, workable, interesting and desirable achievement that merely needs to be fleshed out so that anyone who follows the rules deserves the achievement, and anyone whom the rules excludes really didn't deserve the achievement. And I added a missing k to my earlier comment. -[[User:Robyn|Robyn]] 16:22, 26 May 2009 (UTC) |
Revision as of 16:22, 26 May 2009
- Support - you think this proposal should be added with zero or minor changes
- Do not oppose - you think it's boring/meh/not for you, but it wouldn't harm to have it created
- Oppose - you have a specific reason as to why this ribbon should not exist (state this reasoning in your comment)
- Needs work - you think the achievement should be created after more significant changes have been made
See Proposed achievements for more information on this process.
I support this achievement! Although I like the name Geohashiversary better. Thepiguy 16:39, 22 May 2009 (UTC)
I also support it, just for the record. Geohashiversary is a bit long, IMO, but I do not oppose the name. I am definitely going hashiversaring on my hashiversary, and I assume others might want to do that too. -- relet 21:03, 22 May 2009 (UTC)
I love it. I want to see more a provision for February 29th, and clairify if it should be the anniversary of the first successful geohash or the first attempt, no matter how lame. NW -Robyn 21:12, 22 May 2009 (UTC)
I don't like the way you've treated 29 February. I can see somebody saying to themselves "I like the idea of this geohashing thing. Now, when shall I go on my first expedition. Hey, 29 Feb is coming up -- that will make it really special!". And also, it is difficult to get this ribbon if you are not able to go hashing on every day of the week. I think that you should be able to celebrate your hashiversary either on the same date of your first expedition, or on a date which is the same day of the week as your first expedition, and is the instance of that day which is nearest the exact date anniversary. (So hashing on Friday 29 Feb 2008 would allow you to celebrate on Friday 27 Feb 2009, Friday 26 Feb 2010, and would presumably give you a choice of Fridays in 2011; either 25 Feb or 4 March). At the moment I do not oppose the achievement, but I also think it needs work and then I will support it when this is done. -- Benjw 08:57, 25 May 2009 (UTC)
- I honestly don't think we have to consider those who choose Feb 29 deliberately. If you think that Feb 29 is something special, take your time to reconsider *why* it is special. I would have been worried if there were a Feb 29, 2009 and people had hashed on that day before. But we can still create a (gratuitous) ribbon for the Hashiversary (observed) if it ever happened. -- relet 09:18, 25 May 2009 (UTC)
- Ok, the 29 February problem is a red herring; ignore it. But people not being able to go hashing on weekdays might well still be a problem. I do still think that you should be able to celebrate your hashiversary on the same day of the week as your first hash, not just on the exact date. I know dates are important for hashing itself, but to make the same distinction for anniversaries of hashing is overly exclusive, I think. In principle I support this achievement, but with the date restriction as it is now, I merely do not oppose it. -- Benjw 09:47, 25 May 2009 (UTC)
- And how exactly does the "same day of week" solve the "can't go each day" problem in case the first expedition was on a weekday (or whatever day your regular obligations do not allow you to go one year later)? My first expedition had been on a tuesday. --Ekorren 09:55, 25 May 2009 (UTC)
- My chance for this achievement is in two days (Wednesday). There's a very good chance I won't be able to make it due to work, but I may get lucky. Regardless, I think that it should have to be the same day to get the achievement. If you're going to implement some other method such as the same day of the week, then make it Hashiversary (alternate) or something like that, but at least leave the Hashiversary itself as the same day. It's meant to be like a birthday or anniversary from how I understand it, and those are a calendar date. Also, in case it's not clear, I support this achievement! -Srs0 10:11, 25 May 2009 (UTC)
- Ok, the 29 February problem is a red herring; ignore it. But people not being able to go hashing on weekdays might well still be a problem. I do still think that you should be able to celebrate your hashiversary on the same day of the week as your first hash, not just on the exact date. I know dates are important for hashing itself, but to make the same distinction for anniversaries of hashing is overly exclusive, I think. In principle I support this achievement, but with the date restriction as it is now, I merely do not oppose it. -- Benjw 09:47, 25 May 2009 (UTC)
I support it if it's for the same day of the year, maybe with a honorable mention for those who go on the same day of the week. We shouldn't make achievement requirements more complicated just to make the achievement easier. --ilpadre 10:46, 25 May 2009 (UTC)
Maybe a honorable mention could be for going within of one week after the correct day, just like people often celebrate their birthday not on the exact date but a few days later, and almost never before. Whatever a honorable mention would be for, or whether there will be one at all, I think the true achievement should only be valid on the true day, and in this variant I support it. If you can't go then, or the coordinates are just crap, it's bad luck. You have another chance a year later. There are so many achievements you'll never get a chance, no matter how long you wait, anyway. --Ekorren 10:55, 25 May 2009 (UTC)
- I agree with the "there are some achievements that never get a chance" argument and that it should have to be on the exact date. My February 29th comment was mainly intended as a way of saying "address the non-obvious cases", which that discussion has brought out. I think the description could make it more crystal clear that neither the original nor the anniversary attempt has to succeed, and you'll need to define "go geohashing" in this case. If I look up the coordinates and look longingly in that direction, I probably don't get the ribbon, but what if I walk 8 km towards coordinates that are 50 km away, and then come home to bed? (Something that is likely to be my only way to geohash on my hashiversary next week). What if I go to an alternate instead? I'm sure it doesn't have to be in the same graticule. Basially answer every question that could come up so there aren't arguments later. -Robyn 14:26, 26 May 2009 (UTC)
- When defining the hashcard achievement, I used the wording: You can earn this achievement without reaching the coordinates, but not without seriously trying to get as near as possible, complete with an example of an expedition which was doomed to not reach the coordinates from the beginning. This could well also work here, and for a number or other achievements. I hesitate to call visiting alternate coordinates a geohashing expedition in general, and would strongly prefer that they don't count. Of course the graticule should be of no concern. --Ekorren 14:39, 26 May 2009 (UTC)
- In other words, because I've left this unsaid, this is a good, workable, interesting and desirable achievement that merely needs to be fleshed out so that anyone who follows the rules deserves the achievement, and anyone whom the rules excludes really didn't deserve the achievement. And I added a missing k to my earlier comment. -Robyn 16:22, 26 May 2009 (UTC)