🦊 helloyanis :veripawed3:

💻 #Opensource #developer!
🦊 #Furry #Fox
🇨🇵 #French
🖼️ Profile picture by @xanthe
🤔 I can’t think of any other bullet points

  • 18 Posts
  • 65 Comments
Joined 1 year ago
cake
Cake day: April 29th, 2025

help-circle
  • @Skyline969 I meant you won’t be able ti use the disc drive for that’s still being sold full price today for games beyond 2028. I edited the post to clear that up.

    Also, PC gaming is digital but most of the times you have the game files downloaded somewhere, you can make a backup, and unless the game is online only you can theoratically play it forever.

    With this, once Sony eventually takes down the store just like they did for the PS Vita, then you won’t be able to play games at all, and will very likely be the proud owner of a fancy black and white brick. They can also remove games from your library and this will make you unable to buy used games.













  • @bamboo Not sure if that’s exactly what you mean but each site can set up the age verification by loading a script and adding event callbacks, like redirect_url to set an URL to be redirected to once the verification is over, and onclosed which occurs when the verification is successful, and where the site can set some code to run.

    So if you just block the popup, it never appears and can never fire onclose and the code that happens after will never run.

    Since sites are often minified and obfuscated, and the call for the popup can come from any file, I just replaced the response to requests to the popup URL, to have my own script that fires the event and/or redirects to the page, so that it works every time.

    I think the only way to counter this is, if they change the URL (I can later update it too, or if a website hosts their own version of the file (so it will be at a different URL and be undetected). But all of these have easy workarounds as well.











  • @vapeloki The issue is, once again, not that the app allows you to bypass age verification or anything with how countries implement it. It’s that the app makes it extremely easy to get the data and spoof someone else, while claiming it’s secure and privacy focused while it is not.
    A prectical example would be :
    - Someone steals my phone
    - They can access the app as they can bypass the PIN
    - They can appear and act as myself on any platform that will use the system to verify
    No matter how countries implement it or how the app is still “in development”, I’m just saying that this current implementation is insecure and can be very easily hacked besides what is being said on the public spaces like the dedicated website and the twitter account of the president of the EU commission.
    I will probably stop replying to this thread now as you keep telling me the same arguments and even when I demonstrate how I disagree with them, you keep repeating the same ones so I’ll just stop wasting my time


  • @vapeloki I really don’t get what you say with “there is no app”. The repo is literally called " age verification Android application". It’s not an SDK
    Also, why shouldn’t it matter what Ursula said?The part of the readme you linked me mentions “In particular, any national-specific enrolment procedures must be implemented by the respective Member States or publishing parties”. This does not relate to the security of how data is stored.

    “The current version is not feature complete”, well, it’s not what I’m complaining about. The thing is the feature that are there are not well made and use an approach that don’t focus on security and privacy.

    Yes it’s a demo but if they want people to base their implementation based on that, then every implemenation will be faulty. A demo is meant to DEMOnstrate how it’s done. It never says anywhere it’s a prototype and if it was so, they wouldn’t brag about top notch security on their web page.

    But anyways, you probably won’t change your mind.