Yes, I know snapseed is a mobile app, but that's the kind of simplicity I'm looking for. Pre-made filters, an auto-fix button, adjustment sliders, etc.

I have image toolbox on mobile and even that's a bit over the top with option (and I still haven't found sliders for brightness, contrast, saturation, shadows etc in that maze).

Linux or Windows programs are fine, I run both.

Is it good? Are there any better alternatives?

Dopes anyone know any good mobile app frameworks that are open source. I would like to be able to develop from windows, but move over to a mac (I own one) when I build for IOS. I want raw NATIVE ui provided by SwiftUI and whatever android has (material design I think).

Are there any privacy or security issues here? Would be using this with Proton Mail, probably . . .

Has anyone tried this? I'd like to be able to have something that can sync files between my desktop and phone.

Originally I used Syncthing, until (IIRC) an update to the Syncthing-fork android app messed up all my settings and made me angry enough to ditch it. Then came Filen, which started off well, and it still going well, but doesn't yet have the ability to sync to phone. The feature is promised for the future, but I'd really like to have it now . . .

Folks, are there GenAI tools that can be used like ChapGPT prompt? Basically, chapgpt seems to now require login and i don't want the thing to profile me. I'd rather train a foss tool.

If we combine these two sets of data^1 we obtain a fascinating result^2.

• 46% of all code out there, in every app, is maintained by hobbyists
• 13,8% is maintained by “I sometimes get a bit of pocket money for my code”
• 40% of all code out there is maintained by an industry-paid person

So, nearly 60% of all code being actively shipped in an app or product in the wild is hobbyist-maintained open-source.

See also this discussion on lobste.rs on the economics of the average (as in median) open source project:

https://lobste.rs/s/ftwkvo/hobbyist_maintainer_economic_gravity

To sum up, apparently most open source projects are small, and aren't funded as paid work. And they matter because of their number, which has the effect that they make up a large part of all software in use.

Im trying to find a few different softwares

1. screen recording and/or streaming (preferably lighter weight)

2. Soundboard and other goofy audio stuff

Me and a few friends run some small low quality shitpost gaming channels and I thought it would be funny if I could just randomly chuck sounds in chat and make it a bit more shitposty. We have a lot of fun with it and don’t care for the views, just post for us.

Where does this whole controversy stand right now? Any of you went back to using it? If not, what are the alternatives? I'm pretty dependent on it but in no way informed enough to analyse this on my own

Haraltd is a Bluetooth daemon that provides a JSON-based RPC over the native OS's Bluetooth stack. It currently only supports Bluetooth Classic, and runs on Windows and MacOS. Installation instructions are in the README.

It was created to reduce the pain points of dealing with the various Bluetooth stacks present in different operating systems, and to present a simpler API to handle Bluetooth (classic) based operations. It is intended for Bluetooth managers and possibly can be used for scripting purposes. See bluetuith for an application that interacts with Haraltd.

The RPC specification is published here.

A table of the daemon's features is posted here, but to summarise:

• Adapter/device management

• Automatic/manual profile-based connection

• Pairing with authentication

• OBEX profiles (currently only Object Push, but more OBEX profiles will be added later)

• Notifications for various Bluetooth events

• JSON-based RPC over a Unix socket

This was tested only with a sum total of 3 devices (2 Android phones and 1 Bluetooth earphones), so any feedback is appreciated, especially from users who can test with other kinds of Bluetooth classic devices.

Note: No AI was used to manage the codebase or generate code.

I just open sourced my personal project for tracking relationships. It's like a CRM but for people you actually care about, not sales leads.

The problem: We all have hundreds of contacts scattered everywhere, but can we remember when we last talked to an old friend? Their birthday? How we met them?

The solution: Nametag helps you track people, map how they're connected, and visualize your network as an interactive graph.

Features:

• Track people with flexible attributes (birthdays, contact info, notes)
• Map relationships (family, friends, colleagues, custom types)
• Network graph visualization showing how everyone connects
• Custom groups for organizing contacts
• Birthday and contact reminders
• Dark mode, internationalization (EN/ES)
• Mobile-responsive

Tech stack:

• Next.js 16 with TypeScript
• PostgreSQL + Prisma ORM
• D3.js for graph visualization
• Redis for rate limiting
• Tailwind CSS
• Docker Compose deployment

Why AGPL-3.0?

I chose AGPL instead of MIT/Apache because I want to ensure that if someone modifies and deploys Nametag (especially as a hosted service), they have to contribute their improvements back to the community. Personal relationship data is sensitive - users should always have the right to inspect and modify the code handling their data.

Dual model:

• Hosted SaaS: https://nametag.one/ (free tier: 50 people, paid from $1/month) - sustains development
• Self-hosted: Unlimited contacts, complete data ownership, free forever

The SaaS helps fund development, but self-hosting is a first-class citizen with no compromises. Auto-verified accounts, no email service required, works completely offline.

Contributing:

Looking for contributors! Areas where help would be awesome:

• Additional language translations (currently EN/ES)
• Graph visualization improvements (performance with 500+ nodes)
• Mobile app (Native would be great, but also open to React Native or similar)
• Export/import formats (vCard, CSV, etc.)
• Documentation improvements

GitHub: https://github.com/mattogodoy/nametag

I'd be happy to hear any suggestions you might have. Have a nice day!

Anyone here ever tried keeping a Markdown note next to their movie files? I’m talking about something like having a MovieName (Year).mkv and a MovieName (Year).md living in the same folder.

I was thinking it could be a nice way to keep personal notes about the movie, quick thoughts after watching, trivia, or even just a record of when and which version I watched. Since Markdown is plain text, it feels future-proof and easy to edit from anywhere.

Just looking to see how other people handle notes or metadata outside of the usual movie database apps.

I posted this article, written by Paul Romer, because while it is a few years old, the questions it adresses are more actual than ever - it could have been written yesterday. It is about propietary systems slurping up and commecializing freely available content from an economy of freely sharing ideas and facts.

The article asks why Jupyter succeed where Mathematica failed. The obvious contrast is between the proprietary world of Wolfram and the open-source model of the software ecosystem that Jupyter mobilizes.

[...]

He goes on to detail how this was implemented concretely, and what were the practical effects.

Wolfram made it hard to share a readable PDF version of a notebook because it wanted someone like me to distribute content in its proprietary file format, the CDF.

By the way, Romer starts with mentioning an article in The Atlantic, which is worth reading as well, since it brilliantly describes the achievement of Wolfram, as well as its propietary model and the effects of applying it to science. That article may not be accessible to everyone any more. An archived version of that article is here.

Brodie a Linux YouTuber uploaded a video about a project, I was not aware off: Software Heritage. It is basically for code, what Internet Archive is for websites. If you want watch Brodies video as an introduction: https://inv.nadeko.net/watch?v=MUA9Fu4jNGY or YouTube directly https://youtu.be/MUA9Fu4jNGY

• Archive: https://archive.softwareheritage.org/
• Mission: https://www.softwareheritage.org/mission/
• Features: https://www.softwareheritage.org/software-heritage-features/
• FAQ: https://www.softwareheritage.org/software-heritage-faq/
• Wikipedia Article: https://en.wikipedia.org/wiki/Software_Heritage

We are building the universal software archive

We collect and preserve software in source code form, because software embodies our technical and scientific knowledge and humanity cannot afford the risk of losing it.

Software is a precious part of our cultural heritage. We curate and make accessible all the software we collect, because only by sharing it we can guarantee its preservation in the very long term.

Hey all! I live in a housing cooperative in the USA and I've recently been elected to the board to help manage things for the housing community. I would like to modernize where possible, and wean ourselves away from corporate tools in an effort to increase the privacy of my fellow residents and provide resilience against corporate enshittification and our dangerously hostile federal government.

We're currently using a horribly unsafe (from data ownership and privacy perspectives) mix of corporate software offerings to accomplish our management tasks. Gmail, Google Drive, TownSq (for property management needs, like maintenance tickets and payment processing), various proprietary building entry apps (e.g., pin codes for locks), etc.

I'm very comfortable with de-Googling and self-hosting something like Nextcloud to replace some of those things, but I've had very little luck finding fitting open source replacements for the property management portion. Everything I've been able to find is targeting landlords, real estate, or HOA models. None of those fit well for cooperative housing.

I'm leaning towards a self-hosted mix of NextCloud, possibly (mis)using Forgejo for maintenance requests, and Home Assistant to make a frankensystem covering as many community management needs as I can, and we'd just have to keep using proprietary stuff for the rest. However, I really would love to hear any creative suggestions or feedback from all of you about anything I've said, most especially if you're part of a cooperative and have dealt with similar issues.

All my new code will be closed-source from now on. I've contributed millions of lines of carefully written OSS code over the past decade, spent thousands of hours helping other people. If you want to use my libraries (1M+ downloads/month) in the future, you have to pay.

I made good money funneling people through my OSS and being recognized as expert in several fields. This was entirely based on HUMANS knowing and seeing me by USING and INTERACTING with my code. No humans will ever read my docs again when coding agents do it in seconds. Nobody will even know it's me who built it.

Look at Tailwind: 75 million downloads/month, more popular than ever, revenue down 80%, docs traffic down 40%, 75% of engineering team laid off. Someone submitted a PR to add LLM-optimized docs and Wathan had to decline - optimizing for agents accelerates his business's death. He's being asked to build the infrastructure for his own obsolescence.

Two of the most common OSS business models:

• Open Core: Give away the library, sell premium once you reach critical mass (Tailwind UI, Prisma Accelerate, Supabase Cloud...)
• Expertise Moat: Be THE expert in your library - consulting gigs, speaking, higher salary

Tailwind just proved the first one is dying. Agents bypass the documentation funnel. They don't see your premium tier. Every project relying on docs-to-premium conversion will face the same pressure: Prisma, Drizzle, MikroORM, Strapi, and many more.

The core insight: OSS monetization was always about attention. Human eyeballs on your docs, brand, expertise. That attention has literally moved into attention layers. Your docs trained the models that now make visiting you unnecessary. Human attention paid. Artificial attention doesn't.

Some OSS will keep going - wealthy devs doing it for fun or education. That's not a system, that's charity. Most popular OSS runs on economic incentives. Destroy them, they stop playing.

Why go closed-source? When the monetization funnel is broken, you move payment to the only point that still exists: access. OSS gave away access hoping to monetize attention downstream. Agents broke downstream. Closed-source gates access directly. The final irony: OSS trained the models now killing it. We built our own replacement.

My prediction: a new marketplace emerges, built for agents. Want your agent to use Tailwind? Prisma? Pay per access. Libraries become APIs with meters. The old model: free code -> human attention -> monetization. The new model: pay at the gate or your agent doesn't get in.

Brave is essentially just Chrome with an adblocker, a bunch of bloatware, and a bunch of controversies.

Brave took BAT donations in YouTuber's names without their consent, with them keeping the money if the YouTubers didn't claim it. https://davidgerard.co.uk/blockchain/2019/01/13/brave-web-browser-no-longer-claims-to-fundraise-on-behalf-of-others-so-thats-nice/

Brave's search engine crawler hides itself from websites by pretending to be Googlebot, and Meta (Facebook) buys API access from them to train their AI. https://stackdiary.com/brave-selling-copyrighted-data-for-ai-training/

The business model of Brave rewards as a whole is to block all other ad networks to replace them with their own, which is unfair as only YouTubers and websites that have joined can make money from most Brave users.

If Brave actually cared, they would create an acceptable ads style feature which was free for everyone and allowed simple contextual banners while blocking ads which track you, take up most of the page, or have NSFW content.

Their approach is monopolistic as they have full control and can strangle YouTubers and websites by dropping pay at any time.

And Brenden Eich has said on Twitter that he plans to release "Brave Origin", which is a paid version of Brave without the bloatware. That name is ironic as he is admitting that his browser is commercialised and bloated, which is similar to when gorhill gave uBlock way to Chris Aljoudi who commercialised it, which led him to create uBlock Origin.

If you use Brave, ditch it and look at using Librewolf or Helium instead, which both include no ads nor tracking and don't have Brave News, Rewards, Wallet, Talk etc bloatware.