home.social

#deviceneutrality — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #deviceneutrality, aggregated by home.social.

  1. #DeviceNeutrality must be central to this effort. Users must have full control over their devices: the freedom to install and uninstall software and operating systems, free from gatekeeper interference.

    We regret the EC fails to recognise the need of changing the DMA in order to accommodate the pressing needs of the diverse stakeholders involved in the software industry in the EU.

  2. Do you know what #RouterFreedom is?

    It is the right of users to choose and operate their own routers, modems, and other equipment used for internet connection.

    It is important for user autonomy, competition, and privacy as it enables users to run #FreeSoftware operating systems on their routers and modems.

    fsfe.org/activities/routers/in

    #DeviceNeutrality

  3. Have you seen our new sticker? It’s the perfect one to give to those people (we’re sure at least one name comes to mind) who own an Apple device.

    And yes, it glows in the dark 🤩

    At FSFE :fsfe: booth at #39c3

    #softwarefreedom #deviceneutrality

  4. Your whole internet traffic, encryption, backups, communication, shopping, writings, business interaction, and so on are transferred through your router. If your router is not free, your digital freedom is likely to be compromised.

    💥 Check out our #RouterFreedom tech wiki, which collects information on how to use a different modem or router from your internet provider.

    docs.fsfe.org/en/teams/router-

    #DeviceNeutrality #SoftwareFreedom

  5. #Apple again weaponises its dominant market position and influence over millions of users to undermine a democratically enacted law in Europe:

    Rumour has it that the #gatekeeper might rather disable its WiFi sync functionality than make it interoperable with competitors, as it's obliged to under the EU #DigitalMarketsAct.

    Let me guess: next thing they'll complain again how the #DMA makes Apple products worse.

    numerama.com/tech/2110247-lapp

    #interoperability #DigitalRights #DeviceNeutrality

  6. Debatt i Aktuell Hållbarhet: Så kan du undvika att kasta din dator ♻️

    Många datorer kan inte uppgraderas till Windows 11. Resultatet blir att 400 miljoner fungerande datorer riskerar att kasseras – något som skapar mer än 700 miljoner kg elektronikavfall och stora koldioxidutsläpp. Det skriver @mattiasaxell vid @okfse i #AktuellHållbarhet och ger alternativ 🙌

    👇 Läs debattartikeln här:

    aktuellhallbarhet.se/opinion/d

    #cirkulärekonomi #circulareconomy #deviceneutrality #eWaste #RepairEU #R2R

  7. Debatt i Aktuell Hållbarhet: Så kan du undvika att kasta din dator ♻️

    Många datorer kan inte uppgraderas till Windows 11. Resultatet blir att 400 miljoner fungerande datorer riskerar att kasseras – något som skapar mer än 700 miljoner kg elektronikavfall och stora koldioxidutsläpp. Det skriver @mattiasaxell vid @okfse i #AktuellHållbarhet och ger alternativ 🙌

    👇 Läs debattartikeln här:

    aktuellhallbarhet.se/opinion/d

    #cirkulärekonomi #circulareconomy #deviceneutrality #eWaste #RepairEU #R2R

  8. Debatt i Aktuell Hållbarhet: Så kan du undvika att kasta din dator ♻️

    Många datorer kan inte uppgraderas till Windows 11. Resultatet blir att 400 miljoner fungerande datorer riskerar att kasseras – något som skapar mer än 700 miljoner kg elektronikavfall och stora koldioxidutsläpp. Det skriver @mattiasaxell vid @okfse i #AktuellHållbarhet och ger alternativ 🙌

    👇 Läs debattartikeln här:

    aktuellhallbarhet.se/opinion/d

    #cirkulärekonomi #circulareconomy #deviceneutrality #eWaste #RepairEU #R2R

  9. Debatt i Aktuell Hållbarhet: Så kan du undvika att kasta din dator ♻️

    Många datorer kan inte uppgraderas till Windows 11. Resultatet blir att 400 miljoner fungerande datorer riskerar att kasseras – något som skapar mer än 700 miljoner kg elektronikavfall och stora koldioxidutsläpp. Det skriver @mattiasaxell vid @okfse i #AktuellHållbarhet och ger alternativ 🙌

    👇 Läs debattartikeln här:

    aktuellhallbarhet.se/opinion/d

    #cirkulärekonomi #circulareconomy #deviceneutrality #eWaste #RepairEU #R2R

  10. Debatt i Aktuell Hållbarhet: Så kan du undvika att kasta din dator ♻️

    Många datorer kan inte uppgraderas till Windows 11. Resultatet blir att 400 miljoner fungerande datorer riskerar att kasseras – något som skapar mer än 700 miljoner kg elektronikavfall och stora koldioxidutsläpp. Det skriver @mattiasaxell vid @okfse i #AktuellHållbarhet och ger alternativ 🙌

    👇 Läs debattartikeln här:

    aktuellhallbarhet.se/opinion/d

    #cirkulärekonomi #circulareconomy #deviceneutrality #eWaste #RepairEU #R2R

  11. 👀 Have you already checked our input to the @EUCommission ’s public consultation about the #DMA?

    🔧 After 12 months of the DMA, we stress the hurdles and challenges for making #DeviceNeutrality a reality:

    fsfe.org/news/2025/news-202509

  12. 📣 Hey, #Google "disable" Google apps is not "uninstalling" them. You can't dodge the EU’s #DMA rules by redefining language.

    👏 Thanks to @fsfe and allies, a complaint has been filed to stop this abuse and protect user freedom.

    💪 Support the FSFE's fight for digital rights: my.fsfe.org/donate

    #DeviceNeutrality #BigTech

  13. Looking forward to meet many from the @nextcloud community on Sunday at the #NextcloudConf25! Will give a lightning talk about "Let’s spark children’s interest in coding" and be around to talk about #softwarefreedom and the @fsfe's work as well.

    On Saturday my awesome co-workers @llas and @dario will be there as well to talk with #nextcloud contributors about #DeviceNeutrality and get feedback for our work in front of the European Court of Justice to keep #Apple accountable under the #DMA.

  14. 🎉 The Digital Markets Act #DMA turns 1! Since its approval #Google, #Apple & all gatekeepers must:

    🔹Allow competing app stores
    🔸Not discriminate against browsers & search engines
    🔹Allow uninstallation of pre-installed apps
    🔸Provide free-of-charge interoperability

    👀 But we’re not done! #DeviceNeutrality, the freedom to uninstall, install & control any software on any device still faces hurdles

    💪 With @edri we submitted our contribution to the @EUCommission consultation

    fsfe.org/news/2025/news-202509

  15. 📣 Is "disable" the same as "uninstall"? We do not believe it. Google does.

    Under the DMA, the FSFE with a coalition of civil-society organisations prompts the @EUCommission to open proceedings to investigate Alphabet's (#Google) regarding the uninstallation of pre-installed apps in Android.

    Uninstalling is completely removing the app, not just disabling it! This is key for #DeviceNeutrality!

    📎 edri.org/wp-content/uploads/20

    #SoftwareFreedom #DMA

  16. 🤖⚖️ Locked bootloaders, forced app stores, and vendor lock-in? No thanks!

    #DeviceNeutrality helps to break up digital monopolies and restore competition by giving back to end-users control of their devices! #FreeSoftware

    deviceneutrality.org/

  17. Please help us to reach #ios developers. We need their feedback to our survey fsfe.org/news/2025/news-202506 in order to keep #Apple accountable under the #DMA in a developer friendly way. #DeviceNeutrality

  18. 📢 📣 Tell us how gatekeepers are handling your interoperability requests! #FreeSoftware developers: your voice is needed!

    :fsfe: We launched the Digital Markets Act Interoperability Survey to gather first-hand experiences from developers requesting software interoperability: survey.fsfe.org/index.php/6999 📝

    💡 More info: fsfe.org/news/2025/news-202506

    #SoftwareFreedom #DeviceNeutrality #DMA

  19. Today at #Devconf :
    * Starting from 8:30 I will be at the @fsfe booth again.
    * 11:00 "Enforcing #DeviceNeutrality in the EU: our litigation efforts against #Apple to protect Free Software" by my great co-worker @llas pretalx.devconf.info/devconf-c
    * 14:35 " Identity: Supporting dementia care with #FreeSoftware" by last year's #YouthHacking4Freedom winner @sofiaritz pretalx.devconf.info/devconf-c
    * 17:30 ->.... social event organised by @devconf_cz 🤗

  20. :fsfe: May Newsletter!!🗞️

    In April, our work on #DeviceNeutrality continued with news and meetings on DMA; we had a #PMPC meeting in Germany and talked about the German coalition agreement in one of our Podcast episodes; we also held our annual Legal & Licensing Workshop; and we published another article in our Legal Corner:

    fsfe.org/news/nl/nl-202505.en.

    #softwarefreedom #FreeSoftware #publiccode

  21. :fsfe: May Newsletter!!🗞️

    In April, our work on #DeviceNeutrality continued with news and meetings on DMA; we had a #PMPC meeting in Germany and talked about the German coalition agreement in one of our Podcast episodes; we also held our annual Legal & Licensing Workshop; and we published another article in our Legal Corner:

    fsfe.org/news/nl/nl-202505.en.

    #softwarefreedom #FreeSoftware #publiccode

  22. :fsfe: May Newsletter!!🗞️

    In April, our work on #DeviceNeutrality continued with news and meetings on DMA; we had a #PMPC meeting in Germany and talked about the German coalition agreement in one of our Podcast episodes; we also held our annual Legal & Licensing Workshop; and we published another article in our Legal Corner:

    fsfe.org/news/nl/nl-202505.en.

    #softwarefreedom #FreeSoftware #publiccode

  23. :fsfe: May Newsletter!!🗞️

    In April, our work on #DeviceNeutrality continued with news and meetings on DMA; we had a #PMPC meeting in Germany and talked about the German coalition agreement in one of our Podcast episodes; we also held our annual Legal & Licensing Workshop; and we published another article in our Legal Corner:

    fsfe.org/news/nl/nl-202505.en.

    #softwarefreedom #FreeSoftware #publiccode

  24. :fsfe: May Newsletter!!🗞️

    In April, our work on #DeviceNeutrality continued with news and meetings on DMA; we had a #PMPC meeting in Germany and talked about the German coalition agreement in one of our Podcast episodes; we also held our annual Legal & Licensing Workshop; and we published another article in our Legal Corner:

    fsfe.org/news/nl/nl-202505.en.

    #softwarefreedom #FreeSoftware #publiccode

  25. Open the conversation about:
    Since both are valid, and maintained in the W3C rec, we must assume neither is recommended over the other in every use case instance scenario sitch'

    #CSS #WebDesign #WebDevelopment #crossplatform #deviceneutrality

    So... that said...
    Which method is "better"?
    They both seem to serve the same functional purpose, in the end.
    my intended use is primarly and likely only to appear in a .css doc via <link rel="stylesheet">

    **For the sake of conversation:**
    Why do we have the ability to be more granular about the identity of the source?
    See above "@ import" vs "@ font-face"

    Also, for the sake of ... the same conversation, really:
    [I personally am confident that #WebDeveloper extension exists only after extensive, and continued research]. I feel I could resolve that-- even If i don't know the technical logic leading to one or ther other-- @chrispederick 's extension, having shown the @-import rendered URL in this-- my most likely to be used enviroment-- it is safe for me to say, i can always trust that at-import is satisfactory, while the more granular aproach of @-font-face seems perhaps overkill for this purpose?

    #fontface #import #stylesheet #overkill

  26. Open the conversation about:
    Since both are valid, and maintained in the W3C rec, we must assume neither is recommended over the other in every use case instance scenario sitch'

    #CSS #WebDesign #WebDevelopment #crossplatform #deviceneutrality

    So... that said...
    Which method is "better"?
    They both seem to serve the same functional purpose, in the end.
    my intended use is primarly and likely only to appear in a .css doc via <link rel="stylesheet">

    **For the sake of conversation:**
    Why do we have the ability to be more granular about the identity of the source?
    See above "@ import" vs "@ font-face"

    Also, for the sake of ... the same conversation, really:
    [I personally am confident that #WebDeveloper extension exists only after extensive, and continued research]. I feel I could resolve that-- even If i don't know the technical logic leading to one or ther other-- @chrispederick 's extension, having shown the @-import rendered URL in this-- my most likely to be used enviroment-- it is safe for me to say, i can always trust that at-import is satisfactory, while the more granular aproach of @-font-face seems perhaps overkill for this purpose?

    #fontface #import #stylesheet #overkill

  27. Open the conversation about:
    Since both are valid, and maintained in the W3C rec, we must assume neither is recommended over the other in every use case instance scenario sitch'

    #CSS #WebDesign #WebDevelopment #crossplatform #deviceneutrality

    So... that said...
    Which method is "better"?
    They both seem to serve the same functional purpose, in the end.
    my intended use is primarly and likely only to appear in a .css doc via <link rel="stylesheet">

    **For the sake of conversation:**
    Why do we have the ability to be more granular about the identity of the source?
    See above "@ import" vs "@ font-face"

    Also, for the sake of ... the same conversation, really:
    [I personally am confident that #WebDeveloper extension exists only after extensive, and continued research]. I feel I could resolve that-- even If i don't know the technical logic leading to one or ther other-- @chrispederick 's extension, having shown the @-import rendered URL in this-- my most likely to be used enviroment-- it is safe for me to say, i can always trust that at-import is satisfactory, while the more granular aproach of @-font-face seems perhaps overkill for this purpose?

    #fontface #import #stylesheet #overkill

  28. Open the conversation about:
    Since both are valid, and maintained in the W3C rec, we must assume neither is recommended over the other in every use case instance scenario sitch'

    #CSS #WebDesign #WebDevelopment #crossplatform #deviceneutrality

    So... that said...
    Which method is "better"?
    They both seem to serve the same functional purpose, in the end.
    my intended use is primarly and likely only to appear in a .css doc via <link rel="stylesheet">

    **For the sake of conversation:**
    Why do we have the ability to be more granular about the identity of the source?
    See above "@ import" vs "@ font-face"

    Also, for the sake of ... the same conversation, really:
    [I personally am confident that #WebDeveloper extension exists only after extensive, and continued research]. I feel I could resolve that-- even If i don't know the technical logic leading to one or ther other-- @chrispederick 's extension, having shown the @-import rendered URL in this-- my most likely to be used enviroment-- it is safe for me to say, i can always trust that at-import is satisfactory, while the more granular aproach of @-font-face seems perhaps overkill for this purpose?

    #fontface #import #stylesheet #overkill

  29. Open the conversation about:
    Since both are valid, and maintained in the W3C rec, we must assume neither is recommended over the other in every use case instance scenario sitch'

    #CSS #WebDesign #WebDevelopment #crossplatform #deviceneutrality

    So... that said...
    Which method is "better"?
    They both seem to serve the same functional purpose, in the end.
    my intended use is primarly and likely only to appear in a .css doc via <link rel="stylesheet">

    **For the sake of conversation:**
    Why do we have the ability to be more granular about the identity of the source?
    See above "@ import" vs "@ font-face"

    Also, for the sake of ... the same conversation, really:
    [I personally am confident that #WebDeveloper extension exists only after extensive, and continued research]. I feel I could resolve that-- even If i don't know the technical logic leading to one or ther other-- @chrispederick 's extension, having shown the @-import rendered URL in this-- my most likely to be used enviroment-- it is safe for me to say, i can always trust that at-import is satisfactory, while the more granular aproach of @-font-face seems perhaps overkill for this purpose?

    #fontface #import #stylesheet #overkill

  30. The UK Competition and Markets Authority (#CMA) has launched today a new investigation into #Apple and #Google under the Digital Markets Competition Code (#DMCC) to determine their strategic market status in mobile ecosystems, including operating systems, app stores, and mobile browsers.

    We welcome this as a step towards fairer markets where #DeviceNeutrality is the standard, and #FreeSoftware its enabler.

    gov.uk/government/news/cma-to-

  31. The UK Competition and Markets Authority (#CMA) has launched today a new investigation into #Apple and #Google under the Digital Markets Competition Code (#DMCC) to determine their strategic market status in mobile ecosystems, including operating systems, app stores, and mobile browsers.

    We welcome this as a step towards fairer markets where #DeviceNeutrality is the standard, and #FreeSoftware its enabler.

    gov.uk/government/news/cma-to-

  32. The UK Competition and Markets Authority (#CMA) has launched today a new investigation into #Apple and #Google under the Digital Markets Competition Code (#DMCC) to determine their strategic market status in mobile ecosystems, including operating systems, app stores, and mobile browsers.

    We welcome this as a step towards fairer markets where #DeviceNeutrality is the standard, and #FreeSoftware its enabler.

    gov.uk/government/news/cma-to-

  33. The UK Competition and Markets Authority (#CMA) has launched today a new investigation into #Apple and #Google under the Digital Markets Competition Code (#DMCC) to determine their strategic market status in mobile ecosystems, including operating systems, app stores, and mobile browsers.

    We welcome this as a step towards fairer markets where #DeviceNeutrality is the standard, and #FreeSoftware its enabler.

    gov.uk/government/news/cma-to-

  34. The UK Competition and Markets Authority (#CMA) has launched today a new investigation into #Apple and #Google under the Digital Markets Competition Code (#DMCC) to determine their strategic market status in mobile ecosystems, including operating systems, app stores, and mobile browsers.

    We welcome this as a step towards fairer markets where #DeviceNeutrality is the standard, and #FreeSoftware its enabler.

    gov.uk/government/news/cma-to-

  35. 🚀 Exciting vision for software freedom by 2048! The FSFE outlines goals for device neutrality, public funding for Free Software, and empowering the next generation of tech innovators. Let’s work together for a future where everyone can control their technology! 🌍💻

    Read more: FSFE Vision for 2048 fsfe.org/news/2025/news-202501

    P.S.: @kirschner Living until 4096? With the way technology is advancing, I’m just waiting for my next upgrade! Who needs a time machine when you are a cyborg? 😄

    #SoftwareFreedom #FreeSoftware #FSFE #PublicMoneyPublicCode #YouthHacking4Freedom #SoftwareFreedom #FreeSoftware #FSFE #PublicMoneyPublicCode #YouthHacking4Freedom #DeviceNeutrality #OpenSource #TechForGood #FutureOfTech #Empowerment #Innovation #Community

  36. @llas FSFE Legal Programme Manager is giving today a talk in #DORSCLUC2024 on "When our routers are not free: the challenges for an Open and Neutral Internet"
    ⏰ 11:00 am
    📺 youtube.com/live/N5hKv3G8QaY?f

    #ngi #routerfreedom #deviceneutrality

  37. 💥 The :fsfe: #FSFE’s April newsletter is out!

    💡 Last month, the DMA came into force and we launched a website about #DeviceNeutrality, the #EU parliament voted the #CRA and the #PLD, and we released a guide to get active for the upcoming 🇪🇺 #EUelections. 🚀

    #SoftwareFreedom #FreeSoftware

    🤩 Check it out! ⤵️

    fsfe.org/news/nl/nl-202404.htm