• 0 Posts
  • 144 Comments
Joined 2 years ago
cake
Cake day: June 12th, 2023

help-circle
  • They do for the freedom of expression, as do most EU countries:

    Everyone has the right to freedom of expression. This right shall include freedom to hold opinions and to receive and impart information and ideas without interference by public authority and regardless of frontiers. This Article shall not prevent States from requiring the licensing of broadcasting, television or cinema enterprises.

    The exercise of these freedoms, since it carries with it duties and responsibilities, may be subject to such formalities, conditions, restrictions or penalties as are prescribed by law and are necessary in a democratic society, in the interests of national security, territorial integrity or public safety, for the prevention of disorder or crime, for the protection of health or morals, for the protection of the reputation or rights of others, for preventing the disclosure of information received in confidence, or for maintaining the authority and impartiality of the judiciary.



  • Why does it have that braindead URL?

    euvd.enisa.europa.eu -> European Union Vulnerability Database, run by the European Union Agency for Cybersecurity (from the previous name, European Network and Information Security Agency ENISA), hosted on the official website of the european union, europa.eu.

    And why, for the love of god, does it have a separate numbering scheme?!

    Because they want the ability to reference other vulnerability sources - like JVN - and not just CVE:

    The EUVD service builds upon the CVE system and vulnerabilities in the scope of the CVE numbering service receive a CVE. In addition, the EUVD data aggregates and enriches the vulnerability information and lists an EUVD ID on top of the CVE when new vulnerability entries are created. To allow further cross referencing, the CVE identifier and additional vulnerability identifiers are listed when available. -https://euvd.enisa.europa.eu/faq

    And because, you know, standards.






  • In a few years most of the world probably won’t even be able to. It took Chinese cars decades to come to the worldwide and especially the EU market because nobody in China was developing and manufacturing cars that would pass western safety regulations.

    If the only way for Tesla to stay competitive in the US is by loosening the US regulations, they’ll end up with an ecosystem that can only be sold and used in the US. For example, how the Cybertruck is entirely unroadworthy in the EU.

    I’m just waiting for the day EU declares that self-driving systems need to be able to detect a wall, even if there is a picture of an open road on it, and stop. It would mean Tesla wouldn’t be able to pass it due to Musk insisting on only using cameras and removing all other sensors.









  • The Pebble app was removed from the App store, so you have to manually sideload it every 7 days.

    And:

    Here are the things that are harder or impossible for 3rd party smartwatches (ie non Apple Watches) to do on iPhone:

    • There’s no way for a smartwatch to send text messages or iMessages.
    • You can’t reply to notifications or take ‘actions’ like marking something as done.
    • It’s very difficult to enable other iOS apps to work with Pebble. Basically iOS does not have the concept of ‘interprocess communication’(IPC) like on Android. What we did before was publish an SDK that other apps (like Strava) could integrate to make their own BLE connection to Pebble. It was a clunky quasi-solution that other apps didn’t like, because it was hard to test (among other things)
    • If you (accidentally) close our iOS app, then your watch can’t talk to app or internet
    • Impossible for watch to detect if you are using your phone, so your watch will buzz and display a notification even if you are staring at your iPhone
    • You can’t easily side load apps onto an iPhone. That means we have to publish the app on the iPhone appstore. This is a gigantic pain because Apple. Every update comes with the risk that a random app reviewer could make up some BS excuse and block the update.
    • Because of iOS Appstore rules, it would be hard for us to enable 3rd party watchface/app developers to charge for their work (ie we can’t easily make an appstore within our app)
    • Getting a Javascript engine to run in PebbleOS forced us to go through many hoops due to iOS — creating a compiler inside the Pebble iPhone app that in itself needed to be written in (cross-compiled to) JS to work with Apple’s restriction on downloadable code can only be JS
    • As a Pebble watch/app developer, using the iOS app as relay to the watch sucks since the “developer mode” terminates every few minutes
      https://ericmigi.com/blog/apple-restricts-pebble-from-being-awesome-with-iphones