The federation between mastodon and lemmy is strange. If a M account wants to follow a L community, they need to follow an automated M account which represents the L community. But if any M post mentions that L community, the post will get boosted by the community's M account, so everybody who follows will get a notification. And I'm not sure if this can be moderated from the L side, because it seems like it never goes through L. Such as - do you see this @opensource ? Does a L mod see this?

Source here - https://github.com/FossifyOrg/Voice-Recorder/releases

I dont know if the moderators cant see this but other instances can. Please remove the spam guys. This community used to be good.

Example:

https://play.google.com/store/apps/details?id=com.macoou.feedbrowser

Firefox doesn't seem to do support it currently. Chrome and Brave do come up as options

I'm using a documentation framework that supports offline builds. It works well across browsers on desktop, but it's not great on mobile.

Any recommendations?

Polls:

• https://strawpoll.com/XOgONY582n3
• https://strawpoll.com/7rnzmK9oDyO

Once the threads are finished, it is now time to discuss how the megathread should be built. I apologize in advance for having forgotten to mention any apps for daily use. I noticed that I may have failed launchers or other useful apps for daily use. Still, the threads are open. Any suggestion are welcome. I would like to ask you to contribute with upvotes or downvotes in the comments that best suit your vision. All contributions are important.

Here, you can discuss and say your apps you may have forgotten - https://lemmy.ml/post/11678824

Since English is not my native language, I will try my best to explain some details I want to discuss with the Lemmy community. If you don't understand certain things, please tell me what you don't understand, and I will do my best again.

So…… Lets begin………

• I was thinking of opening three threads per year to update the megathread. Do you think that 3 times a year is enough (for example, once in January, once in June, and another one in December), or do you think I should open 5 to 6 times a year? | Poll here - https://strawpoll.com/XOgONY582n3

• Tittle Im thinking: [Megathread] FOSS Apps — Lemmy Edition | You like? Or do you want another?

• How do you prefer to divide the megathread? I'm thinking of dividing the threads into single topics, that is, intended for each type of app — for example, one part just for YouTube apps, another just for email apps, and so on. This is an example - https://i.imgur.com/pgw47oM.png | I guess it explains better what I'm talking about. How would you like to see the megathread?

• I'm thinking of accepting only suggestions with two upvotes (or a difference with two upvotes) or above on previous threads. Do you think it's fair, or should I accept all the suggestions given? | Poll here - https://strawpoll.com/7rnzmK9oDyO

• In the megathread, I will not accept app suggestions because, in this way, the topic will be clogged. However, I must remain open to important information and other things, as, for example, happened with Simple Mobile Tools, which was sold to a shady company. Of course, all suggestions are welcome, besides app suggestions. Your suggestions will be prompt and extremely useful when I open the threads to update the megathread.

TL;DR …. So far, I'm thinking this:

• Open three-time-per-year threads to talk about new updates for MegaThread.
• Divide all apps into specific categories.
• Only accept suggestions with 2 upvotes or above.
• Not accept suggestions on MegaThread and accept only tips and important information.

Tell me what you think. What you agree or/and disagree.

Lovely day for everyone!

cross-posted from: https://programming.dev/post/10063205

cross-posted from: https://programming.dev/post/10063202

cross-posted from: https://programming.dev/post/10063199

Proton's mission, funding sources, independence, and community are some of the reasons we're more resilient than other privacy-first companies.

ListenBrainz: an open source and crowdsourced music database and music recommendation engine.

https://listenbrainz.org

@opensource

Since yesterday, the really cool fork of openboard with active development and support of adding a swype library manually, got rebranded into Heliboard. A release on izzyondroidrepo and fdroid should be coming soon.

PS. If you are using the old fork you have to remove it first and do a backup of your settings.

the title says it all 😀

Keep small scale open source alive. F-Droid ftw! And consider to donate to Daniel as developer of XMPP software. See also :

• https://gultsch.social/@daniel/111923502625498287

• https://gultsch.social/@daniel/111923542300799098

Here is some important context you need to understand Quicksy:

· It’s not successful at all. The user count has stagnated at just under 1,500 for years.

· It’s very expensive to run. While Quicksy doesn’t have that many users it has a good amount of registrations. Sending SMS is really expensive. There are months in which I’m paying ~100 Euro for server cost + SMS. I receive a few donations that reference Quicksy alongside Conversations but nothing close to 100 Euro / month.

https://github.com/mr3y-the-programmer/Podcaster

cross-posted from: https://lemmy.ca/post/15043450

How is Ubuntu Touch in 2024?

How is the experience nowadays on the os?

Is it stable?

How are the apps?

How is LTE performance?

https://old.reddit.com/r/linux/comments/1apoc6n/3_years_of_work_and_1_million_users_later_im/

In case you guys missed it - btop++ has had for GPU monitoring for a while now. However, it didn't work with AMD ROCm v6.0 until a few hours ago (v1.3.2)!

To get GPU monitoring to work, you'll need to compile btop with GPU support, or used a distro-provided package compiled with GPU support. Arch users for instance can use the btop-gpu-git package for this.

The other catch is that right now the monitoring options are pretty basic, so if you're really interested in proper GPU monitoring, you might want to stick with nvtop. But hopefully that changes in the near future now that btop has basic GPU support!

Made with the Godot engine. Source-code: https://github.com/Nitwel/Immersive-Home

Obligatory note for those that haven't read/retained the news: Simple Mobile Tools was sold to ZipoApps - an Israeli company that specialises in buying and monetising popular apps.

Fossify is the fork of the Simple Mobile Tools repos, and they're gradually getting through each app and re-releasing them under the new name.