cross-posted from: https://leminal.space/post/40562232

From Fluxer's updated roadmap on their website

See the polyproto website they linked here

I hadn't heard of this protocol before, but the possibility of transferring accounts between homeservers sounds exciting!

Here's the text from the screenshot:

Federation lets people on different instances talk to each other as if they were on the same service, the way email works across providers. Fluxer's federation will be based on polyproto-core, a specification from the polyproto project, with our own extensions on top. polyproto is still young, and we hope that building a real implementation of it, and sharing what we learn, helps the specification mature and benefits everyone else who builds on it.

polyproto-core describes an identity that works across servers. Your identity is anchored on your home server and looks like name@domain. Behind it is a certificate that your home server signs over a key created on your device. To prove who you are to another server, your device signs a challenge from that server, so one identity works across servers and you don't need a separate account on each. Messages are signed by the sender, so a server you visit can't forge messages from you without being detected, as long as your home server and your device haven't been compromised. The specification also defines how to move to a new home server.

polyproto-core is an early beta specification maintained by the Polyphony project. As of October 2026 it is at v1.0-beta.13. It focuses on identity and leaves message formats and chat features to extensions. We'll write our own extensions for Fluxer's features and propose changes to the protocol where they would help others too.

We'll publish an experimental draft pull request in 2026 that you can try and give feedback on. The stable release follows in 2027. Until the draft is up, the discussion happens in Fluxer Labs, and you're welcome to join in.

You can already sign in to several instances from one app. You sign in to each instance separately and switch between them. The mobile apps already support several instances and accounts, and the desktop app gets the same in early October 2026 with the update described in #2.

Hi! I’m a table tennis player, club captain and referee who apparently decided that what the world desperately needed was another tournament manager.

So I made LibreTT. 🏓

It’s a desktop app for running table tennis tournaments: players, registrations, fees, groups, draws, matches, knockout brackets, results, backups and exports. It runs on Linux, Windows and macOS, works offline and requires no account.

So why another one?

Because I don’t think competition data should belong to the software that records it.

A result is created by players, clubs, referees and organizers. The software is just a tool. If LibreTT disappears tomorrow, your tournament history shouldn’t disappear with it.

That’s why LibreTT is licensed under AGPL-3.0-or-later. No subscriptions, activation servers, paid feature tiers or vendor lock-in. The source is public, the data stays local, and the community should always be able to preserve, move and continue its own infrastructure.

This is the first public beta (0.1.0-beta.1), so the next milestone is testing it against its natural predator: an actual tournament organizer who is 15 minutes behind schedule.

Development is AI-assisted and I disclose that in the README. I review and test what goes into the project and take responsibility for it.

Feedback, criticism and contributions are very welcome.

Source code · Website

Disclaimer: LibreTT website is still in development, expect bugs

I've been working on reverse-engineering Grindr and creating an open source client implementation for it since March.

When GrindrPlus closed, my project turned out to be its de-facto successor and immediatelly several thousands of people started following it. Now it has 70k+ downloads on Forgejo and the authorship is dedicated to public domain :)

• MIT licensed, no ads, no analytics, no trackers, no diagnostics, no statistics, no telemetry, only opt-in updates checking
• Signed releases, reproducible builds on all four platforms, full transparency
• And it's now in Google Play (for the time being) and being reviewed for F-Droid!

Already applied for Apple developer enrollment and going to publish this to EU alt stores as well as in the TestFlight. Then a classic unsigned ipa and also going to attempt Apple AppStore just for completeness.

You need an existing Grindr account. Downloads: https://opengrind.org/download

Questions and criticism welcome.

I have been noticing an increasing amount of apps on droidify, that are not supposed to have trackers, obtain trackers after being updated. I dont know if its amongst the developers themselves or Google's forced pushed on getting apps approved through their store, but it should be put in the description of these apps before they are downloaded that trackers have been added.

For example, these are some apps that are NOT supposed to have trackers, in fact do have trackers:

Or

Some of these apps, my phone dosent pick up that it contains trackers unless i look at Tracker Control

1. Blorp (Lemmy)
2. FossWallet (this one just happened, this wallet NEVER had trackers until a recent update)
3. All of the browser apps on drodify (even the private ones) - the only one that admits to have anti-privacy features is Tor.
4. Rush (Music Lyrics App) (description has been updated to show it has trackers) i dont understand why a music lyrics app has trackers on it
5. PipePipe (viewed on tracker control)
6. Tuta(viewed on tracker control)
7. Droidify (yes, droidify itself contains trackers)
8. AntennaPod(viewed on tracker control)

I'm not an Android developer, but I plan to learn this along with the Kotlin language. The Android Studio seems to have proprietary components and therefore marked as non-FOSS on Flathub store. The Android SDK specifically (at least builds provided by Google) is also seems to be licensed under non-FOSS license.

Android Studio is a powerful IDE with rich toolbox for Android development, but it feels like strong lock-in on closed technology even in case we have Android as a FOSS platform in face of AOSP.

I'm just curious to learn, is Android development can be setup to be 100% FOSS? What environment, toolchain, and editors like IntelliJ IDEA CE/VSCodium/Neovim we can possibly use to achieve this?

After 5 years, Minecraft: Java Edition (version 26.3+) can finally run out-of-the-box on the Rockchip RK3588 ARM SoC using a fully open-source graphics pipeline!

My setup:

• Operating system: Vanilla OS 3 Reunion (Linux kernel 7.1)
• Drivers: Mesa PanVK (Vulkan 1.4)

Hey everyone!

I’d like to introduce TypeType, because I don’t think many people here have seen it yet.

TypeType is an open-source, self-hostable video app for YouTube, NicoNico and BiliBili. You run one private instance, then use it from the web app or from the native Android client. Your accounts, subscriptions, history, playlists, favorites, watch progress and settings stay on the instance you control, instead of living only inside the platforms.

IF YOU DONT WANT TO READ ALL THE POST (and that's alright no worries), HERE IS A TLDR !

TL;DR: TypeType is an open-source, self-hostable video app for YouTube, NicoNico and BiliBili, with a web app and a native Android client. It’s built on PipePipeExtractor with its own MSE/SABR playback engine. You can import and export your data with a dozen other apps, no lock-in. 1.9.0 is out, focused on playback reliability. Contributions are welcome, in code, translations or testing.

Source code: https://github.com/TypeType-Video/TypeType

Some background, because TypeType didn’t come out of nowhere

If you’ve been around open-source YouTube tooling for a while, you probably know the family tree. NewPipe is the libre Android streaming front-end, and NewPipeExtractor is the library that does the extraction behind it. PipePipe is a hard fork of NewPipe started in early 2022, and it also handles other services, including NicoNico and BiliBili, with its own extractor, PipePipeExtractor.

Then there’s the self-hosted side. Piped and Invidious are the two big alternative frontends, both AGPL, one built around Vue with its own backend, the other written in Crystal. LibreTube is an Android client that supports YouTube content, and it can use Piped for optional account sync. Those projects are the ones that showed a lot of people that running your own YouTube frontend was even possible.

Before TypeType, I had spent years around PipePipe, and that’s really where the project comes from.

The SABR part

My main work this year was on SABR, the protocol YouTube moved to after cutting the older methods used to fetch streams. I started with a proof of concept, the support landed in PipePipeExtractor, and then came the harder parts: live streams, cold start, session recovery, memory growth from segment buffers. I also maintain the PipePipe wiki and wrote the SABR guide there: https://priveetee.github.io/Docs-PipePipe/developer-guide/introduction.html

That work is really why TypeType exists in its current form. Once the extraction and the session logic are yours, you can build an app that owns the entire chain, instead of relying on someone else’s frontend.

What TypeType is in practice

On the web side you get multi-service search, personal libraries, downloads, comments, subtitles, SponsorBlock, administration, and SABR playback in the browser. The Android client adds background audio, Picture in Picture, audio-only playback, native playback controls and notifications, and it works from Android 6.0 without Google Play Services. The web app and the Android app share the same account and the same library, because they talk to the same instance.

One thing I’m quietly proud of is the portability. It works in both directions. You can import and export across TypeType, PipePipe, NewPipe, Invidious, Piped, LibreTube, ViewTube, Materialious, youtube-local, Flow, SkyTube, Grayjay, YouTube Takeout and even OPML, and that covers subscriptions, history, playlists, favorites, watch progress, settings and more.

And to be clear, there’s no competition here. I genuinely don’t care if you leave and use something else. The point is that your data is yours, so you can come from another project without starting over, and leave with it too if you want.

How it works

TypeType is several services rather than one big blob.

The core is a Kotlin/Ktor server. It wraps PipePipeExtractor for the extraction side: streams, manifests, search, suggestions, trending, comments and channels. It also owns the user data, accounts, subscriptions, playlists, favorites, progress, imports and administration, stored in PostgreSQL with Dragonfly as cache.

Next to it, a TypeScript token service handles the YouTube specifics: visitor data, BotGuard challenges, Proof-of-Origin tokens, player signature decoding, and the WEB and MWEB SABR session metadata. Player decoding stays on our own service path, we don’t rely on third-party decoder endpoints.

For downloads, there’s a separate Go service. It takes jobs from the server, downloads the selected streams with concurrent HTTP Range requests or SABR segments, and muxes audio and video without re-encoding, then publishes the artifact to local or S3-compatible storage. No yt-dlp wrapper under the hood.

On the client side, a React and TypeScript web app handles the interface and the library, and playback goes through our own MSE engine, TypeType-Player. It’s written in TypeScript, has no runtime dependencies, and is published on npm and JSR as @typetype/mse.

So the chain is: client asks the server, the server extracts through PipePipeExtractor, the token service supplies what YouTube requires, and the player turns the resulting session into audio and video.

What we built on top

The extraction engine does the hard part, and I credit it every time, because TypeType would not exist without it. But the project is a lot more than a wrapper now: SABR playback sessions with recovery and bounded buffers, opaque media handles, a custom MSE engine, multi-service search, personal libraries, RSS feeds, profiles, notification delivery, downloads and muxing, portability across a dozen apps, OIDC and instance administration.

Around it there are separate repositories: the React web client, the MSE/SABR playback engine, the Go downloader, and the token service. Licenses vary per component: the server is GPLv3 because of the PipePipeExtractor integration, the downloader is GPL-3.0-or-later, and the rest is MIT.

1.9.0 is out

Most of this release is about making playback more dependable rather than adding new screens. YouTube web playback is now SABR-only, and recoverable live requests stay inside the active playback session instead of leaving playback stuck. There’s also work on Takeout imports, subscription groups on desktop, and the self-hosting documentation.

Honestly, the part I’m the most proud of is that this is not a one-person project anymore. Several people sent PRs for this release, on subscription groups, playback and character encoding. That’s still new to me and it makes me really happy :)

And the community around TypeType is something I did not expect. There are amazing people who test builds, report bugs with real details, help with translations, answer each other, and just hang around. It’s warm, it’s genuinely helpful, and I will never thank them enough.

We also published an AI transparency statement, explaining how AI is used in the project and what we expect from contributions: https://github.com/TypeType-Video/TypeType/blob/dev/AI_TRANSPARENCY.md

Links:

Source code: https://github.com/TypeType-Video/TypeType

1.9.0 release notes: https://github.com/TypeType-Video/TypeType/releases/tag/v1.9.0

Android client: https://github.com/TypeType-Video/TypeType-Android

Playback engine: https://github.com/TypeType-Video/TypeType-Player

Self-hosting docs: https://typetype-video.github.io/Docs-TypeType/self-hosting/introduction

Extractor: https://github.com/InfinityLoop1308/PipePipeExtractor

Contributions are welcome, whatever part of the stack interests you: Kotlin/Ktor on the server, the React web client, the TypeScript playback engine, the Go downloader, or the Android app.

And you don’t even need to write code. Translations are handled on Weblate, so if you want to help translate TypeType into your language, you can do it right there: https://translate.typetype.video/engage/typetype/

If you want to follow the project, there’s also a community here on Lemmy: https://lemmy.zip/c/TypeType

Thanks for reading :)

The Document Foundation announced today the general availability of LibreOffice 26.8.1 as the first maintenance update to the latest and greatest LibreOffice 26.8 office suite series with compatibility and text import improvements.

Coming a little over a month after LibreOffice 26.8, the LibreOffice 26.8.1 update is packed with bug fixes for various issues, crashes, and other annoyances reported by users, as well as more reliable import of text and CSV files with various character encodings, including UTF-16, ISO Latin 1, Chinese, and Japanese.

LibreOffice 26.8.1 also improves compatibility with DOCX, XLSX, and PPTX files, and brings various other changes across most of LibreOffice’s core components, including Writer, Calc, Math, Draw, and others. In numbers, the LibreOffice 26.8.1 point release addresses a total of 40 bugs.

Details about these bug fixes can be found in the changelog for our tech-savvy readers. Meanwhile, you can download LibreOffice 26.8.1 from the official website as binaries for DEB and RPM-based GNU/Linux distributions, or as a source tarball if you’re a system integrator or want to install LibreOffice from sources.

LibreOffice 26.8 was released on August 26th, 2026, with new features like Paragraph Composer in Writer as a text layout algorithm that balances word spacing across consecutive lines, support for OpenType font variations, and the ability to detect paragraph direction automatically when documents or plain text are opened or pasted.

It also made the style list consistent across the Notebookbar, the Formatting toolbar, and the sidebar, added support for VeraPDF during automated testing when validating PDF output, updated the Quick Find sidebar to allow searching through comments, and implemented a Draft view to hide headers, footers, and margins.

The LibreOffice 26.8 office suite series will be supported with seven maintenance updates until June 13th, 2027. The next point release, LibreOffice 26.8.2, is planned for the end of October. Meanwhile, The Document Foundation recommends that all LibreOffice 26.8 users update to LibreOffice 26.8.1 as soon as possible.

As a major disappointment to the open-source community, Siemens has decided to end -- and close-up access -- to the OpenRadioss project as the open-source version opened up by Altair Engineering under the GNU AGPL License back in 2022. This was an open-source version of the industry-leading finite element solver that Altair developed. Siemens acquired Altair Engineering last year and have now completely shut the door on OpenRadioss.

Originally from Altair, Radioss has been an industry-leading solver for analyzing crashes, blasts, and other purposes. Altair creating OpenRadioss was a huge milestone for the technical computing industry. It also had other effects like for myself in finally being able to benchmark with this (Open)Radioss code for CPU performance testing compared to the expensive licensing on Radioss itself.

To much disappointment, I find out today they have completely closed down OpenRadioss. The Siemens.com page now explains of OpenRadioss:

"OpenRadioss is transitioning to a new phase. Visitors looking for crash and impact simulation solutions can now explore Simcenter Radioss and the Radioss R&D program through Siemens. These offerings provide pathways for both production engineering and advanced research activities.
...
The OpenRadioss website is being retired and visitors are being redirected to this transition page. If you are looking for simulation software, technical information or opportunities to engage with future development activities, Siemens provides resources and programs to support those needs."

Even worse, it's just not the OpenRadioss website being "retired" a.k.a. shutdown but they closed up their GitHub repository too. OpenRadioss on GitHub is now a 404. It would be one thing just to archive it and at least keep the open-source code readily available, but instead it's been removed.

OpenRadioss 404

Siemens argues the OpenRadioss closure as for consolidating efforts:

"After four years of successful community-driven research, Siemens is entering a new chapter for the Radioss solver. To accelerate innovation and provide the robust support our global users require for production-grade simulation, we are consolidating our efforts."

Very disappointing to see from such a very promising technical computing project these past few years that was also very useful for real-world performance benchmarking purposes as my main interest in the project. At least for now I'll continue with OpenRadioss benchmarking using archived local binaries for there not being any other superior free or open-source solution available. A major disappointment out of Siemens.

Welcome to Bogdan Buzea 🇷🇴

https://blog.documentfoundation.org/blog/2026/09/29/welcome-bogdan-buzea-new-libreoffice-qa-analyst/

Since 2010, F-Droid has been the go-to place for downloading free and open source apps for Android. Its client app is the one people interact with the most, and it has received many upgrades over the years.

But now it's time for a massive rewrite that has emerged from more than a year of development and numerous test releases.

A comprehensive redesign

Kotlin replaces the original Java codebase, and the interface has been rebuilt on Jetpack Compose. The result is an app that follows Material Design throughout, so that it looks and behaves like it belongs on a modern Android device.

The app's bottom bar now has three sections: Discover for browsing, Search for queries and quick access to categories, and My Apps for tracking installed apps, updates, and issues.

You will also find that the Settings menu has moved to the top-right, being placed alongside the new Repositories menu.

Coming back to the Discover page, it has been configured to highlight newly added apps, recently updated ones, and the most downloaded ones in the repository. Related categories are grouped together, making it easier to browse the full catalog without getting lost in a long list.

Search now handles categories, app descriptions, and translated content in addition to app names, and results for Chinese, Japanese, and Korean queries have improved. Your search history is also saved for future queries.

Filtering has been reworked too; results can be narrowed by anti-features, device compatibility, and category all at once.

What else's changed?

This is how the old F-Droid app looks in comparison.

The app now checks for updates in the background by default, removing the need for the pull-to-refresh gesture that used to trigger repository scans. Of course the manual check is still available from the My Apps page once you go into the three-dot menu.

Similarly, the app hiding feature for changing F-Droid's logo to a calculator app has been moved into the Settings menu under "App Icon," and the Nearby app sharing tool has been temporarily removed.

Concluding their announcement, F-Droid stated that:

F-Droid 2.0 represents a major milestone, but it is not the end of the story. Rebuilding the app has given us a stronger foundation, yet there is still plenty of work ahead.

As the rollout reaches more users, we expect to learn a great deal from real-world usage. Community feedback has shaped F-Droid 2.0 from its earliest design discussions through many alpha and RC releases, and it will continue to guide future improvements.

A looming threat

Last year in August, Google announced that starting 2027, every Android app developer would need to register with the company, providing government-issued ID, signing key evidence, and a fee.

This way, apps from unregistered developers would be blocked from running on certified Android devices.

Of course F-Droid didn't sit by idly; one of their board members, Marc Prud'hommeaux, launched the Keep Android Open campaign in response, which has since brought together over 70 organizations from 20+ countries.

Its signatories include big names like the Electronic Frontier Foundation, the Free Software Foundation, KDE, Proton, Codeberg, VideoLAN, LineageOS, CryptPad and the Tor Project.

Seeing that we are shy of the 90-day mark for this absurd lockdown to occur, F-Droid introducing such a major update only strengthens their stance of not backing down to Google's strongarming tactics. Get F-Droid 2.0

This revamp is rolling out gradually over the coming weeks, so if you haven't received this on your existing installation, just wait. For new installations, it is a similar situation, as the latest stable release is still v1.23.2.

On the other hand, if you can't be bothered with practicing the virtue of patience, then you could download the latest 2.0 beta build from the packages portal.

yt-dlp has over 195,000 stars on GitHub, supports thousands of platforms, and is actively maintained by a global developer community. Unfortunately, the IFPI would like to see it on the EU's piracy watchlist.

Just so you know, the International Federation of the Phonographic Industry (IFPI) represents around 8,000 music labels across 70 countries.

In its submission to the EU's Counterfeit and Piracy Watch List consultation, the group calls yt-dlp "a major problem for the music industry" and names four of its maintainers by their GitHub handles.

A Piracy Watch List?

Run by the European Commission's Directorate-General for Trade and Economic Security, the Watch List identifies online services and physical marketplaces outside the EU reported to engage in or facilitate copyright infringement.

While it sounds serious, the undertaking isn't meant to gather legal findings and does not mandate any form of direct action. It's closer to a naming exercise intended to pressure operators and governments outside the EU into addressing the identified services.

The 2027 edition is being compiled from submissions received through September 2026, with the final list expected in Q2 2027. What does their submission say?

IFPI's submission covers a wide range of copyright enforcement concerns, from AI music generators and cyberlockers to streaming fraud services and domain registrars. yt-dlp appears under the "stream ripping" section, grouped with commercial websites like Y2mate and Savefrom.

They describe the tool as an application that retrieves content by parsing web page data and interacting with platform playback endpoints, with GitHub serving as the primary delivery method for its source code, pre-compiled binaries, and installation instructions.

IFPI names four of the project's maintainers by their GitHub handles: pukkandan, who founded the project and led it between 2021 and 2024, and some core maintainers mentioned in the project's Maintainers.md file, like coletdjnz, bashonly, and Grub4K.

The same submission also flags X, Discord, Telegram, and Vimeo as platforms facilitating copyright infringement at scale.

It's a tool, not a service

The Watch List, as described by the European Commission, targets online service providers and physical marketplaces located outside the EU. yt-dlp fits neither description in any conventional sense.

IFPI acknowledges this by noting that the project's open source nature, its Unlicense licensing, and an extensive international developer community make it "difficult to contain and/or remove."

From their point of view, there's no central domain to block, no payment processor to cut off, and no hosting provider to strongarm into complying with a takedown request.

The source code is distributed globally and can be compiled by anyone with the skills to do so. But that doesn't mean yt-dlp is a piracy platform.

It's a command-line tool for downloading audio and video content, and categorizing it alongside dedicated ripping or piracy websites conflates a general-purpose downloader with services whose primary purpose is facilitating unauthorized copying. Closing thoughts

The Watch List has been used in connection with enforcement against commercial stream-ripping platforms before.

Y2mate.com and eleven other stream-ripping sites were shut down in Vietnam in 2025, and Y2mate had previously appeared on the list.

Before that, in 2024, a German court held the host provider for youtube-dl.org liable in connection with facilitating circumvention. This shows that grouping an open source command-line tool with those commercial services in the same breath does not, by itself, make the tool one of those.

From the newsletter:

We’ve recently released tailcat, a remix of pieces of Tailscale that gives you a way to use the open-source Tailscale data plane without the Tailscale control plane, written by the people who made Tailscale.

Specifically, tailcat is both an open-source Go package and a CLI tool using that package. It lets you run a server-side listener and a client to connect to that server, moving bidirectional bytes back and forth.

Potential usage info from the website link - https://tailscale.com/tailcat:

Setting up a tailnet makes sense when you need governable access, identity, and policy. Sometimes you don’t. You might need to SSH into a development environment for an hour. Give an agent access to a test machine for one task. Connect a game session. Move a file between two machines. Tailcat gives you a secure connection without requiring either side to become part of a larger network.

A technical explanation from the github:

Tailcat is a remix of Tailscale open source pieces to act like netcat, but over Tailscale's data plane, without Tailscale's control plane. Tailscale's data plane (magicsock, internally) gives you point-to-point WireGuard®-encrypted tunnels between two machines with DERP as the NAT-hole-punching communication side channel and the ultimate relay-of-last-resort if NAT traversal fails. Instead of using the Tailscale control plane, all tailcat connection metadata is exchanged out of band, however you want.

License: BSD 3-Clause License

Thunderbird 157 is now available, bringing a long list of fixes across mail handling, authentication, encryption, calendars, and account setup, along with a couple of new controls aimed at enterprise deployments.

One notable fix addresses an issue where Thunderbird’s status bar could remain active after an operation finished, potentially pushing CPU usage to 100%. The release also fixes cases where the message list displayed the wrong sender and where sent messages silently failed to save to the IMAP Sent folder.

OpenPGP users get several improvements. Thunderbird 157 fixes an issue that could cause valid RSA OpenPGP keys to be rejected and prevent encryption. Key discovery can now correctly locate replacement keys after an existing key is revoked. The client can also display remote content in OpenPGP messages encrypted with integrity protection.

On the authentication side, intermittent Gmail OAuth2 failures on Windows have been addressed, along with SMTP OAuth2 problems caused by large access tokens. Exchange users should see more reliable NTLM authentication after password changes. Another fix targets SMTP AUTH LOGIN failures following username challenges.

Moreover, Thunderbird could hang while waiting for an IMAP server greeting during account setup. Pending message moves inside the same IMAP account could sometimes make messages disappear. Both issues are fixed in version 157. Plus, manual IMAP and POP configuration is also simplified, as specifying a port is now optional.

Calendar and contacts users are covered too. The update fixes recurring events appearing beyond their configured end date, outdated CalDAV task content after synchronization, CalDAV invitations failing when accepted before a calendar synced, and some CardDAV address books failing to synchronize.

On the enterprise side, administrators now have two additional policies: DisableChat, which disables Thunderbird’s Chat functionality, and DisableFileLink, which disables FileLink. Plus, the built-in Thundermail add-on has been updated to version 2.0.16.

Rounding things out are fixes for disappearing inline images in edited drafts, incorrectly triggered message filters, blank Yahoo messages under certain MIME handler configurations, the Quick Filter keyboard shortcut, and various visual and UX issues.

For additional details, see the announcement.

cross-posted from: https://lemdro.id/post/46516699

GitHub · Google Play

Opens PDF, Word, Excel, PowerPoint, photos, video, audio, Markdown and code, all rendered on the device. About 5 MB, one build for every processor, Android 8.0 and up.

Search works in every document type. PDF text selects, copies and reads aloud to a screen reader, and there is a night mode that turns the paper black and leaves most photographs alone.

Its permissions page is empty and the manifest has no INTERNET so it can't open a network connection. Files reach it through the system picker, an Open-with intent, or a folder you grant once. The About screen asks Android what the app requests and shows you the result.

Not an editor. Legacy .ppt does not open. Complex PowerPoint renders approximately.

I will be in the comments today, so ask away, including why it isn't on F-Droid yet.

I know there are a lot of project management apps out there, but is there a simple one you could recommend for a small-scale personal project? It's mainly meant to keep myself organized, and to break down tasks.

About a decade ago I tried to create an alternative to Google, using the Dewey Decimal System to group web domains by subject matter. My vision was that the website was a library, and domains were individual books. Rankings were a mixture of domain reputation and cultural significance.

The OCLC is very protective of their IP, and likes to sue.

Needless to say, my project was shut down before even getting off the ground.

I'm working on reviving the project, under a new classification system (The Open Categorization System), and would love any help I can get.

The project can be found here: https://github.com/ki4jgt/Open-Catalog-System

*Correction -------> yt-dlp-server

Cross posted from https://lemmy.zip/post/72457695

I got this on a old desktop going to a external drive that has a samba connection. Nice offloading work.

services:
  youtube-dl-server:
    image: nbr23/youtube-dl-server:latest
    container_name: youtube-dl-server
    ports:
      - "8080:8080"
    environment:
      - YOUTUBE_DL_UPDATE=true
      - YDL_FORMAT=bestvideo+bestaudio/best
    volumes:
      - /your/internal_or_external/drive/youtube-d:/youtube-dl
    restart: unless-stopped

If you want anonymity and security on Linux, you should consider using the Tor network, and this simple app makes that easy.🤔

https://framagit.org/tractor/carburetor

Managarr is a CLI (command-line) and TUI (Text-based User Interface) tool for managing all of your Servarr's in one place.

This most recent release adds support for Readarr and several compatible forks.

I know that Readarr has sadly been retired, however there's still community support in keeping the dream of Readarr alive. As such, extra time was put into this release to test out Managarr with four of those forks to ensure that in addition to the final release of Readarr, Managarr works with these other forks as well.

So now, as long as a fork of Readarr still is compatible with the v1 Readarr API, Managarr can work with it too.

I tested the following forks and made changes in Managarr to ensure support:

• Bookshelf
• Readarr-Resurrected
• Librarr
• Chaptarr

In addition to Readarr (and forks), Managarr supports Radarr, Sonarr, and Lidarr.

You can try it out for yourself without installing it by visiting the demo site if you'd like!

This is a passion project of mine so I'd love to hear any and all feedback! And thanks to all who contributed to this release!

open software to bridge the gap between researcher and statistician

https://www.jamovi.org/

Is there an application that guesses what language you are typing in and switches the keyboard layout automatically? The idea is that you may start typing in, say, German in any text editor, the application guesses that what you are typing makes more sense in, say, English, so it switches the keyboard layout to English and corrects what you had mistyped.

That's good for lazy typing but more importantly it helps with those annoying moments where you realise that 3–4 words you've just typed are in the wrong language, so you have to delete them, switch layout and start again.

Keyboard Switcher supports only three languages and Key Switcher disappeared.