GDPR compliance DM response not being accepted on PixelFed

[iolaire]

Since the GDPR change I've [@iolaire@pixey.org] (https://pixey.org/@iolaire) responded multiple times to @altbot@fuzzies.wtf DM with consent via both Yes and I agree and the bot has not yet accepted the consent.

I should note that I also have an account on Mastodon [@iolaire@masto.ai] (https://masto.ai/@iolaire) which accepted the consent the first try.

Also I tried un following and re following a week or so ago and it didn't help.

Let me know if I can help debug this in some fashion.

I appreciate the tool and also the mention that you moved to Ovis2. I'm exploring using Ovis2 for my own image organization.

[micr0-dev]

I've never used pixelfed but just looking at the interface it is probably because they don't actually make a reply to the message. Its the equivalent of a new direct message post hmm

[micr0-dev]

yeah just as a suspected, I'll add a patch for this once I can think of something.

the real problem is that there is no way to know if this is a reply to this request or something else

[micr0-dev]

thanks for reporting this bug!

[iolaire]

Thank you. Not a huge priority but your tool is great so I miss it.

thanks for reporting this bug!

[iolaire]

How about allowing a non linked DM along the lines of:
I AGREE TO GDPR CONSENT STATEMENT
, to provide agreement outside of the DM/Response framework?

yeah just as a suspected, I'll add a patch for this once I can think of something.

the real problem is that there is no way to know if this is a reply to this request or something else

[micr0-dev]

sorry I am currently on vacation but I will implement something when I get back!

[iolaire]

sorry I am currently on vacation but I will implement something when I get back!
Enjoy your vacation!