Search
388 results for “keepandroidopen”
-
📰 «Mantengan Android abierto!»
🔗 https://proxy.jesusysustics.com/2026/04/30244/
Google no prohíbe instalar apps fuera de Play Store, pero hará que te rindas intentándolo https://www.larazon.es/tecnologia-consumo/google/google-no-prohibe-instalar-apps-fuera-de-play-store-pero-hara-que-te-rindas-intentandolo_2026032069bd051c3156ba241d5d96e6.htmlLo reconozco, me he quedado con este artículo solamente por su titular. Me parece perfecto, al grano y bien clarito: no es que Google vaya a impedir instalar apps desde fuera de su ecosistema sino que va a complicar y ralentizar tanto el proceso que nos va a quitar las ganas de usar esas alternativas.
F-Droid es el mejor repositorio alternativo a la tienda oficial de Google. Está llena de aplicaciones de código abierto y estas nuevas restricciones que plantean para Android les hará la vida imposible. Hace un mes y medio ya publicaron una carta abierta en contra de esta medida y luego se sumaron también desde Keep Android Open.
Quiero ahondar en esta última plataforma, pues Keep Android Open es la opción ideal para mantenerse informado sobre la posible evolución de este tema.
Keep Android Open https://keepandroidopen.org/es/ #️⃣ #Android #códigoAbierto #Google #novedad #plataforma #privacidad -
📰 «Mantengan Android abierto!»
🔗 https://proxy.jesusysustics.com/2026/04/30244/
Google no prohíbe instalar apps fuera de Play Store, pero hará que te rindas intentándolo https://www.larazon.es/tecnologia-consumo/google/google-no-prohibe-instalar-apps-fuera-de-play-store-pero-hara-que-te-rindas-intentandolo_2026032069bd051c3156ba241d5d96e6.htmlLo reconozco, me he quedado con este artículo solamente por su titular. Me parece perfecto, al grano y bien clarito: no es que Google vaya a impedir instalar apps desde fuera de su ecosistema sino que va a complicar y ralentizar tanto el proceso que nos va a quitar las ganas de usar esas alternativas.
F-Droid es el mejor repositorio alternativo a la tienda oficial de Google. Está llena de aplicaciones de código abierto y estas nuevas restricciones que plantean para Android les hará la vida imposible. Hace un mes y medio ya publicaron una carta abierta en contra de esta medida y luego se sumaron también desde Keep Android Open.
Quiero ahondar en esta última plataforma, pues Keep Android Open es la opción ideal para mantenerse informado sobre la posible evolución de este tema.
Keep Android Open https://keepandroidopen.org/es/ #️⃣ #Android #códigoAbierto #Google #novedad #plataforma #privacidad -
Moinsen.
Heute ist mal wieder ein "digitaler Unabhängigkeitstag".
Und ich habe es geschafft, die im Beitrag von @[email protected] erwähnte Dokumentation bei ARTE vollständig zu sehen - übrigens via Zapp, einer freien App, die im F-Droid-Repository zu finden ist.
Gefährliche Apps - Im Netz der Datenhändler
https://www.arte.tv/de/videos/123951-000-A/gefaehrliche-apps-im-netz-der-datenhaendler/
52 Min. | Verfügbar bis zum 14.07.2026Für mich nicht wirklich Neues und leider wird auch nicht wirklich auf Gegenmaßnahmen eingegangen (im Gegenteil, es wird einmal erwähnt, man hätte keine Wahl - was schlicht falsch ist). Dennoch sollte diese Doku über abfließende Daten, den Handel damit und die sich damit ergebenden gefährlichen Möglichkeiten eigentlich von der gesamten Bevölkerung verinnerlicht werden.
Vermeidet unfreie Apps, prüft Apps auf deren Verhalten vor der Installation, dichtet Eure Geräte ab, setzt Schutzmaßnahmen ein (filtert Traffic), verzichtet auf Registrierungen, wenn nicht notwendig (insbesondere bei bekannten Datenkraken), macht Euch schlau!
Und bedenkt, daß es normalerweise nichts kostenlos gibt... möglicherweise seid Ihr nämlich das Produkt. Und ja, wer dies liest, ist vermutlich im Fediverse unterwegs und daher wahrscheinlich schon im Bilde... ;-)
Und übrigens, Android sollte offen gehalten werden!
https://keepandroidopen.org/de/CC
@[email protected]
@[email protected]#Dokumentation #ARTE #Datenhandel #DID #DUT #Android #iOS #Fediverse
-
Moinsen.
Heute ist mal wieder ein "digitaler Unabhängigkeitstag".
Und ich habe es geschafft, die im Beitrag von @[email protected] erwähnte Dokumentation bei ARTE vollständig zu sehen - übrigens via Zapp, einer freien App, die im F-Droid-Repository zu finden ist.
Gefährliche Apps - Im Netz der Datenhändler
https://www.arte.tv/de/videos/123951-000-A/gefaehrliche-apps-im-netz-der-datenhaendler/
52 Min. | Verfügbar bis zum 14.07.2026Für mich nicht wirklich Neues und leider wird auch nicht wirklich auf Gegenmaßnahmen eingegangen (im Gegenteil, es wird einmal erwähnt, man hätte keine Wahl - was schlicht falsch ist). Dennoch sollte diese Doku über abfließende Daten, den Handel damit und die sich damit ergebenden gefährlichen Möglichkeiten eigentlich von der gesamten Bevölkerung verinnerlicht werden.
Vermeidet unfreie Apps, prüft Apps auf deren Verhalten vor der Installation, dichtet Eure Geräte ab, setzt Schutzmaßnahmen ein (filtert Traffic), verzichtet auf Registrierungen, wenn nicht notwendig (insbesondere bei bekannten Datenkraken), macht Euch schlau!
Und bedenkt, daß es normalerweise nichts kostenlos gibt... möglicherweise seid Ihr nämlich das Produkt. Und ja, wer dies liest, ist vermutlich im Fediverse unterwegs und daher wahrscheinlich schon im Bilde... ;-)
Und übrigens, Android sollte offen gehalten werden!
https://keepandroidopen.org/de/CC
@[email protected]
@[email protected]#Dokumentation #ARTE #Datenhandel #DID #DUT #Android #iOS #Fediverse
-
حافظوا على انفتاح أندرويد
اقرأ رسالتنا المفتوحة التي تعارض برنامج التحقق من مطوري أندرويد
في أغسطس 2025، أعلنت جوجل أنه اعتبارًا من سبتمبر 2026، لن يكون من الممكن تطوير تطبيقات لمنصة أندرويد دون التسجيل أولاً بشكل مركزي لدى جوجل. سيتضمن هذا التسجيل:
- دفع رسوم لجوجل
- الموافقة على الشروط والأحكام الخاصة بجوجل
- تقديم إثبات هوية حكومية
- رفع دليل على مفتاح التوقيع الخاص بالمطور
- إدراج جميع معرفات التطبيقات الحالية والمستقبلية
ماذا يعني هذا بالنسبة لحقوقك
➤ أنت، المستهلك، اشتريت جهاز أندرويد الخاص بك وأنت تؤمن بوعد جوجل بأنه منصة حوسبة مفتوحة وأن بإمكانك تشغيل أي برنامج تختاره عليه. وبدلاً من ذلك، واعتبارًا من سبتمبر 2026، سيقومون بدفع تحديث إلى نظام التشغيل الخاص بك دون موافقتك والذي سيحجب هذا الحق بشكل لا رجعة فيه ويجعلك تحت رحمة حكمهم بشأن البرامج التي يُسمح لك بالوثوق بها.
➤ أنت، المبدع، لم يعد بإمكانك تطوير تطبيق ومشاركته مباشرة مع أصدقائك وعائلتك ومجتمعك دون الحصول أولاً على موافقة جوجل. إن وعد أندرويد — والميزة التسويقية التي استخدمها لتمييز نفسه عن الآيفون — كان دائمًا أنه "مفتوح". لكن من الواضح أن جوجل تشعر الآن أن لديها سيطرة كافية على نظام أندرويد، إلى جانب نفوذ تنظيمي كافٍ، بحيث يمكنها الآن التخلي عن هذا المبدأ بكل تحيز......
#android #open #أندرويد #نظام #هاتف #gnutux https://keepandroidopen.org/
-
Last night was my first ever aboard a sleeper train! I took the European Sleeper (ES 452) from Berlin Gesundbrunnen to Bruxelles-Midi in Comfort Standard class.
With disruption on the north-south lines of the Berlin S-Bahn and construction work on sections of the U-Bahn, getting from U-Bahnhof Mehringdamm to Gesundbrunnen was unsettling but thankfully uneventful. After extracting my essential nighttime items - pyjamas and blåhaj - from my suitcase on the platform, I boarded the European Sleeper train, which departed punctually at 22:59.
Upon boarding, I quickly noticed that the air in the train was much warmer and drier than I had expected, and the 500 ml bottle of water provided for each passenger would have been entirely inadequate. Luckily, there was an extra bottle of water, and after a brief discussion with the one other passenger in the compartment, I drank that too. Only in the morning did I notice that there was a climate control panel for the compartment, which was set to 'medium'.
The mattresses were comfortable (as were the pillows) although the bunk was ever so slightly too short for me to lie down straight on. There was also loads of luggage space, both below the seats and on a narrow shelf at the head of the bunks, but I think it would have been much less spacious in the couchette carriages, which fit six passengers into each compartment - there, I would expect space for no more than a rucksack per passenger.
There was another Träwelling user on board, but we didn't get to meet each other! Judging by the tags on our respective check-ins, we were in different carriages.
I got to sleep at approximately midnight, which is pretty typical for me. However, I woke up at 03:00 after a dream in which I had a productive discussion with @marcprux about KeepAndroidOpen.org shortly before the train derailed and plunged off the side of a bridge (metaphor?) - considering the subject matter, this dream did not bother me as much as it perhaps should have. In fairness, I think the dream might have had more to do with some very intense lighting around Rheine than with anything about the ride quality of the train.
At this point the train had stopped at Bad Bentheim, where we stayed for close to an hour. I don't know what the wait was for, but we had a driver change during this time. I also took the opportunity to use the WC (one per carriage, seemingly) while the train was stationary, and I found it to be well-designed, clean and fully functional. I went back to bed at about 04:00 when we started moving again.
I slept pretty soundly until 07:30, when the announcements for the stop in Rotterdam woke me momentarily, and then I fell back to sleep again, finally being woken up for good at 09:20 by my fellow passenger, who alerted me to the fact that we were already at Brussels! We crawled along at a snails pace through the underground North-South connection and arrived in Bruxelles-Midi exactly on time at 09:27.
In total, out of the 10 hours and 28 minutes of travel time, I got about 8 hours of sleep - not bad at all!
The train didn't wait long at Brussels - by 09:40 a member of staff on the train chivvied me politely to leave, the train pulled away at 09:56, and another train had already arrived at the same platform by 10:00.
My suggestions to others taking the European Sleeper: bring long cables to charge whatever devices you have (the compartment I was in only had two electricity sockets, which were situated below the window), bring something to cover your eyes (the curtains did not block much light, and there is lots of artificial lighting on that route), and something to block out the creaking and clanking of the train - my fellow passenger used noise-cancelling headphones.
All in all, it was a fantastic experience, and one which I hope to repeat soon. Not only did it fulfil a key part of my itinerary, but it was also relatively good value: the bunk reservation being priced at €89 with an Interrail pass, it was approximately the same cost as a hotel room in Brussels, which I would have had to book if I'd taken day trains instead.
https://traewelling.de/status/7336542
#CrossBorderRail #traewelling #EuropeanSleeper #NightTrains #NightTrain #SleeperTrains #SleeperTrain
-
Last night was my first ever aboard a sleeper train! I took the European Sleeper (ES 452) from Berlin Gesundbrunnen to Bruxelles-Midi in Comfort Standard class.
With disruption on the north-south lines of the Berlin S-Bahn and construction work on sections of the U-Bahn, getting from U-Bahnhof Mehringdamm to Gesundbrunnen was unsettling but thankfully uneventful. After extracting my essential nighttime items - pyjamas and blåhaj - from my suitcase on the platform, I boarded the European Sleeper train, which departed punctually at 22:59.
Upon boarding, I quickly noticed that the air in the train was much warmer and drier than I had expected, and the 500 ml bottle of water provided for each passenger would have been entirely inadequate. Luckily, there was an extra bottle of water, and after a brief discussion with the one other passenger in the compartment, I drank that too. Only in the morning did I notice that there was a climate control panel for the compartment, which was set to 'medium'.
The mattresses were comfortable (as were the pillows) although the bunk was ever so slightly too short for me to lie down straight on. There was also loads of luggage space, both below the seats and on a narrow shelf at the head of the bunks, but I think it would have been much less spacious in the couchette carriages, which fit six passengers into each compartment - there, I would expect space for no more than a rucksack per passenger.
There was another Träwelling user on board, but we didn't get to meet each other! Judging by the tags on our respective check-ins, we were in different carriages.
I got to sleep at approximately midnight, which is pretty typical for me. However, I woke up at 03:00 after a dream in which I had a productive discussion with @marcprux about KeepAndroidOpen.org shortly before the train derailed and plunged off the side of a bridge (metaphor?) - considering the subject matter, this dream did not bother me as much as it perhaps should have. In fairness, I think the dream might have had more to do with some very intense lighting around Rheine than with anything about the ride quality of the train.
At this point the train had stopped at Bad Bentheim, where we stayed for close to an hour. I don't know what the wait was for, but we had a driver change during this time. I also took the opportunity to use the WC (one per carriage, seemingly) while the train was stationary, and I found it to be well-designed, clean and fully functional. I went back to bed at about 04:00 when we started moving again.
I slept pretty soundly until 07:30, when the announcements for the stop in Rotterdam woke me momentarily, and then I fell back to sleep again, finally being woken up for good at 09:20 by my fellow passenger, who alerted me to the fact that we were already at Brussels! We crawled along at a snails pace through the underground North-South connection and arrived in Bruxelles-Midi exactly on time at 09:27.
In total, out of the 10 hours and 28 minutes of travel time, I got about 8 hours of sleep - not bad at all!
The train didn't wait long at Brussels - by 09:40 a member of staff on the train chivvied me politely to leave, the train pulled away at 09:56, and another train had already arrived at the same platform by 10:00.
My suggestions to others taking the European Sleeper: bring long cables to charge whatever devices you have (the compartment I was in only had two electricity sockets, which were situated below the window), bring something to cover your eyes (the curtains did not block much light, and there is lots of artificial lighting on that route), and something to block out the creaking and clanking of the train - my fellow passenger used noise-cancelling headphones.
All in all, it was a fantastic experience, and one which I hope to repeat soon. Not only did it fulfil a key part of my itinerary, but it was also relatively good value: the bunk reservation being priced at €89 with an Interrail pass, it was approximately the same cost as a hotel room in Brussels, which I would have had to book if I'd taken day trains instead.
https://traewelling.de/status/7336542
#CrossBorderRail #traewelling #EuropeanSleeper #NightTrains #NightTrain #SleeperTrains #SleeperTrain
-
Last night was my first ever aboard a sleeper train! I took the European Sleeper (ES 452) from Berlin Gesundbrunnen to Bruxelles-Midi in Comfort Standard class.
With disruption on the north-south lines of the Berlin S-Bahn and construction work on sections of the U-Bahn, getting from U-Bahnhof Mehringdamm to Gesundbrunnen was unsettling but thankfully uneventful. After extracting my essential nighttime items - pyjamas and blåhaj - from my suitcase on the platform, I boarded the European Sleeper train, which departed punctually at 22:59.
Upon boarding, I quickly noticed that the air in the train was much warmer and drier than I had expected, and the 500 ml bottle of water provided for each passenger would have been entirely inadequate. Luckily, there was an extra bottle of water, and after a brief discussion with the one other passenger in the compartment, I drank that too. Only in the morning did I notice that there was a climate control panel for the compartment, which was set to 'medium'.
The mattresses were comfortable (as were the pillows) although the bunk was ever so slightly too short for me to lie down straight on. There was also loads of luggage space, both below the seats and on a narrow shelf at the head of the bunks, but I think it would have been much less spacious in the couchette carriages, which fit six passengers into each compartment - there, I would expect space for no more than a rucksack per passenger.
There was another Träwelling user on board, but we didn't get to meet each other! Judging by the tags on our respective check-ins, we were in different carriages.
I got to sleep at approximately midnight, which is pretty typical for me. However, I woke up at 03:00 after a dream in which I had a productive discussion with @marcprux about KeepAndroidOpen.org shortly before the train derailed and plunged off the side of a bridge (metaphor?) - considering the subject matter, this dream did not bother me as much as it perhaps should have. In fairness, I think the dream might have had more to do with some very intense lighting around Rheine than with anything about the ride quality of the train.
At this point the train had stopped at Bad Bentheim, where we stayed for close to an hour. I don't know what the wait was for, but we had a driver change during this time. I also took the opportunity to use the WC (one per carriage, seemingly) while the train was stationary, and I found it to be well-designed, clean and fully functional. I went back to bed at about 04:00 when we started moving again.
I slept pretty soundly until 07:30, when the announcements for the stop in Rotterdam woke me momentarily, and then I fell back to sleep again, finally being woken up for good at 09:20 by my fellow passenger, who alerted me to the fact that we were already at Brussels! We crawled along at a snails pace through the underground North-South connection and arrived in Bruxelles-Midi exactly on time at 09:27.
In total, out of the 10 hours and 28 minutes of travel time, I got about 8 hours of sleep - not bad at all!
The train didn't wait long at Brussels - by 09:40 a member of staff on the train chivvied me politely to leave, the train pulled away at 09:56, and another train had already arrived at the same platform by 10:00.
My suggestions to others taking the European Sleeper: bring long cables to charge whatever devices you have (the compartment I was in only had two electricity sockets, which were situated below the window), bring something to cover your eyes (the curtains did not block much light, and there is lots of artificial lighting on that route), and something to block out the creaking and clanking of the train - my fellow passenger used noise-cancelling headphones.
All in all, it was a fantastic experience, and one which I hope to repeat soon. Not only did it fulfil a key part of my itinerary, but it was also relatively good value: the bunk reservation being priced at €89 with an Interrail pass, it was approximately the same cost as a hotel room in Brussels, which I would have had to book if I'd taken day trains instead.
https://traewelling.de/status/7336542
#CrossBorderRail #traewelling #EuropeanSleeper #NightTrains #NightTrain #SleeperTrains #SleeperTrain
-
Last night was my first ever aboard a sleeper train! I took the European Sleeper (ES 452) from Berlin Gesundbrunnen to Bruxelles-Midi in Comfort Standard class.
With disruption on the north-south lines of the Berlin S-Bahn and construction work on sections of the U-Bahn, getting from U-Bahnhof Mehringdamm to Gesundbrunnen was unsettling but thankfully uneventful. After extracting my essential nighttime items - pyjamas and blåhaj - from my suitcase on the platform, I boarded the European Sleeper train, which departed punctually at 22:59.
Upon boarding, I quickly noticed that the air in the train was much warmer and drier than I had expected, and the 500 ml bottle of water provided for each passenger would have been entirely inadequate. Luckily, there was an extra bottle of water, and after a brief discussion with the one other passenger in the compartment, I drank that too. Only in the morning did I notice that there was a climate control panel for the compartment, which was set to 'medium'.
The mattresses were comfortable (as were the pillows) although the bunk was ever so slightly too short for me to lie down straight on. There was also loads of luggage space, both below the seats and on a narrow shelf at the head of the bunks, but I think it would have been much less spacious in the couchette carriages, which fit six passengers into each compartment - there, I would expect space for no more than a rucksack per passenger.
There was another Träwelling user on board, but we didn't get to meet each other! Judging by the tags on our respective check-ins, we were in different carriages.
I got to sleep at approximately midnight, which is pretty typical for me. However, I woke up at 03:00 after a dream in which I had a productive discussion with @marcprux about KeepAndroidOpen.org shortly before the train derailed and plunged off the side of a bridge (metaphor?) - considering the subject matter, this dream did not bother me as much as it perhaps should have. In fairness, I think the dream might have had more to do with some very intense lighting around Rheine than with anything about the ride quality of the train.
At this point the train had stopped at Bad Bentheim, where we stayed for close to an hour. I don't know what the wait was for, but we had a driver change during this time. I also took the opportunity to use the WC (one per carriage, seemingly) while the train was stationary, and I found it to be well-designed, clean and fully functional. I went back to bed at about 04:00 when we started moving again.
I slept pretty soundly until 07:30, when the announcements for the stop in Rotterdam woke me momentarily, and then I fell back to sleep again, finally being woken up for good at 09:20 by my fellow passenger, who alerted me to the fact that we were already at Brussels! We crawled along at a snails pace through the underground North-South connection and arrived in Bruxelles-Midi exactly on time at 09:27.
In total, out of the 10 hours and 28 minutes of travel time, I got about 8 hours of sleep - not bad at all!
The train didn't wait long at Brussels - by 09:40 a member of staff on the train chivvied me politely to leave, the train pulled away at 09:56, and another train had already arrived at the same platform by 10:00.
My suggestions to others taking the European Sleeper: bring long cables to charge whatever devices you have (the compartment I was in only had two electricity sockets, which were situated below the window), bring something to cover your eyes (the curtains did not block much light, and there is lots of artificial lighting on that route), and something to block out the creaking and clanking of the train - my fellow passenger used noise-cancelling headphones.
All in all, it was a fantastic experience, and one which I hope to repeat soon. Not only did it fulfil a key part of my itinerary, but it was also relatively good value: the bunk reservation being priced at €89 with an Interrail pass, it was approximately the same cost as a hotel room in Brussels, which I would have had to book if I'd taken day trains instead.
https://traewelling.de/status/7336542
#CrossBorderRail #traewelling #EuropeanSleeper #NightTrains #NightTrain #SleeperTrains #SleeperTrain
-
Rencontres Francophones Sailfish·OS
La communauté francophone des utilisatrices et utilisateurs de Sailfish OS1 a choisi de se réunir à Lyon, ce samedi 21 mars.
Le lieu choisi n’est autre que l’AltNet, au 7 Place Louis Chazette 69001 Lyon. Les membres de l’ALDIL connaissent cette espace pour y avoir fait leur dernière AG et leur apéro de rentrée.
LALIS, dont le local est adjacent, a accompagné les préparatifs de ce rassemblement inédit.
Le système Sailfish OS pour smartphone, en quelques mots :
Sailfish OS est une distribution linux et les paquets sont au format RPM.
Sont propriétaires pour l’essentiel:
– « le bureau » appelé Silica (c’est le Plasma de cette distribution linux pour donner un exemple) lui même basé sur Qt.
– AAS, c’est à dire le Android App Support qui fonctionne dans un container afin de faire tourner un Android aosp, ce qui permet de combler les lacunes des applications natives,
– le clavier prédictif et vraisemblablement quelques autres bricoles dont je n’ai pas la liste avec précision 😉
À noter aussi l’histoire de l’entreprise Jolla qui est née sur les « cendres » de la branche smartphone de Nokia.
Concernant l’événement en lui-même, voici de quoi il retourne :
C’est une journée destinée aux utilisateurs de Sailfish OS avec notamment le but de répondre aux questions, montrer des solutions de contournement aux problèmes et bugs. Notamment la version 5.0.0.73 sera certainement déployée à tous les utilisateurs. Cette 5.0.0.73 arrive avec Android aosp 13 ce qui générera aussi des questions. Nous devrions avoir également la présence de certains développeurs d’applications tierces notamment en la personne de Ruben de Smet avec un moment de travail sur leurs applications (hackaton ?). Nous espérons également la venue d’Andrew Branson, salarié de Jolla, qui pourra alors nous présenter de manière concrète le nouveau J2.
https://mastodon.social/@rubdos
https://mastodon.social/@abranson
Bien entendu, cette journée pourra vraisemblablement intéresser les « linuxiens » lyonnais 😉 et tout le monde est bienvenu, dans la limite de la capacité de la salle. Nous pourrions même aider ceux et celles qui auraient en « stock » un sony xperia xa2, ou x10ii ou x10iii à flasher leur téléphone (install party !). Il y a d’autres smartphones compatibles pouvant accepter des versions communautaires de Sailfish OS.
Le système n’étant pas totalement libre, et les contours de l’événement aillant mis du temps à se préciser, la collégiale de l’ALDIL n’a pas souhaité y être associée. Mais ce serait quand même dommage ne pas en dire quelques mots. Voilà donc cet article, à la publication certes un peu tardive, mais autre ambition que d’informer notre réseau.
Vous voilà donc, chères lectrices, chers lecteurs, dans la confidence de ce modeste événement. Un rendez-vous qui pourrait bien se renouveler. Et avec les prochains changements de CGU d’Android2, toute alternative est bonne à connaitre.3
Crédit images :
- Small Group, tuxwrench
- Logo de SailFish OS
- Logo de LALIS
- https://sailfishos.org/ ↩︎
- https://keepandroidopen.org/fr/ ↩︎
- https://petitions.assemblee-nationale.fr/initiatives/i-5304?locale=fr ↩︎
-
Rencontres Francophones Sailfish OS
La communauté francophone des utilisatrices et utilisateurs de Sailfish OS1 a choisi de se réunir à Lyon, ce samedi 21 mars.
Le lieu choisi n’est autre que l’AltNet, au 7 Place Louis Chazette 69001 Lyon. Les membres de l’ALDIL connaissent cette espace pour y avoir fait leur dernière AG et leur apéro de rentrée.
LALIS, dont le local est adjacent, a accompagné les préparatifs de ce rassemblement inédit.
Le système Sailfish OS pour smartphone, en quelques mots :
Sailfish OS est une distribution linux et les paquets sont au format RPM.
Sont propriétaires pour l’essentiel:
– « le bureau » appelé Silica […] lui même basé sur Qt.
– AAS, c’est à dire le Android App Support qui fonctionne dans un container afin de faire tourner un Android aosp, ce qui permet de combler les lacunes des applications natives,
– le clavier prédictif et vraisemblablement quelques autres bricoles dont je n’ai pas la liste avec précision 😉
À noter aussi l’histoire de l’entreprise Jolla qui est née sur les « cendres » de la branche smartphone de Nokia.
Concernant l’événement en lui-même, voici de quoi il retourne :
C’est une journée destinée aux utilisateurs de Sailfish OS avec notamment le but de répondre aux questions, montrer des solutions de contournement aux problèmes et bugs. Notamment la version 5.0.0.73 sera certainement déployée à tous les utilisateurs. Cette 5.0.0.73 arrive avec Android aosp 13 ce qui générera aussi des questions. Nous devrions avoir également la présence de certains développeurs d’applications tierces notamment en la personne de Ruben de Smet avec un moment de travail sur leurs applications (hackaton ?). Nous espérons également la venue d’Andrew Branson, salarié de Jolla, qui pourra alors nous présenter de manière concrète le nouveau J2.
https://mastodon.social/@rubdos
https://mastodon.social/@abranson
Bien entendu, cette journée pourra vraisemblablement intéresser les « linuxiens » lyonnais 😉 et tout le monde est bienvenu, dans la limite de la capacité de la salle. Nous pourrions même aider ceux et celles qui auraient en « stock » un sony xperia xa2, ou x10ii ou x10iii à flasher leur téléphone (install party !). Il y a d’autres smartphones compatibles pouvant accepter des versions communautaires de Sailfish OS.
Le système n’étant pas totalement libre, et les contours de l’événement aillant mis du temps à se préciser, la collégiale de l’ALDIL n’a pas souhaité y être associée. Mais ce serait quand même dommage ne pas en dire quelques mots. Voilà donc cet article, à la publication certes un peu tardive, mais autre ambition que d’informer notre réseau.
Vous voilà donc, chères lectrices, chers lecteurs, dans la confidence de ce modeste événement. Un rendez-vous qui pourrait bien se renouveler. Et avec les prochains changements de CGU d’Android2, toute alternative est bonne à connaitre.3
Crédit images :
- Small Group, tuxwrench
- Logo de SailFish OS
- Logo de LALIS
- https://sailfishos.org/ ↩︎
- https://keepandroidopen.org/fr/ ↩︎
- https://petitions.assemblee-nationale.fr/initiatives/i-5304?locale=fr ↩︎
-
Rencontres Francophones Sailfish·OS
La communauté francophone des utilisatrices et utilisateurs de Sailfish OS1 a choisi de se réunir à Lyon, ce samedi 21 mars.
Le lieu choisi n’est autre que l’AltNet, au 7 Place Louis Chazette 69001 Lyon. Les membres de l’ALDIL connaissent cette espace pour y avoir fait leur dernière AG et leur apéro de rentrée.
LALIS, dont le local est adjacent, a accompagné les préparatifs de ce rassemblement inédit.
Le système Sailfish OS pour smartphone, en quelques mots :
Sailfish OS est une distribution linux et les paquets sont au format RPM.
Sont propriétaires pour l’essentiel:
– « le bureau » appelé Silica (c’est le Plasma de cette distribution linux pour donner un exemple) lui même basé sur Qt.
– AAS, c’est à dire le Android App Support qui fonctionne dans un container afin de faire tourner un Android aosp, ce qui permet de combler les lacunes des applications natives,
– le clavier prédictif et vraisemblablement quelques autres bricoles dont je n’ai pas la liste avec précision 😉
À noter aussi l’histoire de l’entreprise Jolla qui est née sur les « cendres » de la branche smartphone de Nokia.
Concernant l’événement en lui-même, voici de quoi il retourne :
C’est une journée destinée aux utilisateurs de Sailfish OS avec notamment le but de répondre aux questions, montrer des solutions de contournement aux problèmes et bugs. Notamment la version 5.0.0.73 sera certainement déployée à tous les utilisateurs. Cette 5.0.0.73 arrive avec Android aosp 13 ce qui générera aussi des questions. Nous devrions avoir également la présence de certains développeurs d’applications tierces notamment en la personne de Ruben de Smet avec un moment de travail sur leurs applications (hackaton ?). Nous espérons également la venue d’Andrew Branson, salarié de Jolla, qui pourra alors nous présenter de manière concrète le nouveau J2.
https://mastodon.social/@rubdos
https://mastodon.social/@abranson
Bien entendu, cette journée pourra vraisemblablement intéresser les « linuxiens » lyonnais 😉 et tout le monde est bienvenu, dans la limite de la capacité de la salle. Nous pourrions même aider ceux et celles qui auraient en « stock » un sony xperia xa2, ou x10ii ou x10iii à flasher leur téléphone (install party !). Il y a d’autres smartphones compatibles pouvant accepter des versions communautaires de Sailfish OS.
Le système n’étant pas totalement libre, et les contours de l’événement aillant mis du temps à se préciser, la collégiale de l’ALDIL n’a pas souhaité y être associée. Mais ce serait quand même dommage ne pas en dire quelques mots. Voilà donc cet article, à la publication certes un peu tardive, mais autre ambition que d’informer notre réseau.
Vous voilà donc, chères lectrices, chers lecteurs, dans la confidence de ce modeste événement. Un rendez-vous qui pourrait bien se renouveler. Et avec les prochains changements de CGU d’Android2, toute alternative est bonne à connaitre.3
Crédit images :
- Small Group, tuxwrench
- Logo de SailFish OS
- Logo de LALIS
- https://sailfishos.org/ ↩︎
- https://keepandroidopen.org/fr/ ↩︎
- https://petitions.assemblee-nationale.fr/initiatives/i-5304?locale=fr ↩︎
-
Rencontres Francophones Sailfish·OS
La communauté francophone des utilisatrices et utilisateurs de Sailfish OS1 a choisi de se réunir à Lyon, ce samedi 21 mars.
Le lieu choisi n’est autre que l’AltNet, au 7 Place Louis Chazette 69001 Lyon. Les membres de l’ALDIL connaissent cette espace pour y avoir fait leur dernière AG et leur apéro de rentrée.
LALIS, dont le local est adjacent, a accompagné les préparatifs de ce rassemblement inédit.
Le système Sailfish OS pour smartphone, en quelques mots :
Sailfish OS est une distribution linux et les paquets sont au format RPM.
Sont propriétaires pour l’essentiel:
– « le bureau » appelé Silica (c’est le Plasma de cette distribution linux pour donner un exemple) lui même basé sur Qt.
– AAS, c’est à dire le Android App Support qui fonctionne dans un container afin de faire tourner un Android aosp, ce qui permet de combler les lacunes des applications natives,
– le clavier prédictif et vraisemblablement quelques autres bricoles dont je n’ai pas la liste avec précision 😉
À noter aussi l’histoire de l’entreprise Jolla qui est née sur les « cendres » de la branche smartphone de Nokia.
Concernant l’événement en lui-même, voici de quoi il retourne :
C’est une journée destinée aux utilisateurs de Sailfish OS avec notamment le but de répondre aux questions, montrer des solutions de contournement aux problèmes et bugs. Notamment la version 5.0.0.73 sera certainement déployée à tous les utilisateurs. Cette 5.0.0.73 arrive avec Android aosp 13 ce qui générera aussi des questions. Nous devrions avoir également la présence de certains développeurs d’applications tierces notamment en la personne de Ruben de Smet avec un moment de travail sur leurs applications (hackaton ?). Nous espérons également la venue d’Andrew Branson, salarié de Jolla, qui pourra alors nous présenter de manière concrète le nouveau J2.
https://mastodon.social/@rubdos
https://mastodon.social/@abranson
Bien entendu, cette journée pourra vraisemblablement intéresser les « linuxiens » lyonnais 😉 et tout le monde est bienvenu, dans la limite de la capacité de la salle. Nous pourrions même aider ceux et celles qui auraient en « stock » un sony xperia xa2, ou x10ii ou x10iii à flasher leur téléphone (install party !). Il y a d’autres smartphones compatibles pouvant accepter des versions communautaires de Sailfish OS.
Le système n’étant pas totalement libre, et les contours de l’événement aillant mis du temps à se préciser, la collégiale de l’ALDIL n’a pas souhaité y être associée. Mais ce serait quand même dommage ne pas en dire quelques mots. Voilà donc cet article, à la publication certes un peu tardive, mais autre ambition que d’informer notre réseau.
Vous voilà donc, chères lectrices, chers lecteurs, dans la confidence de ce modeste événement. Un rendez-vous qui pourrait bien se renouveler. Et avec les prochains changements de CGU d’Android2, toute alternative est bonne à connaitre.3
Crédit images :
- Small Group, tuxwrench
- Logo de SailFish OS
- Logo de LALIS
- https://sailfishos.org/ ↩︎
- https://keepandroidopen.org/fr/ ↩︎
- https://petitions.assemblee-nationale.fr/initiatives/i-5304?locale=fr ↩︎
-
Rencontres Francophones Sailfish·OS
La communauté francophone des utilisatrices et utilisateurs de Sailfish OS1 a choisi de se réunir à Lyon, ce samedi 21 mars.
Le lieu choisi n’est autre que l’AltNet, au 7 Place Louis Chazette 69001 Lyon. Les membres de l’ALDIL connaissent cette espace pour y avoir fait leur dernière AG et leur apéro de rentrée.
LALIS, dont le local est adjacent, a accompagné les préparatifs de ce rassemblement inédit.
Le système Sailfish OS pour smartphone, en quelques mots :
Sailfish OS est une distribution linux et les paquets sont au format RPM.
Sont propriétaires pour l’essentiel:
– « le bureau » appelé Silica (c’est le Plasma de cette distribution linux pour donner un exemple) lui même basé sur Qt.
– AAS, c’est à dire le Android App Support qui fonctionne dans un container afin de faire tourner un Android aosp, ce qui permet de combler les lacunes des applications natives,
– le clavier prédictif et vraisemblablement quelques autres bricoles dont je n’ai pas la liste avec précision 😉
À noter aussi l’histoire de l’entreprise Jolla qui est née sur les « cendres » de la branche smartphone de Nokia.
Concernant l’événement en lui-même, voici de quoi il retourne :
C’est une journée destinée aux utilisateurs de Sailfish OS avec notamment le but de répondre aux questions, montrer des solutions de contournement aux problèmes et bugs. Notamment la version 5.0.0.73 sera certainement déployée à tous les utilisateurs. Cette 5.0.0.73 arrive avec Android aosp 13 ce qui générera aussi des questions. Nous devrions avoir également la présence de certains développeurs d’applications tierces notamment en la personne de Ruben de Smet avec un moment de travail sur leurs applications (hackaton ?). Nous espérons également la venue d’Andrew Branson, salarié de Jolla, qui pourra alors nous présenter de manière concrète le nouveau J2.
https://mastodon.social/@rubdos
https://mastodon.social/@abranson
Bien entendu, cette journée pourra vraisemblablement intéresser les « linuxiens » lyonnais 😉 et tout le monde est bienvenu, dans la limite de la capacité de la salle. Nous pourrions même aider ceux et celles qui auraient en « stock » un sony xperia xa2, ou x10ii ou x10iii à flasher leur téléphone (install party !). Il y a d’autres smartphones compatibles pouvant accepter des versions communautaires de Sailfish OS.
Le système n’étant pas totalement libre, et les contours de l’événement aillant mis du temps à se préciser, la collégiale de l’ALDIL n’a pas souhaité y être associée. Mais ce serait quand même dommage ne pas en dire quelques mots. Voilà donc cet article, à la publication certes un peu tardive, mais autre ambition que d’informer notre réseau.
Vous voilà donc, chères lectrices, chers lecteurs, dans la confidence de ce modeste événement. Un rendez-vous qui pourrait bien se renouveler. Et avec les prochains changements de CGU d’Android2, toute alternative est bonne à connaitre.3
Crédit images :
- Small Group, tuxwrench
- Logo de SailFish OS
- Logo de LALIS
- https://sailfishos.org/ ↩︎
- https://keepandroidopen.org/fr/ ↩︎
- https://petitions.assemblee-nationale.fr/initiatives/i-5304?locale=fr ↩︎
-
💡如果喜欢这些内容对你有帮助，不妨分享转嘟，让这份声音传得远一点
@board B 站UP主@科技老男孩于 2026 年 2 月 27 日发布了视频：
《对比满血版 Android，国产安卓阉割了哪些功能？》。
遗憾的是，该视频在上线后不久后 (大概为3月2日) 便因“不可抗力”被下架。为了对抗这种信息的阻断，UP 主已在评论区置顶声明：将该视频彻底开源： 授予任何人免费、不受限制地分发此视频的权利。1. 本视频不仅仅探讨了国产手机对用户的种种限制，还揭示了国产手机将使用者作为`潜在受害者`乃至`潜在罪犯`，推荐香油们观看，了解国产安卓厂家的所作所为；
2. 你认为你买的是手机的所有权，实际上使用权都不一定完整；
3. Android修改于开放的Linux内核，但是在国产手机厂家却为了符合规定，将其魔改为了布满监控的监狱；
4. 即使你使用苹果，也不代表一定安全，苹果也有为了进入中国市场而妥协。我已将视频上传至Peertube(属于联邦宇宙平台)：https://peertube.feddit.social/w/tc7UFZa5aE6RRk5UzE7XD8
其他被下架的视频：【极客湾】手机游戏性能大横评：厂商作弊太疯狂！https://peertube.feddit.social/w/gXiCLMjwdC3348nYY5L3Bb虽然视频在YouTube、X、OneDrive等国外平台分发，但是我们仍然需要像Peertube去中心化的平台记录真相；OneDrive：https://onedrive.live.com/?redeem=aHR0cHM6Ly8xZHJ2Lm1zL2YvYy9lNTY1YjIzOWQ0MWM4MGRlL0lnRFptcWIxZnZCVVFvSmVtSU5VWXZFWUFST0pKMl94NVg1NWgzYzQyUTg4UzFN&id=E565B239D41C80DE%21sf5a69ad9f07e4254825e98835462f118&cid=E565B239D41C80DE
再引申一个链接，安卓将成为一个封闭平台：https://keepandroidopen.org/zh-CN -
💡如果喜欢这些内容对你有帮助，不妨分享转嘟，让这份声音传得远一点
@board B 站UP主@科技老男孩于 2026 年 2 月 27 日发布了视频：
《对比满血版 Android，国产安卓阉割了哪些功能？》。
遗憾的是，该视频在上线后不久后 (大概为3月2日) 便因“不可抗力”被下架。为了对抗这种信息的阻断，UP 主已在评论区置顶声明：将该视频彻底开源： 授予任何人免费、不受限制地分发此视频的权利。1. 本视频不仅仅探讨了国产手机对用户的种种限制，还揭示了国产手机将使用者作为`潜在受害者`乃至`潜在罪犯`，推荐香油们观看，了解国产安卓厂家的所作所为；
2. 你认为你买的是手机的所有权，实际上使用权都不一定完整；
3. Android修改于开放的Linux内核，但是在国产手机厂家却为了符合规定，将其魔改为了布满监控的监狱；
4. 即使你使用苹果，也不代表一定安全，苹果也有为了进入中国市场而妥协。我已将视频上传至Peertube(属于联邦宇宙平台)：https://peertube.feddit.social/w/tc7UFZa5aE6RRk5UzE7XD8
其他被下架的视频：【极客湾】手机游戏性能大横评：厂商作弊太疯狂！https://peertube.feddit.social/w/gXiCLMjwdC3348nYY5L3Bb虽然视频在YouTube、X、OneDrive等国外平台分发，但是我们仍然需要像Peertube去中心化的平台记录真相；OneDrive：https://onedrive.live.com/?redeem=aHR0cHM6Ly8xZHJ2Lm1zL2YvYy9lNTY1YjIzOWQ0MWM4MGRlL0lnRFptcWIxZnZCVVFvSmVtSU5VWXZFWUFST0pKMl94NVg1NWgzYzQyUTg4UzFN&id=E565B239D41C80DE%21sf5a69ad9f07e4254825e98835462f118&cid=E565B239D41C80DE
再引申一个链接，安卓将成为一个封闭平台：https://keepandroidopen.org/zh-CN -
💡如果喜欢这些内容对你有帮助，不妨分享转嘟，让这份声音传得远一点
@board B 站UP主@科技老男孩于 2026 年 2 月 27 日发布了视频：
《对比满血版 Android，国产安卓阉割了哪些功能？》。
遗憾的是，该视频在上线后不久后 (大概为3月2日) 便因“不可抗力”被下架。为了对抗这种信息的阻断，UP 主已在评论区置顶声明：将该视频彻底开源： 授予任何人免费、不受限制地分发此视频的权利。1. 本视频不仅仅探讨了国产手机对用户的种种限制，还揭示了国产手机将使用者作为`潜在受害者`乃至`潜在罪犯`，推荐香油们观看，了解国产安卓厂家的所作所为；
2. 你认为你买的是手机的所有权，实际上使用权都不一定完整；
3. Android修改于开放的Linux内核，但是在国产手机厂家却为了符合规定，将其魔改为了布满监控的监狱；
4. 即使你使用苹果，也不代表一定安全，苹果也有为了进入中国市场而妥协。我已将视频上传至Peertube(属于联邦宇宙平台)：https://peertube.feddit.social/w/tc7UFZa5aE6RRk5UzE7XD8
其他被下架的视频：【极客湾】手机游戏性能大横评：厂商作弊太疯狂！https://peertube.feddit.social/w/gXiCLMjwdC3348nYY5L3Bb虽然视频在YouTube、X、OneDrive等国外平台分发，但是我们仍然需要像Peertube去中心化的平台记录真相；OneDrive：https://onedrive.live.com/?redeem=aHR0cHM6Ly8xZHJ2Lm1zL2YvYy9lNTY1YjIzOWQ0MWM4MGRlL0lnRFptcWIxZnZCVVFvSmVtSU5VWXZFWUFST0pKMl94NVg1NWgzYzQyUTg4UzFN&id=E565B239D41C80DE%21sf5a69ad9f07e4254825e98835462f118&cid=E565B239D41C80DE
再引申一个链接，安卓将成为一个封闭平台：https://keepandroidopen.org/zh-CN -
💡如果喜欢这些内容对你有帮助，不妨分享转嘟，让这份声音传得远一点
@board B 站UP主@科技老男孩于 2026 年 2 月 27 日发布了视频：
《对比满血版 Android，国产安卓阉割了哪些功能？》。
遗憾的是，该视频在上线后不久后 (大概为3月2日) 便因“不可抗力”被下架。为了对抗这种信息的阻断，UP 主已在评论区置顶声明：将该视频彻底开源： 授予任何人免费、不受限制地分发此视频的权利。1. 本视频不仅仅探讨了国产手机对用户的种种限制，还揭示了国产手机将使用者作为`潜在受害者`乃至`潜在罪犯`，推荐香油们观看，了解国产安卓厂家的所作所为；
2. 你认为你买的是手机的所有权，实际上使用权都不一定完整；
3. Android修改于开放的Linux内核，但是在国产手机厂家却为了符合规定，将其魔改为了布满监控的监狱；
4. 即使你使用苹果，也不代表一定安全，苹果也有为了进入中国市场而妥协。我已将视频上传至Peertube(属于联邦宇宙平台)：https://peertube.feddit.social/w/tc7UFZa5aE6RRk5UzE7XD8
其他被下架的视频：【极客湾】手机游戏性能大横评：厂商作弊太疯狂！https://peertube.feddit.social/w/gXiCLMjwdC3348nYY5L3Bb虽然视频在YouTube、X、OneDrive等国外平台分发，但是我们仍然需要像Peertube去中心化的平台记录真相；OneDrive：https://onedrive.live.com/?redeem=aHR0cHM6Ly8xZHJ2Lm1zL2YvYy9lNTY1YjIzOWQ0MWM4MGRlL0lnRFptcWIxZnZCVVFvSmVtSU5VWXZFWUFST0pKMl94NVg1NWgzYzQyUTg4UzFN&id=E565B239D41C80DE%21sf5a69ad9f07e4254825e98835462f118&cid=E565B239D41C80DE
再引申一个链接，安卓将成为一个封闭平台：https://keepandroidopen.org/zh-CN -
💡如果喜欢这些内容对你有帮助，不妨分享转嘟，让这份声音传得远一点
@board B 站UP主@科技老男孩于 2026 年 2 月 27 日发布了视频：
《对比满血版 Android，国产安卓阉割了哪些功能？》。
遗憾的是，该视频在上线后不久后 (大概为3月2日) 便因“不可抗力”被下架。为了对抗这种信息的阻断，UP 主已在评论区置顶声明：将该视频彻底开源： 授予任何人免费、不受限制地分发此视频的权利。1. 本视频不仅仅探讨了国产手机对用户的种种限制，还揭示了国产手机将使用者作为`潜在受害者`乃至`潜在罪犯`，推荐香油们观看，了解国产安卓厂家的所作所为；
2. 你认为你买的是手机的所有权，实际上使用权都不一定完整；
3. Android修改于开放的Linux内核，但是在国产手机厂家却为了符合规定，将其魔改为了布满监控的监狱；
4. 即使你使用苹果，也不代表一定安全，苹果也有为了进入中国市场而妥协。我已将视频上传至Peertube(属于联邦宇宙平台)：https://peertube.feddit.social/w/tc7UFZa5aE6RRk5UzE7XD8
其他被下架的视频：【极客湾】手机游戏性能大横评：厂商作弊太疯狂！https://peertube.feddit.social/w/gXiCLMjwdC3348nYY5L3Bb虽然视频在YouTube、X、OneDrive等国外平台分发，但是我们仍然需要像Peertube去中心化的平台记录真相；OneDrive：https://onedrive.live.com/?redeem=aHR0cHM6Ly8xZHJ2Lm1zL2YvYy9lNTY1YjIzOWQ0MWM4MGRlL0lnRFptcWIxZnZCVVFvSmVtSU5VWXZFWUFST0pKMl94NVg1NWgzYzQyUTg4UzFN&id=E565B239D41C80DE%21sf5a69ad9f07e4254825e98835462f118&cid=E565B239D41C80DE
再引申一个链接，安卓将成为一个封闭平台：https://keepandroidopen.org/zh-CN -
Android dead on 01 September 2026 (09-01-2K26)
Unless you've been living under a rock at the bottom of the Mariana Trench, you know that google wants to close the Android Platform up, after having made sure that many hundreds of millions (actually more than (5 * 10↑ 9)) Androids are running globally.
Google wants to close up Android tighter that a father isolated his promiscuous daughter in the dark ages...
• Some bullets points
- Android development spawned in 2003 by Android, Inc.
- Android Inc fetches the Open Source Linux kernel and studies to use it for it's upcoming smart phone platform in 2003
- Google gobbled them up in 2005
Android was not google's idea!
Android was not google's idea!
Android was not google's idea!
- Android beta is released November 5, 2007
Android stable v1.0 is released September 23, 2008
Google made sure that in the years that followed they subtly started to make certain things hard to do, which were easy and open in the beginning
Way in the beginning, those of you who had an android then remember how easy it was to install software on your phone
When you install anything now that's Open Source playstore tells you that it's unsafe.
Even when you open a PO3 / IMAP account on your android, google shows you the perfectly fine server certificate and tells you it's not good, forcing you to click advanced then yes to use an email account NOT sanctioned by google, in their gmail android program
gmail android is a POS in comparison with the awsome MUTT OpenSource mail client
installing KDE_Connect a magnificent program suite which makes your android communicate properly with any Linux or BSD server / client gives problems too and is even SABOTAGED by android comms & battery protocol
the battery protocol constantly kills KDE_Connect making transfer and control a PITA
the comms protocol drops packets of KDE_Connect making it look like the program fails horribly
install KDE_Connect on an Open Source Android distro and you will see that the program suite not only works perfectly, it transfers files as fast as your phones tranceiver will pump them to your target phone or computer, running and Open Source Operating System
The beginning of the END
- Google starts with forcing programmers to submit a government issued ID for just writing software, released on the app store
- no Open Source programmer is crazy enough to do so, so you now need other means like FDroid & similar to install them, or go straight to their Codeberg or github pages to fetch them, making phone illiterates losing access to their beloved Open Source android programs
- Google annouces that it will block non sanctioned (Open Source) programs from installing after undisclosed ammount of time
- Google announces the date when it will hard block you, the propriator of your Androids to install software on your OWN FUCKING COMPUTER!!!*
WTF google! have you gone microSLOP?
We the people can stop Alphabet from this bullshit
• Those of us who live in the EU especially have a tremendous stopping power, to the BULLYING of Alphabet regardless of which EU country you live in
WHY?
- Google has a market of hundreds of millions of high android spending users there
- Loosing the EU all together will be a tremendous financial blow to google
- Remember that apple bowed to EU will and put USBC connectors on their hardware way before the deadline was put
- apple did that globally, because that makes logistical sense
apple bowed to the EU because of financial greed, not the fine
Alphabet is in a similar boat when google is stopped there to close the platform it's logistically easier to just remove the measures globally on their android platform
Rest of Terra
- The rest of us not stated in the below doc should do the following
- call our governments to do something by calling Ambassador / consul of US to give letter with grievances even if your country has less than 750.000 inhabitants, the protest matters, find your representatives and do it
- find alternative OS to run on your current and future androids
DITCH android if and when the lockdown comes
that means we the people gave up and lost
android humanity is than fiucked
no one of us wants to see that
FIGHT for your Android rights. The computer is your private posession!
Sending Universal Love and Universal Energy to all who read this doc
•
•Sources
mea
https://keepandroidopen.org/
https://en.wikipedia.org/wiki/Android_version_history
https://www.sci-tech-today.com/stats/android-phones-statistics/
https://www.bankmycell.com/blog/how-many-android-users-are-there
https://en.wikipedia.org/wiki/Android_version_history#OpenSource #ClosedSource #kernel #Torvalds #Linus #Linux #LinusTorvalds #technology #programming #networking #Your #Rights #ownership #alphabet #google #enshittification #fight #Android #AndroidInc
-
Android dead on 01 September 2026 (09-01-2K26)
Unless you've been living under a rock at the bottom of the Mariana Trench, you know that google wants to close the Android Platform up, after having made sure that many hundreds of millions (actually more than (5 * 10↑ 9)) Androids are running globally.
Google wants to close up Android tighter that a father isolated his promiscuous daughter in the dark ages...
• Some bullets points
- Android development spawned in 2003 by Android, Inc.
- Android Inc fetches the Open Source Linux kernel and studies to use it for it's upcoming smart phone platform in 2003
- Google gobbled them up in 2005
Android was not google's idea!
Android was not google's idea!
Android was not google's idea!
- Android beta is released November 5, 2007
Android stable v1.0 is released September 23, 2008
Google made sure that in the years that followed they subtly started to make certain things hard to do, which were easy and open in the beginning
Way in the beginning, those of you who had an android then remember how easy it was to install software on your phone
When you install anything now that's Open Source playstore tells you that it's unsafe.
Even when you open a PO3 / IMAP account on your android, google shows you the perfectly fine server certificate and tells you it's not good, forcing you to click advanced then yes to use an email account NOT sanctioned by google, in their gmail android program
gmail android is a POS in comparison with the awsome MUTT OpenSource mail client
installing KDE_Connect a magnificent program suite which makes your android communicate properly with any Linux or BSD server / client gives problems too and is even SABOTAGED by android comms & battery protocol
the battery protocol constantly kills KDE_Connect making transfer and control a PITA
the comms protocol drops packets of KDE_Connect making it look like the program fails horribly
install KDE_Connect on an Open Source Android distro and you will see that the program suite not only works perfectly, it transfers files as fast as your phones tranceiver will pump them to your target phone or computer, running and Open Source Operating System
The beginning of the END
- Google starts with forcing programmers to submit a government issued ID for just writing software, released on the app store
- no Open Source programmer is crazy enough to do so, so you now need other means like FDroid & similar to install them, or go straight to their Codeberg or github pages to fetch them, making phone illiterates losing access to their beloved Open Source android programs
- Google annouces that it will block non sanctioned (Open Source) programs from installing after undisclosed ammount of time
- Google announces the date when it will hard block you, the propriator of your Androids to install software on your OWN FUCKING COMPUTER!!!*
WTF google! have you gone microSLOP?
We the people can stop Alphabet from this bullshit
• Those of us who live in the EU especially have a tremendous stopping power, to the BULLYING of Alphabet regardless of which EU country you live in
WHY?
- Google has a market of hundreds of millions of high android spending users there
- Loosing the EU all together will be a tremendous financial blow to google
- Remember that apple bowed to EU will and put USBC connectors on their hardware way before the deadline was put
- apple did that globally, because that makes logistical sense
apple bowed to the EU because of financial greed, not the fine
Alphabet is in a similar boat when google is stopped there to close the platform it's logistically easier to just remove the measures globally on their android platform
Rest of Terra
- The rest of us not stated in the below doc should do the following
- call our governments to do something by calling Ambassador / consul of US to give letter with grievances even if your country has less than 750.000 inhabitants, the protest matters, find your representatives and do it
- find alternative OS to run on your current and future androids
DITCH android if and when the lockdown comes
that means we the people gave up and lost
android humanity is than fiucked
no one of us wants to see that
FIGHT for your Android rights. The computer is your private posession!
Sending Universal Love and Universal Energy to all who read this doc
•
•Sources
mea
https://keepandroidopen.org/
https://en.wikipedia.org/wiki/Android_version_history
https://www.sci-tech-today.com/stats/android-phones-statistics/
https://www.bankmycell.com/blog/how-many-android-users-are-there
https://en.wikipedia.org/wiki/Android_version_history#OpenSource #ClosedSource #kernel #Torvalds #Linus #Linux #LinusTorvalds #technology #programming #networking #Your #Rights #ownership #alphabet #google #enshittification #fight #Android #AndroidInc
-
Android dead on 01 September 2026 (09-01-2K26)
Unless you've been living under a rock at the bottom of the Mariana Trench, you know that google wants to close the Android Platform up, after having made sure that many hundreds of millions (actually more than (5 * 10↑ 9)) Androids are running globally.
Google wants to close up Android tighter that a father isolated his promiscuous daughter in the dark ages...
• Some bullets points
- Android development spawned in 2003 by Android, Inc.
- Android Inc fetches the Open Source Linux kernel and studies to use it for it's upcoming smart phone platform in 2003
- Google gobbled them up in 2005
Android was not google's idea!
Android was not google's idea!
Android was not google's idea!
- Android beta is released November 5, 2007
Android stable v1.0 is released September 23, 2008
Google made sure that in the years that followed they subtly started to make certain things hard to do, which were easy and open in the beginning
Way in the beginning, those of you who had an android then remember how easy it was to install software on your phone
When you install anything now that's Open Source playstore tells you that it's unsafe.
Even when you open a PO3 / IMAP account on your android, google shows you the perfectly fine server certificate and tells you it's not good, forcing you to click advanced then yes to use an email account NOT sanctioned by google, in their gmail android program
gmail android is a POS in comparison with the awsome MUTT OpenSource mail client
installing KDE_Connect a magnificent program suite which makes your android communicate properly with any Linux or BSD server / client gives problems too and is even SABOTAGED by android comms & battery protocol
the battery protocol constantly kills KDE_Connect making transfer and control a PITA
the comms protocol drops packets of KDE_Connect making it look like the program fails horribly
install KDE_Connect on an Open Source Android distro and you will see that the program suite not only works perfectly, it transfers files as fast as your phones tranceiver will pump them to your target phone or computer, running and Open Source Operating System
The beginning of the END
- Google starts with forcing programmers to submit a government issued ID for just writing software, released on the app store
- no Open Source programmer is crazy enough to do so, so you now need other means like FDroid & similar to install them, or go straight to their Codeberg or github pages to fetch them, making phone illiterates losing access to their beloved Open Source android programs
- Google annouces that it will block non sanctioned (Open Source) programs from installing after undisclosed ammount of time
- Google announces the date when it will hard block you, the propriator of your Androids to install software on your OWN FUCKING COMPUTER!!!*
WTF google! have you gone microSLOP?
We the people can stop Alphabet from this bullshit
• Those of us who live in the EU especially have a tremendous stopping power, to the BULLYING of Alphabet regardless of which EU country you live in
WHY?
- Google has a market of hundreds of millions of high android spending users there
- Loosing the EU all together will be a tremendous financial blow to google
- Remember that apple bowed to EU will and put USBC connectors on their hardware way before the deadline was put
- apple did that globally, because that makes logistical sense
apple bowed to the EU because of financial greed, not the fine
Alphabet is in a similar boat when google is stopped there to close the platform it's logistically easier to just remove the measures globally on their android platform
Rest of Terra
- The rest of us not stated in the below doc should do the following
- call our governments to do something by calling Ambassador / consul of US to give letter with grievances even if your country has less than 750.000 inhabitants, the protest matters, find your representatives and do it
- find alternative OS to run on your current and future androids
DITCH android if and when the lockdown comes
that means we the people gave up and lost
android humanity is than fiucked
no one of us wants to see that
FIGHT for your Android rights. The computer is your private posession!
Sending Universal Love and Universal Energy to all who read this doc
•
•Sources
mea
https://keepandroidopen.org/
https://en.wikipedia.org/wiki/Android_version_history
https://www.sci-tech-today.com/stats/android-phones-statistics/
https://www.bankmycell.com/blog/how-many-android-users-are-there
https://en.wikipedia.org/wiki/Android_version_history#OpenSource #ClosedSource #kernel #Torvalds #Linus #Linux #LinusTorvalds #technology #programming #networking #Your #Rights #ownership #alphabet #google #enshittification #fight #Android #AndroidInc
-
Android dead on 01 September 2026 (09-01-2K26)
Unless you've been living under a rock at the bottom of the Mariana Trench, you know that google wants to close the Android Platform up, after having made sure that many hundreds of millions (actually more than (5 * 10↑ 9)) Androids are running globally.
Google wants to close up Android tighter that a father isolated his promiscuous daughter in the dark ages...
• Some bullets points
- Android development spawned in 2003 by Android, Inc.
- Android Inc fetches the Open Source Linux kernel and studies to use it for it's upcoming smart phone platform in 2003
- Google gobbled them up in 2005
Android was not google's idea!
Android was not google's idea!
Android was not google's idea!
- Android beta is released November 5, 2007
Android stable v1.0 is released September 23, 2008
Google made sure that in the years that followed they subtly started to make certain things hard to do, which were easy and open in the beginning
Way in the beginning, those of you who had an android then remember how easy it was to install software on your phone
When you install anything now that's Open Source playstore tells you that it's unsafe.
Even when you open a PO3 / IMAP account on your android, google shows you the perfectly fine server certificate and tells you it's not good, forcing you to click advanced then yes to use an email account NOT sanctioned by google, in their gmail android program
gmail android is a POS in comparison with the awsome MUTT OpenSource mail client
installing KDE_Connect a magnificent program suite which makes your android communicate properly with any Linux or BSD server / client gives problems too and is even SABOTAGED by android comms & battery protocol
the battery protocol constantly kills KDE_Connect making transfer and control a PITA
the comms protocol drops packets of KDE_Connect making it look like the program fails horribly
install KDE_Connect on an Open Source Android distro and you will see that the program suite not only works perfectly, it transfers files as fast as your phones tranceiver will pump them to your target phone or computer, running and Open Source Operating System
The beginning of the END
- Google starts with forcing programmers to submit a government issued ID for just writing software, released on the app store
- no Open Source programmer is crazy enough to do so, so you now need other means like FDroid & similar to install them, or go straight to their Codeberg or github pages to fetch them, making phone illiterates losing access to their beloved Open Source android programs
- Google annouces that it will block non sanctioned (Open Source) programs from installing after undisclosed ammount of time
- Google announces the date when it will hard block you, the propriator of your Androids to install software on your OWN FUCKING COMPUTER!!!*
WTF google! have you gone microSLOP?
We the people can stop Alphabet from this bullshit
• Those of us who live in the EU especially have a tremendous stopping power, to the BULLYING of Alphabet regardless of which EU country you live in
WHY?
- Google has a market of hundreds of millions of high android spending users there
- Loosing the EU all together will be a tremendous financial blow to google
- Remember that apple bowed to EU will and put USBC connectors on their hardware way before the deadline was put
- apple did that globally, because that makes logistical sense
apple bowed to the EU because of financial greed, not the fine
Alphabet is in a similar boat when google is stopped there to close the platform it's logistically easier to just remove the measures globally on their android platform
Rest of Terra
- The rest of us not stated in the below doc should do the following
- call our governments to do something by calling Ambassador / consul of US to give letter with grievances even if your country has less than 750.000 inhabitants, the protest matters, find your representatives and do it
- find alternative OS to run on your current and future androids
DITCH android if and when the lockdown comes
that means we the people gave up and lost
android humanity is than fiucked
no one of us wants to see that
FIGHT for your Android rights. The computer is your private posession!
Sending Universal Love and Universal Energy to all who read this doc
•
•Sources
mea
https://keepandroidopen.org/
https://en.wikipedia.org/wiki/Android_version_history
https://www.sci-tech-today.com/stats/android-phones-statistics/
https://www.bankmycell.com/blog/how-many-android-users-are-there
https://en.wikipedia.org/wiki/Android_version_history#OpenSource #ClosedSource #kernel #Torvalds #Linus #Linux #LinusTorvalds #technology #programming #networking #Your #Rights #ownership #alphabet #google #enshittification #fight #Android #AndroidInc
-
Android dead on 01 September 2026 (09-01-2K26)
Unless you've been living under a rock at the bottom of the Mariana Trench, you know that google wants to close the Android Platform up, after having made sure that many hundreds of millions (actually more than (5 * 10↑ 9)) Androids are running globally.
Google wants to close up Android tighter that a father isolated his promiscuous daughter in the dark ages...
• Some bullets points
- Android development spawned in 2003 by Android, Inc.
- Android Inc fetches the Open Source Linux kernel and studies to use it for it's upcoming smart phone platform in 2003
- Google gobbled them up in 2005
Android was not google's idea!
Android was not google's idea!
Android was not google's idea!
- Android beta is released November 5, 2007
Android stable v1.0 is released September 23, 2008
Google made sure that in the years that followed they subtly started to make certain things hard to do, which were easy and open in the beginning
Way in the beginning, those of you who had an android then remember how easy it was to install software on your phone
When you install anything now that's Open Source playstore tells you that it's unsafe.
Even when you open a PO3 / IMAP account on your android, google shows you the perfectly fine server certificate and tells you it's not good, forcing you to click advanced then yes to use an email account NOT sanctioned by google, in their gmail android program
gmail android is a POS in comparison with the awsome MUTT OpenSource mail client
installing KDE_Connect a magnificent program suite which makes your android communicate properly with any Linux or BSD server / client gives problems too and is even SABOTAGED by android comms & battery protocol
the battery protocol constantly kills KDE_Connect making transfer and control a PITA
the comms protocol drops packets of KDE_Connect making it look like the program fails horribly
install KDE_Connect on an Open Source Android distro and you will see that the program suite not only works perfectly, it transfers files as fast as your phones tranceiver will pump them to your target phone or computer, running and Open Source Operating System
The beginning of the END
- Google starts with forcing programmers to submit a government issued ID for just writing software, released on the app store
- no Open Source programmer is crazy enough to do so, so you now need other means like FDroid & similar to install them, or go straight to their Codeberg or github pages to fetch them, making phone illiterates losing access to their beloved Open Source android programs
- Google annouces that it will block non sanctioned (Open Source) programs from installing after undisclosed ammount of time
- Google announces the date when it will hard block you, the propriator of your Androids to install software on your OWN FUCKING COMPUTER!!!*
WTF google! have you gone microSLOP?
We the people can stop Alphabet from this bullshit
• Those of us who live in the EU especially have a tremendous stopping power, to the BULLYING of Alphabet regardless of which EU country you live in
WHY?
- Google has a market of hundreds of millions of high android spending users there
- Loosing the EU all together will be a tremendous financial blow to google
- Remember that apple bowed to EU will and put USBC connectors on their hardware way before the deadline was put
- apple did that globally, because that makes logistical sense
apple bowed to the EU because of financial greed, not the fine
Alphabet is in a similar boat when google is stopped there to close the platform it's logistically easier to just remove the measures globally on their android platform
Rest of Terra
- The rest of us not stated in the below doc should do the following
- call our governments to do something by calling Ambassador / consul of US to give letter with grievances even if your country has less than 750.000 inhabitants, the protest matters, find your representatives and do it
- find alternative OS to run on your current and future androids
DITCH android if and when the lockdown comes
that means we the people gave up and lost
android humanity is than fiucked
no one of us wants to see that
FIGHT for your Android rights. The computer is your private posession!
Sending Universal Love and Universal Energy to all who read this doc
•
•Sources
mea
https://keepandroidopen.org/
https://en.wikipedia.org/wiki/Android_version_history
https://www.sci-tech-today.com/stats/android-phones-statistics/
https://www.bankmycell.com/blog/how-many-android-users-are-there
https://en.wikipedia.org/wiki/Android_version_history#OpenSource #ClosedSource #kernel #Torvalds #Linus #Linux #LinusTorvalds #technology #programming #networking #Your #Rights #ownership #alphabet #google #enshittification #fight #Android #AndroidInc
-
RE: https://techhub.social/@keepandroidopen/116340826595529252
Wer keinen Bock mehr auf #USA und Co hat: #GrapheneOSFoundation kommt aus dem demokratischen #Kanada und ist ein freies OS für Smarthones, basierend auf #Android OS, einer gemeinnützigen Organisation. 🔻
-
RE: https://techhub.social/@keepandroidopen/116340826595529252
Wer keinen Bock mehr auf #USA und Co hat: #GrapheneOSFoundation kommt aus dem demokratischen #Kanada und ist ein freies OS für Smarthones, basierend auf #Android OS, einer gemeinnützigen Organisation. 🔻
-
RE: https://techhub.social/@keepandroidopen/116340826595529252
Wer keinen Bock mehr auf #USA und Co hat: #GrapheneOSFoundation kommt aus dem demokratischen #Kanada und ist ein freies OS für Smarthones, basierend auf #Android OS, einer gemeinnützigen Organisation. 🔻
-
RE: https://techhub.social/@keepandroidopen/116340826595529252
Wer keinen Bock mehr auf #USA und Co hat: #GrapheneOSFoundation kommt aus dem demokratischen #Kanada und ist ein freies OS für Smarthones, basierend auf #Android OS, einer gemeinnützigen Organisation. 🔻