Čo chcú voliči Republiky a ako sa to dá dosiahnuť umierneným, konštruktívnym spôsobom?


Kotleba padol ale Republika stúpa. A dosť silne. Jej voliči vnímajú nejaké potreby, ktoré chcú mať naplnené cez Republiku.

Ja to poriadne nesledujem, tak sa do detailov nevyznám. Viete konkrétne sformulovať čo vlastne bežný volič Republiky chce?

A ako by sa to dalo dosiahnuť spôsobom, ktorý by bolo ťažké označiť za fašizmus?

in reply to EfreetSK

Tak to sme sa teda pohli 😅

Asi najbližšie, čo poznám, sa k tomu dostal Ken Wilber v knihe "Trump a post-pravdový svet". Ten popísal situácii v USA, ale základné koncepty by mali fungovať aj na Slovensko. Vychádza z vývinovej psychológie, podľa ktorej sa ľudská psychika vyvíja celý život a dajú sa identifikovať viaceré rozličné fázy vývinu. Argumentuje, že ľudia centrovaní v autoritárskej "jantárovej, modrej" fáze (bežné znaky do napr. čierno-biele chápanie sveta, kolektivizmus, rešpektovanie autority, neprijímanie rozdielov (sexizmus, rasizmus, xenofóbia atď)) boli progresívnymi a liberálnymi vladármi dlhú dobu odsúvaný na druhú koľaj, z čoho bolo nasraní. A keď prišiel Trump, ktorý hovoril presne to čo cítili a nadával na tých, na ktorých aj oni, cítili s ním hlboké spojenie a preto ho volili. To, že je to diktátorský magor im nevadilo, lebo to bol ich diktátorský magor.

Na konceptuálnej úrovni to vnímam rovnako aj na Slovensku. Akurát v úrovni konkrétností už neviem čo slovenskí republikáni chcú... Teda, okrem svojho tatka, ktorý nadáva rovnako ako oni. Ale na začiatok by však rozhodne bola vhodná úcta a neopovrhovanie.

GrapheneOS version 2025122500 released


Tags:

  • 2025122500 (Pixel 6, Pixel 6 Pro, Pixel 6a, Pixel 7, Pixel 7 Pro, Pixel 7a, Pixel Tablet, Pixel Fold, Pixel 8, Pixel 8 Pro, Pixel 8a, Pixel 9, Pixel 9 Pro, Pixel 9 Pro XL, Pixel 9 Pro Fold, Pixel 9a, Pixel 10, Pixel 10 Pro, Pixel 10 Pro XL, Pixel 10 Pro Fold, emulator, generic, other targets)

Changes since the 2025121700 release:

  • restore support for bypassing carriers disallowing choosing the cellular network mode (this was lost in a recent major version migration such as the port to Android 16 QPR1 but we aren't sure exactly when it regressed)
  • remove poorly designed upstream end session button on the lockscreen (it remains available in the power menu)
  • enable feature flag for new upstream end session button in the user switcher
  • switch to vendor files from 2nd December 2025 release (BP4A.251205.006.E1) for devices with it available
  • enable lockscreen widget support
  • fix upstream system_server crash in NotificationHistoryProtoHelper
  • Wi-Fi HAL: ignore debug logging requests on all Pixels with MTE support to avoid a crash from detecting an invalid memory access in the upstream code
  • Sandboxed Google Play compatibility layer: add support for redirecting Google Play location service requests from within Google Play services itself which means the GrapheneOS provided network location will work for internal Play services features such as Google Maps location sharing when redirecting to the OS is enabled (which is the default) and the Location permission is granted to it
  • Sandboxed Google Play compatibility layer: force redirecting Google Play location service requests from within Google Play services and Android Auto when the Location permission is disabled for better error handling (neither properly handles the Location permission not being granted since it's always granted on any Google Mobile Services OS in practice instead of being explicitly opt-in)
  • Sandboxed Google Play compatibility layer: fix a compatibility issue with the Chromium test suite
  • Network Location: improve position estability accuracy and stability
  • Network Location: prevent potential division by zero exception
  • Network Location: improve experimental Wi-Fi RTT support which is still disabled in production
  • kernel (6.1): update to latest GKI LTS branch revision
  • kernel (6.6): update to latest GKI LTS branch revision including update to 6.6.119
  • kernel (6.6): disable CONFIG_TLS to reduce attack surface
  • kernel (6.12): update to latest GKI LTS branch revision including update to 6.12.63
  • kernel (6.12): disable CONFIG_TLS to reduce attack surface
  • include configuration for thermometer on 10th gen Pixels
  • adevtool: auto-detect filesystem image type (ext4 vs. EROFS)
  • adevtool: add support for canary builds
  • adevtool: improve performance
  • remove obsolete workaround for using a prebuilt recovery extension

All of the Android 16 security patches from the current January 2026, February 2026, March 2026, April 2026, May 2026 and June 2026 Android Security Bulletins are included in the 2025121701 security preview release. List of additional fixed CVEs:

  • High: CVE-2025-32348, CVE-2025-48561, CVE-2025-48630, CVE-2025-48641, CVE-2025-48642, CVE-2025-48644, CVE-2025-48645, CVE-2025-48646, CVE-2025-48649, CVE-2025-48652, CVE-2025-48653, CVE-2026-0014, CVE-2026-0015, CVE-2026-0016, CVE-2026-0017, CVE-2026-0018, CVE-2026-0020, CVE-2026-0021, CVE-2026-0022, CVE-2026-0023, CVE-2026-0024, CVE-2026-0025

2025121701 provides at least the full 2026-01-01 Android and Pixel security patch level but will remain marked as providing 2025-12-05.

For detailed information on security preview releases, see our post about it.

in reply to strubbl

Lauren Leek's post about London restaurants was a good read. Her description of Google Maps as more of a market maker than a simple directory is spot on.

GrapheneOS version 2025121700 released


Tags:

  • 2025121700 (Pixel 6, Pixel 6 Pro, Pixel 6a, Pixel 7, Pixel 7 Pro, Pixel 7a, Pixel Tablet, Pixel Fold, Pixel 8, Pixel 8 Pro, Pixel 8a, Pixel 9, Pixel 9 Pro, Pixel 9 Pro XL, Pixel 9 Pro Fold, Pixel 9a, Pixel 10, Pixel 10 Pro, Pixel 10 Pro XL, Pixel 10 Pro Fold, emulator, generic, other targets)

Changes since the 2025121200 release:

  • add workaround for upstream system_server WallpaperManagerService.hasPermission() crash
  • fix upstream system_server crash in NotificationHistory.getPooledStringsToWrite()
  • Launcher: add a workaround for upstream QuickstepModelDelegate.getContainer() crash
  • set initial port security state at an earlier boot stage to improve debugging on production builds where the port state has been changed from the default "Charging-only when locked" to "Charging-only when locked, except before first unlock" or "On"
  • use default desktop mode configuration since our changes are no longer needed to enable features and caused crashes for at least 1 user which were addressed with an out-of-band release prior to this one
  • kernel (6.1): update to latest GKI LTS branch revision
  • kernel (6.1): add back recent dma-buf changes now that an upstream use-after-free bug is resolved
  • kernel (6.6): update to latest GKI LTS branch revision including update to 6.6.118
  • adevtool: update carrier settings
  • Vanadium: update to version 143.0.7499.146.0

All of the Android 16 security patches from the current January 2026, February 2026, March 2026, April 2026, May 2026 and June 2026 Android Security Bulletins are included in the 2025121701 security preview release. List of additional fixed CVEs:

  • High: CVE-2025-32348, CVE-2025-48641, CVE-2026-0014, CVE-2026-0015, CVE-2026-0016, CVE-2026-0017, CVE-2026-0018

2025121701 provides at least the full 2026-01-01 Android and Pixel security patch level but will remain marked as providing 2025-12-05.

For detailed information on security preview releases, see our post about it.

Vanadium version 143.0.7499.146.0 released


Changes in version 143.0.7499.146.0:

  • update to Chromium 143.0.7499.146

A full list of changes from the previous release (version 143.0.7499.109.0) is available through the Git commit log between the releases.

This update is available to GrapheneOS users via our app repository and will also be bundled into the next OS release. Vanadium isn't yet officially available for users outside GrapheneOS, although we plan to do that eventually. It won't be able to provide the WebView outside GrapheneOS and will have missing hardening and other features.

Tools for growing the commons | a diverse set of tools—economic and financial, legal and governance, social and cultural—that help communities build resilient systems designed to last and thrive


Slovenskí esperantisti oslávili Zamenhofov deň 2025 - výročie iniciátora jazyka esperanto


Esperanto je umelý jazyk, ktorého cieľom je poskytnúť ľudstvu možnosť dorozumieť sa s inými ľuďmi z celého sveta ľahko a spravodlivo (keďže nepatrí žiadnemu národu, nikto nemá príliš veľkú výhodu). Jeho základy položil Ľudovít Zamenhof už v roku 1887 a od vtedy sa jeho komunita postupne rozširuje.

15 december je medzi esperantistami slávený ako "Zamenhofov deň", kedy si pripomíname narodeniny jeho iniciátora.

Na Slovensku sme v 2025 oslavovali v Novej Dubnici. V sobotu 13.12. sme začali pracovnou brigádou v Esperantskom archíve Jana Vajsa. Archív je ešte pomerne nový, ale má dosť veľa kníh, časopisov a iných materiálov. Nie všetky sú však zoradené a katalogizované. Je to mravenčia práce ale opäť sme s ňou dobre pohli.

Večer sme spoločnej dohovali a do nálady nám na gitare zahrala a zaspievala Majka Minichová, predovšetkým ľudové piesne preložené do esperanta.

Ďalší deň sme mali pár prednášok v kancelárii občianskeho združenia E@I. Peter Baláž predstavil nedávne aktivity E@I, novo vydané knihy, Svetový kongres esperanta 2026 v Rakúsku a 2027 v Austrálii, ktoré organizuje.


Maciej Jaskot (profesor španielčiny na Krakovskej univerzite) o mýtoch o učení sa jazykov.

KuboF Hromoslav o novinkách z Wikimedia EO (občianske združenie podporujúce Wikipédiu) a Projektejo - novo pripravovanom nástroji projektového manažmentu pre celú esperantskú komunitu.

Spomenuté boli aj aktuálne projekty podporované programom Erasmus+, ako napríklad SANO zastúpený WMEO a EduLand a Deutsch.info z E@I.

This entry was edited (1 month ago)
in reply to EfreetSK

Medžuslovjansky je tiež parádny! Minulý rok som bol na koncerte medžuslovjanskeho pesničkára a bol to jazykový orgazmus 😍 Niektorí z tých medzislovanských jazykov sa chcem niekedy naučiť, ale prioritou pre mňa je pomôcť s vyriešením niektorých celosvetových problémov a výziev, a keď ide o koníčky, radšej sa vrátim k hudbe a foteniu.

Ale ak chceš rýchlo zvládnuť nejaký neštandatdný jazyk,Toki Pona môže byť tá pravá. Je to silne minimalistický jazyk, ktorý sa dá naučiť za 2 týždne, popri deťoch možno za 3. Ale potom je trochu problém v ňom čokoľvek povedať 🤣

Mimochodom, komunita !esperanto@sopuli.xyz je prekvapivo veľká, aj keď tiež nie práve najaktívnejšia 😅

in reply to Václav

Ještě se můžeš podívat tady na reporty: linux-hardware.org/?id=pci%3A1…

Jinak dívám se, že doma v počítači mám MT7927, což je podobný čip používající stejný ovladač, tak se můžu mrknout, jak funguje. Hardware to rozpozná, wifi sítě najde a připojí se to k nim, ale jedu primárně na LAN, takže problémy se stabilitou jsem nezaznamenal.

Windows, dlhodobý kráľ desktopových operačných systémov dlhodobo upadá.


cross-posted from: piefed.blahaj.zone/c/technolog…

Windows Marketshare since 2010

for your enjoyment

source gs.statcounter.com/os-market-s…

Mladí Európania požadujú silnejšiu Európu


cross-posted from: sopuli.xyz/post/38159981

Forget the far right. The kids want a ‘United States of Europe.’

GrapheneOS version 2025121200 released


Tags:

  • 2025121200 (Pixel 6, Pixel 6 Pro, Pixel 6a, Pixel 7, Pixel 7 Pro, Pixel 7a, Pixel Tablet, Pixel Fold, Pixel 8, Pixel 8 Pro, Pixel 8a, Pixel 9, Pixel 9 Pro, Pixel 9 Pro XL, Pixel 9 Pro Fold, Pixel 9a, Pixel 10, Pixel 10 Pro, Pixel 10 Pro XL, Pixel 10 Pro Fold, emulator, generic, other targets)

Changes since the 2025121000 release:

  • disable notification summaries and organizer features due to AOSP and GrapheneOS lacking the AI models used to implement these features
  • add workaround for notification background appearance regression in Android 16 QPR2
  • Vanadium: update to version 143.0.7499.109.0
  • GmsCompatConfig: update to version 167

All of the Android 16 security patches from the current January 2026, February 2026, March 2026, April 2026, May 2026 and June 2026 Android Security Bulletins are included in the 2025121201 security preview release. List of additional fixed CVEs:

  • High: CVE-2025-32348, CVE-2025-48641, CVE-2026-0014, CVE-2026-0015, CVE-2026-0016, CVE-2026-0017, CVE-2026-0018

2025121201 provides at least the full 2026-01-01 Android and Pixel security patch level but will remain marked as providing 2025-12-05.

For detailed information on security preview releases, see our post about it.

Second New IPv4 /24 Subnet Received


We've received a 2nd IPv4 /24 subnet from ARIN for our 2nd anycast DNS network. Both our /24 subnets were obtained quickly under the NRPM 4.10 policy for IPv6 deployment for our dual stack DNS use case. 2nd was obtained without waiting 6 months due to being a discrete network.

We host our own authoritative DNS servers to provide DNS resolution for our services. Authoritative DNS are the servers queried by DNS resolvers run by your ISP, VPN or an explicitly user chosen one such as Cloudflare or Quad9 DNS. We now have our own AS and IP space for this.

Our ns1 has 11 locations on Vultr: New York City, Miami, Los Angeles, Seattle, London, Frankfurt, Singapore, Mumbai, Tokyo, Sao Paulo and Sydney.

Our ns2 has 4 locations on BuyVM: New York City, Miami, Las Vegas and Bern. We'll be adding a 2nd server provider for more locations.

DNS resolvers quickly fall back to the other network if traffic is dropped. Having two discrete networks with separate hosting companies and transit providers provides very high reliability. Individual servers which go down also stop having traffic routed to them due to BGP.

We have tiny website/network servers and also powerful update mirrors around the world. Our DNS servers use a combination of a GeoIP database and their own location to route users to the closest server that's up. Frequent health checks and low expiry time handle server downtime.

GmsCompatConfig version 167 released


Changes in version 167:

  • add stub for BluetoothA2dp.setConnectionPolicy() to fix a crash with a new version of Android Auto

A full list of changes from the previous release (version 166) is available through the Git commit log between the releases (only changes to the gmscompat_config text file and config-holder/ directory are part of GmsCompatConfig).

GmsCompatConfig is the text-based configuration for the GrapheneOS sandboxed Google Play compatibility layer. It provides a large portion of the compatibility shims.

This update is available to GrapheneOS users via our app repository and will also be bundled into the next OS release.

Vanadium version 143.0.7499.109.0 released


Changes in version 143.0.7499.109.0:

  • update to Chromium 143.0.7499.109

A full list of changes from the previous release (version 143.0.7499.52.0) is available through the Git commit log between the releases.

This update is available to GrapheneOS users via our app repository and will also be bundled into the next OS release. Vanadium isn't yet officially available for users outside GrapheneOS, although we plan to do that eventually. It won't be able to provide the WebView outside GrapheneOS and will have missing hardening and other features.

GrapheneOS Foundation Responds To Jolla


Jolla has spent years disparaging projects based on the Android Open Source Project (AOSP) for marketing. SailfishOS has a largely closed source user interface and application layer with no equivalent to the open source AOSP. It's far less private and secure than AOSP or iOS too.

Jolla recently launched a new product so their supporters are understandably trying to promote it. As part of that, they've been posting about it in replies to posts about GrapheneOS. We've replied to some of it with our perspective within threads originally about GrapheneOS.

Since we dared to post accurate information in threads about GrapheneOS where they mentioned us in replies to promote it, their forum is being used as a place to attack GrapheneOS including libelous attacks towards our team referencing harassment content:

forum.sailfishos.org/t/sailfis…

Several of their supporters are taking the usual approach of calling us crazy and delusional while referencing harassment content at the same time as calling the factual info we posted aggressive. They're brigading discussions about GrapheneOS with attacks so we made this thread.

Brigading threads about an open source project and attacking the team with libelous claims is toxic. Defending ourselves from it with factual statements is not toxic. Repeating dishonest attacks on our team based on similar attacks over and over doesn't make it any less untrue.

GrapheneOS version 2025121000 released


This is our first non-experimental release based on Android 16 QPR2 after our initial experimental 2025120800 release.

The change to the style of notification backgrounds is an upstream regression rather than an intentional change to a more minimal style. It will be fixed in a subsequent release since we decided it isn't important enough to delay this.

Tags:

  • 2025121000 (Pixel 6, Pixel 6 Pro, Pixel 6a, Pixel 7, Pixel 7 Pro, Pixel 7a, Pixel Tablet, Pixel Fold, Pixel 8, Pixel 8 Pro, Pixel 8a, Pixel 9, Pixel 9 Pro, Pixel 9 Pro XL, Pixel 9 Pro Fold, Pixel 9a, Pixel 10, Pixel 10 Pro, Pixel 10 Pro XL, Pixel 10 Pro Fold, emulator, generic, other targets)

Changes since the 2025120400 release:

  • full 2025-12-05 security patch level
  • rebased onto BP4A.251205.006 Android Open Source Project release (Android 16 QPR2)
  • disable promotion of identity check feature not currently present in GrapheneOS due to depending on privileged Google Mobile Services integration
  • GmsCompatConfig: update to version 166

All of the Android 16 security patches from the current January 2026, February 2026, March 2026, April 2026, May 2026 and June 2026 Android Security Bulletins are included in the 2025121001 security preview release. List of additional fixed CVEs:

  • High: CVE-2025-32348, CVE-2025-48641, CVE-2026-0014, CVE-2026-0015, CVE-2026-0016, CVE-2026-0017, CVE-2026-0018

2025121001 provides at least the full 2026-01-01 Android and Pixel security patch level but will remain marked as providing 2025-12-05.

For detailed information on security preview releases, see our post about it.

1 zo 4 lekárov v USA považuje kryonické uchovanie za trochu alebo veľmi pravdepodobné pre budúce oživenie


Nová štúdia ukazuje, že podstatná časť lekárov v USA verí kryonike, cíti sa komfortne ak si ju ich pacient vyberie a dokonca podporuje legálnosť procedúr, ktoré ju vylepšia.

Celá štúdia, ešte pred revíziou od kolegov a pred tlačou, je dostupná zadarmo 👇
medrxiv.org/content/10.64898/2…

Aký je váš názor na kryoniku? Ak by peniaze neboli problém, dali by ste sa vitrifikovať ("zmraziť") pre oživenie v budúcnosti?

This entry was edited (1 month ago)
in reply to Vlado

To je oprávnená obava! Počas času biostázy ("zmrazenia") nemá človek prehľad o svete, a už vôbec nie kontrolu nad svojou situáciou.

Otázkou je či veríš, že civilizácia v ktorej by rozhodne nestálo za to žiť by si dala tú námahu aby ťa vôbec oživila 🤔 (Post)apokalyptická spoločnosť by na to skoro určite nemala zdroje. Totalitná spoločnosť by oživovaniu ľudí, ktorí by mohli narušiť ich politiku, asi nevenovala veľa pozornosti a v najlepšom prípade by ich nechala odpočívať v pokoji.

Podľa mňa, človek môže rátať s oživením akurát do decentnej spoločnosti, ktorá si váži život. Dôležitejšou otázkou je či vyvinieme technológiu na to oživenie 🤔

in reply to kubofhromoslav

Nie ze by som cakal uplne post-apo ale tak ci tak je podla mna velka sanca, ze by som si tym pohorsil a prebral sa v horsej dobe.

Dalsi problem vidim v tom, ze ten svet proste bude vyzerat inak a moze byt dost zlozite sa s tym vyrovnat. Predpokladam, ze by to mohol byt dost sok. Nehovoriac o tom, ze teraz ma clovek rodinu, znamych, … To po rozmrazeni uz mat nemusi (a keby aj ano, tak tou dobou uz to budu pravdepodobne ini ludia)

Zatial co pozitiva popravde nevidim. Okrem klasickeho “mam nevyliecitelnu chorobu a v buducnosti uz ju snad budu vediet liecit”. Kazdopadne beruc do uvahy vsetko co som spominal - asi by som do toho ani tak nesiel.

This entry was edited (3 weeks ago)
in reply to Vlado

Čo sa týka toho šoku z novej vezie spoločnosti, to je vec, ktorá je konceptuálne už pripravená a je zahrnutá v cene za uchovanie. V zásade je to podobné ako keď sa človek preberie po dlhej kóme, akurát na steroidoch. Očakávame, že bude vytvorených viacero priestorov, ktoré budú imitovať verziu spoločnosti z istého obdobia, napr. 2030-2040. Novo rozmrazený človek tam bude umiestnený aby bol v známom prostredí. Potom bude postupne zoznamovaný s novinkami a bude si na ne privikať - to môže trvať týždne, mesiace alebo občas aj roky. Potom bude premiestnený do prostredia ako z obdobia 2040-2045 atď až kým sa prispôsobí na spoločnosť v danej dobe. Nejaký čas to trvať bude. Očakávam, že veľa ľudí sa postupne privikne. A tí ostatní môžu ostať v danom prostredí a napr pomáhať novo rozmrazeným.

Emil Kendziorra, riaditeľ kryonickej spoločnosti Tomorrow Biostasis, o tom podobne hovoril. Nie som si istý kde, ale asi v tomto rozhovore: youtu.be/pTVwFKvGYeM

in reply to Vlado

Čo sa týka pozitív, tak o kryouchovanie zvyčajne majú záujem ľudia, ktorí majú život veľmi radi a chcú žiť veľmi dlho. Jednou z tých "nevyliečiteľných chorôb" je totiž aj starnutie, ktoré nie len zabíja, ale sťažuje život niekoľko desaťročí. Očakáva sa, že v čase keď budeme vedieť ľudí rozmraziť (veľmi nejasné kedy, ale 2075-2125 je slušný, informovaný odhad) tak budeme vedieť aj podstatne zvrátiť starnutie. Takže človek bude nie len živý, ale aj vitálny.

Je pravda, že dlhodobá vitalita nie je niečo, čo by chceli všetci, ale za mňa je to veľké pozitívum.

Ďalšie Lemmy komunity v slovenčine?


Zdar. Poznáte na Lemmy aj ďalšie komunity v slovenčine? Ja som zatiaľ našiel len všeobecné /c/Slovakia, pričom len táto jediná má nejaký nový zmysluplný obsah. Viem, že je nás tu málo, ale možno máme aj nejakú tematickú komunitu v slovenčine (alebo aspoň budeme mať ;).
in reply to kubofhromoslav

Čau, nuž zo začiatku boli viac menej 2 relatívne aktívne:
* !slovakia@sopuli.xyz
* !slovakia@lemmy.world

Okrem toho sú aj tieto viac menej mŕtve komunity:
* !Slovakia@kbin.social
* !slovakia@lemmy.ml

Tématická komunita je fajn nápad, je to trocha odvážne keďže máme problém ako tak udržať nad vodou tieto naše generické komunity (je nás tu fakt málo) ale veď prečo nie, kým neskúsime nezistíme :)

Ako ja dlho snívam o nejakej čisto slovenskej inštancii - napr. lemmy.sk (čo už niekto kúpil) alebo piefed.sk ktorá by sa sústredila čisto na Slovensko. To by bolo krásne, no len čo som čítal tak že je to relatívne drahé a náročné prevádzkovať takú inštanciu. No a trebalo by ľudí samozrejme. Ale snívať môžem :)

in reply to kubofhromoslav

Uff presné číslo neviem ale za posledné roky už pár inštancií skončilo s tým že proste sa im to neoplatí, tak z toho usudzujem. Hlavne si spomínam na 2 prípady
* ~~lemmy.zip~~ lemm.ee - to bola všeobecná inštancia a relatívne veľká. Oni skončili myslím že pre to že tá správa toho vyžadovala dosť času a už sa tomu nechceli venovať
* diagonlemmy.social - to bola Harry Potter inštancia a pokiaľ viem tak oni skončili pre peniaze, že je to proste príliš špecifická inštancia a nestojí to za to spravovať pre tých pár komunít celú inštanciu. Ale toto ma mrzelo lebo ich som videl ako príklad toho ako by to malo fungovať.

Ale pre porovnanie - veľké inštancie ako lemmy.world uvádzajú že majú výdavky asi 9000 € ročne (keď pozerám na ich výdavky z 2023 a 2024)

opencollective.com/mastodonwor…

Ale zas treba zohľadniť to že to je najväčšia lemmy inštancia na svete a spravujú mimo nej aj Mastodon inštanciu, Piefed inštanciu a bohvie čo ešte. No a že sú v cloude, tam aj malá inštancia vyjde tipujem aspoň na 100 € mesačne. Keď to človek rozbehá na nejakom PC doma pod stolom tak to nebude stáť takmer nič (ehm no mimo elektriny, domény, PC súčastí, ...)

This entry was edited (1 month ago)

Experimental GrapheneOS Release Based On AOSP 16 QPR2 Now Available For Testing


An experimental release of GrapheneOS (2025120800) based on Android 16 QPR2 is available for testing via sideloading. It won't be pushed out via Alpha. You can join our testing chat room if you want to help with testing (grapheneos.org/contact#communi…). No security preview variant yet.

GrapheneOS Based On AOSP 16 QPR2 Releasing Soon


Android 16 QPR2 experimental releases will be available soon. We're dealing with a lot of attacks on the project branching off from the smear campaign in France. We'd appreciate if our community would debunk this nonsense across platforms for us so we can focus on QPR2. Thanks.

If you see the fake story about someone claiming to be charged with premeditated murder because GrapheneOS supposedly didn't protect their data, see nitter.net/GrapheneOS/status/1… for a thorough debunking. Their story keeps changing and clearly isn't real. They may be a career criminal but this is fake.

GmsCompatConfig version 166 released


Changes in version 166:

  • add initial stubs for Android 16 QPR2

A full list of changes from the previous release (version 165) is available through the Git commit log between the releases (only changes to the gmscompat_config text file and config-holder/ directory are part of GmsCompatConfig).

GmsCompatConfig is the text-based configuration for the GrapheneOS sandboxed Google Play compatibility layer. It provides a large portion of the compatibility shims.

This update is available to GrapheneOS users via our app repository and will also be bundled into the next OS release.

in reply to EfreetSK

Nech odpočíva v pokoji, a sústrasť jej rodine a priateľom!

V článku nespomínajú príčinu úmrtia, ale očakávam, že je to následkom starnutia. Je to tým smutnejšie, že vedci už vyvíjajú lieky na ozajstné zvrátenie starnutia. Ak by vydržala ešte cca 15-20 rokov (pri jej veku a súčasnom stave medicíny by to bolo ťažké), mohla by žiť ozaj veľmi dlho. Koľko vecí by ešte mohla napísať 😥

GrapheneOS version 2025120400 released


Tags:

  • 2025120400 (Pixel 6, Pixel 6 Pro, Pixel 6a, Pixel 7, Pixel 7 Pro, Pixel 7a, Pixel Tablet, Pixel Fold, Pixel 8, Pixel 8 Pro, Pixel 8a, Pixel 9, Pixel 9 Pro, Pixel 9 Pro XL, Pixel 9 Pro Fold, Pixel 9a, Pixel 10, Pixel 10 Pro, Pixel 10 Pro XL, Pixel 10 Pro Fold, emulator, generic, other targets)

Changes since the 2025111800 release:

  • full 2025-12-01 security patch level (has already been fully provided by our security preview releases for at least a month and most of the patches since September)
  • add experimental support for the Pixel 10, Pixel 10 Pro, Pixel 10 Pro XL and Pixel 10 Pro Fold (there were 2 standalone experimental releases prior to this via 2025112500 and 2025113000 along with corresponding security preview releases for each)
  • Cell Broadcast Receiver: switch back to our modified text for the presidential alerts toggle
  • kernel (6.1): update to latest GKI LTS branch revision including update to 6.1.158
  • kernel (6.6): update to latest GKI LTS branch revision including update to 6.6.116
  • kernel (6.12): update to latest GKI LTS branch revision including update to 6.12.60
  • Auditor: update to version 90
  • Vanadium: update to version 143.0.7499.34.0
  • Vanadium: update to version 143.0.7499.34.1
  • Vanadium: update to version 143.0.7499.34.2
  • GmsCompatConfig: update to version 164
  • GmsCompatConfig: update to version 165

All of the Android 16 security patches from the current January 2026, February 2026 and March 2026 Android Security Bulletins are included in the 2025120401 security preview release. List of additional fixed CVEs:

  • Critical: CVE-2025-48631, CVE-2026-0006
  • High: CVE-2022-25836, CVE-2022-25837, CVE-2023-40130, CVE-2025-22420, CVE-2025-22432, CVE-2025-26447, CVE-2025-32319, CVE-2025-32348, CVE-2025-48525, CVE-2025-48536, CVE-2025-48555, CVE-2025-48564, CVE-2025-48565, CVE-2025-48566, CVE-2025-48567, CVE-2025-48572, CVE-2025-48573, CVE-2025-48574, CVE-2025-48575, CVE-2025-48576, CVE-2025-48577, CVE-2025-48578, CVE-2025-48579, CVE-2025-48580, CVE-2025-48582, CVE-2025-48583, CVE-2025-48584, CVE-2025-48585, CVE-2025-48586, CVE-2025-48587, CVE-2025-48589, CVE-2025-48590, CVE-2025-48592, CVE-2025-48594, CVE-2025-48596, CVE-2025-48597, CVE-2025-48598, CVE-2025-48600, CVE-2025-48601, CVE-2025-48602, CVE-2025-48603, CVE-2025-48604, CVE-2025-48605, CVE-2025-48609, CVE-2025-48612, CVE-2025-48614, CVE-2025-48615, CVE-2025-48616, CVE-2025-48617, CVE-2025-48618, CVE-2025-48619, CVE-2025-48620, CVE-2025-48621, CVE-2025-48622, CVE-2025-48626, CVE-2025-48628, CVE-2025-48629, CVE-2025-48630, CVE-2025-48632, CVE-2025-48633, CVE-2025-48634, CVE-2026-0005, CVE-2026-0007, CVE-2026-0008

For detailed information on security preview releases, see our post about it.

Vanadium version 143.0.7499.52.0 released


Changes in version 143.0.7499.52.0:

  • update to Chromium 143.0.7499.52

A full list of changes from the previous release (version 143.0.7499.34.2) is available through the Git commit log between the releases.

This update is available to GrapheneOS users via our app repository and will also be bundled into the next OS release. Vanadium isn't yet officially available for users outside GrapheneOS, although we plan to do that eventually. It won't be able to provide the WebView outside GrapheneOS and will have missing hardening and other features.

Vanadium version 143.0.7499.34.2 released


Changes in version 143.0.7499.34.2:

  • avoid always open external links in Incognito mode causing bookmarks to always open in it
  • enable autofill configuration screens regardless of autofill settings
  • remove unused Google autofill status
  • enable Drumbrake WebAssembly interpreter for x86_64 builds used in the emulator too

A full list of changes from the previous release (version 143.0.7499.34.1) is available through the Git commit log between the releases.

This update is available to GrapheneOS users via our app repository and will also be bundled into the next OS release. Vanadium isn't yet officially available for users outside GrapheneOS, although we plan to do that eventually. It won't be able to provide the WebView outside GrapheneOS and will have missing hardening and other features.

GrapheneOS Foundation Suggests Improvements For Early Security Patch Previews


Our security preview releases have provided the December 2025 security patches for the Android Open Source Project since September 2025. December 2025 security patches are now public and being integrated into our regular releases while our security previews have up to March 2026.

A bunch of the patches previously scheduled for December 2025 were made optional and deferred to future months so they're not listed in the public bulletin. That's why even our September 2025 security preview releases list CVEs which are still not public in December 2025.

The reason patches get deferred is because OEMs aren't capable of quickly integrating, testing and shipping patches. When issues are identified including an OEM having trouble with it, they'll often defer it to a future month. Our security previews can continue shipping these.

GrapheneOS is the only Android-based OS providing the full security preview patches. Samsung ships a small subset of their flagship devices. Pixel stock OS gets a portion of it early but we aren't sure exactly how much since they don't follow their guidelines for listing patches.

Providing our security preview patches is a lot of work for us. It requires a full time developer spending a significant fraction of their time on it. It's hard to understand why large companies can't keep up with these patches but what matters is that we can provide them early.

Android security preview patches are currently backports to Android 13, 14, 15 and 16. Since GrapheneOS is based on Android 16 QPR1, we need to forward port the patches from 16 to 16 QPR1. Our understanding is they're going to start backporting to some quarterly releases too.

Android 16 QPR2 appears to be the first quarterly release of Android which is going to be shipped by non-Pixel devices. If that's the case, they'll need to start providing security preview patches backported to it too. It's not clear if it will happen for every quarterly release.

Spending a significant amount of time on this is part of the reason GrapheneOS feature development has slowed down. Expanding our servers and now migrating away from OVH is another. We'll be hiring more people and improving our organization structure to get things moving better.

We would greatly prefer it if patches were disclosed to OEMs 1 week ahead instead of 2-4 months ahead so our security preview releases would only need to exist for a week and regular releases would get the patches much faster. OEMs should just hire far more people and do better.

Vanadium version 143.0.7499.34.1 released


Changes in version 143.0.7499.34.1:

  • fix regression for setting opening external links in Incognito mode
  • disable search engine compose plate feature to avoid a UI feature exclusive to Google search promoting AI mode

A full list of changes from the previous release (version 143.0.7499.34.0) is available through the Git commit log between the releases.

This update is available to GrapheneOS users via our app repository and will also be bundled into the next OS release. Vanadium isn't yet officially available for users outside GrapheneOS, although we plan to do that eventually. It won't be able to provide the WebView outside GrapheneOS and will have missing hardening and other features.

GrapheneOS Experimental Releases For Pixel 10 Devices Now Available


We now have experimental support for the Pixel 10, Pixel 10 Pro, Pixel 10 Pro XL and Pixel 10 Pro Fold.

Our initial 2025112500 release for these is available through our web installer or releases page on our staging site:

staging.grapheneos.org/install…staging.grapheneos.org/release…

GrapheneOS Foundation Explains Why GrapheneOS Has Left France


A false narrative is being pushed about GrapheneOS claiming we're ending operations in France due to the actions of 2 newspapers. That's completely wrong. If both newspapers and the overall French media had taken our side instead of extreme bias against us, we'd still be leaving.

We're ending operations in France and ending our use of French companies (mainly OVH) to provide services because of direct quotes by law enforcement in dozens of French news publications. Their inaccurate claims about GrapheneOS and thinly veiled threats were our sign to leave.

French law enforcement hijacked the servers of companies selling secure phones multiple times and is comparing us with those companies. They've made it clear they expect access to phones and will go after us if we do not cooperate. Cooperating with that means adding a backdoor.

We were already moving away from OVH over time. We didn't have authoritative DNS or update mirrors on it anymore prior to this. We were only going to be using it for our website/network service instances which are tiny servers with only static content and reverse proxies.

We couldn't see any of the specific claims from French law enforcement until the news stories were published. French law enforcement are wrongly conflating GrapheneOS with products using portions of our code. Claims about our features, distribution and marketing are inaccurate.

French law enforcement brought up SkyECC and Encrochat, two companies they went after with arrests and server seizures. They made it very clear they'll go after us similarly if they're able to conjure a good enough justification and we don't cooperate by providing device access.

Thinly veiled threats from law enforcement are quoted in several of the news article including archive.is/UrlvK. We don't store user data and cannot bypass brute force protection for encryption. Cooperating to provide device access means one thing: encryption backdoors.

in reply to KindnessInfinity

They’ve made it clear [they expect access to phones and ...]


How did they make it clear? Can you provide the full quote or reference to the message?

Thinly veiled threats from law enforcement are quoted in several of the news article


Which ones exactly? Unfortunately I don't speak French, but here's what I get with a translator on the reference link:

With this new tool, for some users there is a genuine legitimacy in wanting to protect their communications. The approach is therefore different. But this will not stop us from prosecuting the developers if links are found between them and a criminal organization and they do not cooperate with justice.


Is it a thinly veiled threat, or it could be something else as well, such as simply news coverage and a warning? They clearly acknowledge that "some users ~have a genuine legitimacy in wanting to protect their communications".

I mean I get it if you want to leave France due to *fears*. If and only if you say you're afraid, not that you know for a fact about "thinly veiled threats", "they make it clear", "no open-source privacy project can exist in France" etc. Or if you do know some of it as a fact, then provide proofs, not "we have information that......".

This entry was edited (1 month ago)

Social and Organizational Talks at FOSDEM 2026


Hey, all. One thing that's different this year about the Social Web Devroom at FOSDEM 2026 is that we're going to include talks about the organizational and social aspects of rolling out Open Source Fediverse software for individuals and communities. Last

Hey, all. One thing that’s different this year about the Social Web Devroom at FOSDEM 2026 is that we’re going to include talks about the organizational and social aspects of rolling out Open Source Fediverse software for individuals and communities. Last year, we focused pretty heavily on technical talks from the principle developers of FLOSS packages. This year, we want to make sure the other aspects of Fediverse growth and improvement are covered, too.

Consequently, the guidance for last year’s event, which was focused on how to make a great technical presentation, might seem a little outdated. But on reviewing it, I’ve found that it still has good advice for social and organizational talks. Just like software developers, community builders see problems and construct solutions for them. The solutions aren’t just about writing code, though; more often they involve bringing people together, assembling off-the-shelf tools, and making processes and rules for interaction.

Talks about Open Source software to implement ActivityPub and build the social web are still welcome, of course. We’re just expanding a bit to cover the human aspects of the Fediverse as well.

I’m looking forward to having the interesting discussions about bringing people together to make the Social Web. If you haven’t already, please consider submitting a talk to pretalx.fosdem.org/fosdem-2026…. Select “Social Web” from the “Track” dropdown, and include the length of your talk (8/25/50) in the submission notes. The deadline is December 1, 2025, so get them in as soon as possible!

This entry was edited (1 month ago)