vikingtons

Update: to whomever referred to the UK's ICO as a toothless organisation, I think I owe you a pint.

On the morning of Monday, 2024 11 25, I received a text message from my bank notifying me of a potentially fraudulent transaction of $0.00. This resembled some kind of a service test charge.

I was amused to see this was sufficient to trigger such a response from my bank. My account had been paused and my card transactions were halted as a result, though I'm grateful for their diligence.

Looking at the message, it appears to have been from Blizzard Entertainment:

The first time I dealt with them as a customer was around 2016 or 2017. Overwatch was on sale and my friends urged me to pick it up. It wasn't my sort of thing and I quickly put it back down.

I was stupid enough to buy Destiny 2 later on in 2017. The long-timers (or most likely, former players) amongst you may recall that D2 was only available through BattleNet on PC. I think they moved away to Steam a couple years later after parting ways with Activision, and I linked my Steam account to complete the transfer around this time.

Fast-forward to October 2019 and the "Blitzchung controversy". I don't wish to expand on the topic here. I didn't agree with Blizzard's actions around that event, nor did I have any particular reason to retain my online account with them, so I decided to delete it in some extremely minor form of protest.

It seems that a significant number of account holders thought of doing the same thing, as Blizzard started to demand some form of government photo ID to proceed.

I can only presume they employed this tactic as some sort of deterrent, though I was fairly sure it couldn't legally be enforced; what business did they have to ask this of me? They've never needed my drivers license or passport photo before?

After a lengthy back and forth with their support agents, I decided to send them a GDPR data erasure request instead. They immediately honoured my request and notified me that my account and all associated PII would be removed from their systems.

Just over five years later, and I'm randomly greeted with this fraud alert. Mondays are particularly busy for me, as I'm sure they are for many of you. I cursed as I glanced at phone that morning. I don't need more stuff to deal with.

I immediately called my bank and rectified the situation, though I wanted to understand how this happened to begin with. Whilst I was still on the phone to them, I confirmed that:

• My last payment to Blizzard Entertainment was in 2017 (2 years prior to my GDPR data erasure request)
• The attempted transaction on Monday originated from Irvine, US (location of their HQ - it wasn't someone using my card details)

I decided to write to Blizzard's customer support. They appear to have a section dedicated to unauthorised payments. My endeavours were unsuccessful.

After explaining all of the above, I pressed them on several key points:

• What is the purpose of this charge and why did this happen?
• What data are you retaining on me?
• Has another user attempted to use my payment information (at this point, I've no reason to suspect my payment info has been compromised)
• What will you do to prevent this happening again?

I wasn't satisfied with the first response, so I tried again later on.

Check if you have an active World of Warcraft subscription

Couldn't you folks have done that?

Check your recent purchases in your Transaction History

(I had already explained that I had done this as part of my initial query to them)

Make sure that you are logged in to the correct Blizzard account

"An extensive research" to be sure

All of these questions were completely sidestepped. I began to suspect that these were bot generated or generic, canned responses.

If you are indeed real people, and you somehow stumble upon this post, please know that I'm sorry to call you out, and I know you're dealing with my case using the resources you have available.

So why am I mentioning any of this here?

I would love to know if any of you took the same action as I did back in 2019:

• Did you attempt to close your account following the HK tournament controversy?
• Did you face the same level of resistance as I did?
• Did you follow up with a data erasure request?
• Do you have any reason to suspect that Blizzard are still retaining data on you in 2024?

An associate of mine has pointed out that they may have a legal obligation to retain some records despite my request for data erasure. The question is, why was this service test charge placed?

Thank you for reading through my ramblings.

Have a cosy one.

Hey there,

Not sure if this is actually more of an Android system limitation, but I came across this post earlier:

https://lemm.ee/post/45289052

The feed renders the linked .SVG graphic as expected, though the image lightbox (image view when tapped on) doesn't appear to render this. The AOSP gallery / files app and Google Photos app appear to also be incapable of rendering this, however.

Disregard, - it works now for me now 😅

Hey there,

This is an extremely minor quirk with how the image lightbox (apologies if I'm using web specific terms) behaves when a post image is selected from the feed and put into full screen mode.

On devices with on-screen nav and expanded status bar areas (camera hole design concession), the lightbox will show end to end with the UI controls overlayed.

If you tap once on the image to hide the UI elements, the status bar area is filled, whereas the nav area still shows as expected, though the image appears to resize slightly in response to the change in viewport. Wondering if this was intentional?

Video link here: https://imgur.com/a/NG74wiO

Truly the most P4 item I could think of but was curious.

Pixel 7 | Android 14 | Lemmy 0.0.75

E: fixed in 0.0.75 - thank you MV :)

Hey there,

I was wondering if anybody else was experiencing this behavior where the swipe to navigate back gesture would register twice within the app, taking you back two steps instead of just one.

I'm not sure exactly when this behaviour was introduced, though it persists with today's .72 alpha release. I was to say it came about in the .6X timeframe.

I've not found this reported on the github, though I just wanted to check that this isn't a system specific issue before submitting. #1399 may be relevant as it refers to swipe input sensitivity but I think that's more of a gesture threshold matter than input registering twice in the app.

My app settings are attached in a photo:

and I have a short clip:

https://imgur.com/a/YOIKbtE

Steps to reproduce:

• Using the provided gesture settings in Jerboa
• From the home feed, tap into a community name
• From the community view, tap into a community post
• Swipe left to navigate back to the community view
• Observe two steps back in response to a single input

Pixel 7, Android 14

Got back home, took my top off and was surprised to see this little guy clinging onto the back.

Took em out into the backyard and let them slowly crawl onto one of my plants. Not sure what kind of caterpillar this is but I think they were okay with their new spot.

https://streamable.com/5i7nr8