fosstodon.org is one of the many independent Mastodon servers you can use to participate in the fediverse.
Fosstodon is an invite only Mastodon instance that is open to those who are interested in technology; particularly free & open source software. If you wish to join, contact us for an invite.

Administered by:

Server stats:

11K
active users

#GrapheneOS

77 posts62 participants3 posts today

Secure PDF Viewer app version 26 released

lemmy.ml/post/26423925

lemmy.mlSecure PDF Viewer app version 26 released - LemmyNotable changes in version 26: - prevent trying to open document properties before they’re loaded to avoid a rare crash A full list of changes from the previous release (version 25) is available through the Git commit log between the releases [https://github.com/GrapheneOS/PdfViewer/compare/25...26]. Simple Android PDF viewer based on pdf.js and content providers. The app doesn’t require any permissions. The PDF stream is fed into the sandboxed WebView without giving it access to content or files. Content Security Policy is used to enforce that the JavaScript and styling properties within the WebView are entirely static content from the apk assets. It reuses the hardened Chromium rendering stack while only exposing a tiny subset of the attack surface compared to actual web content. The PDF rendering code itself is memory safe with dynamic code evaluation disabled, and even if an attacker did gain code execution by exploiting the underlying web rendering engine, they’re within the Chromium renderer sandbox with no access to the network (unlike a browser), files, or other content. This app is available through the Play Store with the app.grapheneos.pdfviewer.play app id [https://play.google.com/store/apps/details?id=app.grapheneos.pdfviewer.play]. Play Store releases go through review and it usually takes around 1 to 3 days before the Play Store pushes out the update to users. Play Store releases use Play Signing, so we use a separate app id from the releases we publish ourselves to avoid conflicts and to distinguish between them. Each release is initially pushed out through the Beta channel followed by the Stable channel. Releases of the app signed by GrapheneOS with the app.grapheneos.pdfviewer id are published in the GrapheneOS App Store [https://github.com/GrapheneOS/AppStore/releases] which provides fully automatic updates. Each release is initially pushed out through the Alpha channel, followed by the Beta channel and then finally the Stable channel. These releases are also bundled as part of GrapheneOS and published on GitHub. GrapheneOS users must obtain GrapheneOS app updates through our App Store since verified boot metadata is required for out-of-band system app updates on GrapheneOS as part of extending verified boot to them.

GrapheneOS Camera app version 81 released

lemmy.ml/post/26423872

lemmy.mlGrapheneOS Camera app version 81 released - LemmyNotable changes in version 81: - avoid video recording crash on a small subset of low-end devices caused by the OS wrapping the capture button drawable inside of another type we didn’t request which leads to an invalid cast exception when animating it to start video recording A full list of changes from the previous release (version 80) is available through the Git commit log between the releases [https://github.com/GrapheneOS/Camera/compare/80...81]. This app is available through the Play Store with the app.grapheneos.camera.play app id [https://play.google.com/store/apps/details?id=app.grapheneos.camera.play]. Play Store releases go through review and it usually takes around 1 to 3 days before the Play Store pushes out the update to users. Play Store releases use Play Signing, so we use a separate app id from the releases we publish ourselves to avoid conflicts and to distinguish between them. Each release is initially pushed out through the Beta channel followed by the Stable channel. Releases of the app signed by GrapheneOS with the app.grapheneos.camera app id are published in the GrapheneOS App Store [https://github.com/GrapheneOS/AppStore/releases] which provides fully automatic updates. Each release is initially pushed out through the Alpha channel, followed by the Beta channel and then finally the Stable channel. These releases are also bundled as part of GrapheneOS and published on GitHub. GrapheneOS users must obtain GrapheneOS app updates through our App Store since verified boot metadata is required for out-of-band system app updates on GrapheneOS as part of extending verified boot to them.

Secure PDF Viewer app version 25 released

lemmy.ml/post/26402507

lemmy.mlSecure PDF Viewer app version 25 released - LemmyNotable changes in version 24: - avoid reading the entire file into memory for “Save as” - handle edge case errors for opening and saving files mainly caused by bugs in the OS or the apps sending/receiving files - avoid a redundant cycle of opening and closing of the file before loading it - improve error message text for errors encountered while opening or saving a file - update JavaScript development dependencies - set WebView layout algorithm to the NORMAL mode since the default NARROW_COLUMNS is deprecated - minor improvements to code quality and efficiency A full list of changes from the previous release (version 23) is available through the Git commit log between the releases [https://github.com/GrapheneOS/PdfViewer/compare/23...24]. Simple Android PDF viewer based on pdf.js and content providers. The app doesn’t require any permissions. The PDF stream is fed into the sandboxed WebView without giving it access to content or files. Content Security Policy is used to enforce that the JavaScript and styling properties within the WebView are entirely static content from the apk assets. It reuses the hardened Chromium rendering stack while only exposing a tiny subset of the attack surface compared to actual web content. The PDF rendering code itself is memory safe with dynamic code evaluation disabled, and even if an attacker did gain code execution by exploiting the underlying web rendering engine, they’re within the Chromium renderer sandbox with no access to the network (unlike a browser), files, or other content. This app is available through the Play Store with the app.grapheneos.pdfviewer.play app id [https://play.google.com/store/apps/details?id=app.grapheneos.pdfviewer.play]. Play Store releases go through review and it usually takes around 1 to 3 days before the Play Store pushes out the update to users. Play Store releases use Play Signing, so we use a separate app id from the releases we publish ourselves to avoid conflicts and to distinguish between them. Each release is initially pushed out through the Beta channel followed by the Stable channel. Releases of the app signed by GrapheneOS with the app.grapheneos.pdfviewer id are published in the GrapheneOS App Store [https://github.com/GrapheneOS/AppStore/releases] which provides fully automatic updates. Each release is initially pushed out through the Alpha channel, followed by the Beta channel and then finally the Stable channel. These releases are also bundled as part of GrapheneOS and published on GitHub. GrapheneOS users must obtain GrapheneOS app updates through our App Store since verified boot metadata is required for out-of-band system app updates on GrapheneOS as part of extending verified boot to them.

Secure PDF Viewer app version 24 released

lemmy.ml/post/26402428

lemmy.mlSecure PDF Viewer app version 24 released - LemmyNotable changes in version 24: - avoid reading the entire file into memory for “Save as” - handle edge case errors for opening and saving files mainly caused by bugs in the OS or the apps sending/receiving files - avoid a redundant cycle of opening and closing of the file before loading it - improve error message text for errors encountered while opening or saving a file - update JavaScript development dependencies - set WebView layout algorithm to the NORMAL mode since the default NARROW_COLUMNS is deprecated - minor improvements to code quality and efficiency A full list of changes from the previous release (version 23) is available through the Git commit log between the releases [https://github.com/GrapheneOS/PdfViewer/compare/23...24]. Simple Android PDF viewer based on pdf.js and content providers. The app doesn’t require any permissions. The PDF stream is fed into the sandboxed WebView without giving it access to content or files. Content Security Policy is used to enforce that the JavaScript and styling properties within the WebView are entirely static content from the apk assets. It reuses the hardened Chromium rendering stack while only exposing a tiny subset of the attack surface compared to actual web content. The PDF rendering code itself is memory safe with dynamic code evaluation disabled, and even if an attacker did gain code execution by exploiting the underlying web rendering engine, they’re within the Chromium renderer sandbox with no access to the network (unlike a browser), files, or other content. This app is available through the Play Store with the app.grapheneos.pdfviewer.play app id [https://play.google.com/store/apps/details?id=app.grapheneos.pdfviewer.play]. Play Store releases go through review and it usually takes around 1 to 3 days before the Play Store pushes out the update to users. Play Store releases use Play Signing, so we use a separate app id from the releases we publish ourselves to avoid conflicts and to distinguish between them. Each release is initially pushed out through the Beta channel followed by the Stable channel. Releases of the app signed by GrapheneOS with the app.grapheneos.pdfviewer id are published in the GrapheneOS App Store [https://github.com/GrapheneOS/AppStore/releases] which provides fully automatic updates. Each release is initially pushed out through the Alpha channel, followed by the Beta channel and then finally the Stable channel. These releases are also bundled as part of GrapheneOS and published on GitHub. GrapheneOS users must obtain GrapheneOS app updates through our App Store since verified boot metadata is required for out-of-band system app updates on GrapheneOS as part of extending verified boot to them.
Abstract Subjectivism!

2025 年 2 月 22 日、午前 9:44

In the philosophy of art, subjectivism is the belief that art should capture and reflect the subjective experience of both the artist and the viewer, turning the work of art into a mirror. "Abstract Subjectivism" is a photographic art form that begins with traditional photography, using an image as its foundation. Through intensive editing, the photo is transformed into abstract, geometrically asymmetric forms that reflect the artist's emotional and psychological state. Intended as a healing mechanism, the artist expresses perceived flaws and inner conflicts through seemingly chaotic subjects called "errors," turning these imperfections into meaningful experiences. This process mirrors artistic subjectivism, creating catharsis by transferring the value of imperfection into the qualities that produce a work of art.


曼農可

I am not a monster. I support the freedom to live and enjoy the possibilities of existence.

I belong to a diverse community of free individuals who tolerate each other through mutual influence inspiring one another on a humane level through mutual identification without ever losing our own independence.

No nationalism, no violence, no war.


#art #mastodonart #pixelfedart #fediverseart #architecture #photography #mirroring #abstractsubjectivism #subjectivism #abstractart #abstractphotography #originalart #abstractsubject #symmetry #error #chaos #geometricalasymmetry #beauty #catharsis #productivity #westernphilosophy #japaneseaestheticsensibility #harmony #wabisabi #mononoaware #ma #turning #geometry #freedom #graphicart #illustration #symmetry #geometricart #geometry #snapseed #android #grapheneos #mobileart #photographicart #healing #mathematical #proportional #design
Replied in thread

@twelvety I ditched my iPhone SE for a Pixel 8 with #grapheneos with b/w launcher without icons and that calmed down some very obnoxious parts already.

Eink devices, it depends. Have Boox ones for 2 years and once set up, reading, handwriting/sketching and RSS feeds and such work well and make it a dedicated reading device.

Not sure yet whether and how the Supernote can replace it