# Fake aficionado

**URL:** https://meta.discourse.org/t/fake-aficionado/100412
**Category:** Bug
**Created:** [25 oktober 2018 om 01:47 UTC](https://meta.discourse.org/t/fake-aficionado/100412 "2018-10-25T01:47:57Z")
**Posts on this page:** 11
**Page:** 1

<div class="post-metadata">

### Author: ![dfabulich](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/dfabulich/32/108716_2.png) [@dfabulich](https://meta.discourse.org/u/dfabulich)
#### Post date: [25 oktober 2018 om 01:47 UTC](https://meta.discourse.org/t/fake-aficionado/100412/1 "2018-10-25T01:47:57Z")

</div>

I just received a notification from [meta.discourse.org](http://meta.discourse.org) telling me that I’d earned the Aficionado badge for visiting 100 days in a row.

But that’s not correct. I almost never visit [meta.discourse.org](http://meta.discourse.org) unless I have a particular thread or bug report to follow up on. I didn’t visit yesterday, or the day before that. I wouldn’t have visited today if I hadn’t received a notification.

I do have [meta.discourse.org](http://meta.discourse.org) configured in my iOS Discourse app. I wonder if its poll for notifications was somehow mistaken for site activity?

---

<div class="post-metadata">

### Author: ![codinghorror](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/codinghorror/32/110067_2.png) [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [25 oktober 2018 om 01:54 UTC](https://meta.discourse.org/t/fake-aficionado/100412/2 "2018-10-25T01:54:45Z")

</div>

Good point, I’m not sure but that sounds plausible to me. cc @sam

---

<div class="post-metadata">

### Author: ![sam](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sam/32/102149_2.png) [@sam](https://meta.discourse.org/u/sam)
#### Post date: [25 oktober 2018 om 08:11 UTC](https://meta.discourse.org/t/fake-aficionado/100412/3 "2018-10-25T08:11:49Z")

</div>

Yes this is a side effect of having the app, technically it is a sort of visit cause it ask meta for information, I guess we can add a special bypass

---

<div class="post-metadata">

### Author: ![codinghorror](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/codinghorror/32/110067_2.png) [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [25 oktober 2018 om 08:30 UTC](https://meta.discourse.org/t/fake-aficionado/100412/4 "2018-10-25T08:30:43Z")

</div>

Yeah this is a bug. He didn’t actually visit.

---

<div class="post-metadata">

### Author: ![sam](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sam/32/102149_2.png) [@sam](https://meta.discourse.org/u/sam)
#### Post date: [25 oktober 2018 om 08:31 UTC](https://meta.discourse.org/t/fake-aficionado/100412/5 "2018-10-25T08:31:42Z")

</div>

We can not fix this retrospectively but I can investigate adding bypasses for user api

---

<div class="post-metadata">

### Author: ![codinghorror](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/codinghorror/32/110067_2.png) [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [25 oktober 2018 om 08:31 UTC](https://meta.discourse.org/t/fake-aficionado/100412/7 "2018-10-25T08:31:55Z")

</div>

Totally fine, not worried about history.

---

<div class="post-metadata">

### Author: ![TheBestPessimist](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/thebestpessimist/32/247704_2.png) [@TheBestPessimist](https://meta.discourse.org/u/TheBestPessimist)
#### Post date: [25 oktober 2018 om 08:32 UTC](https://meta.discourse.org/t/fake-aficionado/100412/8 "2018-10-25T08:32:23Z")

</div>

related to this: i am pretty sure i have visited meta (and a few more sites) for more than 100 days and still didn’t get this particular badge. is there any way to check this count?

---

<div class="post-metadata">

### Author: ![codinghorror](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/codinghorror/32/110067_2.png) [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [25 oktober 2018 om 08:32 UTC](https://meta.discourse.org/t/fake-aficionado/100412/9 "2018-10-25T08:32:56Z")

</div>

You have to visit for 100 consecutive days. This is not the topic for that discussion.

---

<div class="post-metadata">

### Author: ![david](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/david/32/157490_2.png) [@david](https://meta.discourse.org/u/david)
#### Post date: [25 oktober 2018 om 12:49 UTC](https://meta.discourse.org/t/fake-aficionado/100412/10 "2018-10-25T12:49:21Z")

</div>

I realised this was a regression I introduced in July while solving [a different](https://github.com/discourse/discourse/commit/2dc3a50dacb2aa699b0c68c9abf8fcc5436dc81b) `last_seen` bug. API and User API access should not update last\_seen, and therefore should not create a visit record. Should be fixed by:

[https://github.com/discourse/discourse/commit/56e0f47bcd183f9d8e5cde853bcb9f8fe38eebf7](https://github.com/discourse/discourse/commit/56e0f47bcd183f9d8e5cde853bcb9f8fe38eebf7)

---

<div class="post-metadata">

### Author: ![codinghorror](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/codinghorror/32/110067_2.png) [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [25 oktober 2018 om 23:35 UTC](https://meta.discourse.org/t/fake-aficionado/100412/11 "2018-10-25T23:35:36Z")

</div>

Oh good news so this is only a bug from July not 2016 😉

---

<div class="post-metadata">

### Author: ![david](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/david/32/157490_2.png) [@david](https://meta.discourse.org/u/david)
#### Post date: [29 oktober 2018 om 18:00 UTC](https://meta.discourse.org/t/fake-aficionado/100412/12 "2018-10-29T18:00:09Z")

</div>

This topic was automatically closed after 4 days. New replies are no longer allowed.
