The recent PKM thread had me thinking about what folks are using as journaling app/portal. I do use Obsidian for my second brain right now and genuinely love it. But I find the mobile app on Android to be a bit clunky, if I'm honest. Seems slow to open even with very few plugins. For jounaling I've used DayOne for years. I started back when it was iOS/MacOS only, but then switched phone to Android and haven't been back. But now they have an app and web app for that. What I don't like is the somewhat goofy format it saves in and it's on their servers. They used to allow you to at least leverage your own Dropbox, but no longer.

For the past several months I've tried several FOSS options. Main criteria is that I could host it myself, supports offline entries stored in an open file format (preferably MarkDown), and had either multi platform app or a decent web app. That lead me to try these:

Memos
Pros:

• Great persistent web app
• Slick UI that is light and snappy
• markdown support
  Cons:
• Stuffs the .md inside a database file so can be a bit cumbersome to export data
• No offline support. There is a 3rd party app that hopes to implement it

Flatnotes
Pros:

• Incredibly simple
• Another easily deployed app
• Flat Markdown files
  Cons:
• Web app on mobile is almost unusable as in it doesn't scale well to smaller screens
• Very early development, but very likely to stay as minimalistic as it is now.
• No offline and very unlikely to ever have it

Joplin
Pros:

• Multi platform apps that perform well
• End-to-end encryption supported
• Could replace both DayOne and my To-do solution (Google Keep)
• Offline support
  Cons:
• More database stuff instead of flat markdown files

One solution I've been testing lately is using IAWriter to write to a 'Journal' folder within my Obsidian vault on Google drive Obsidian Vault > Journal > 2023.... for example. This works surprisingly well. Of course IAWriter is a bit spendy at $29 for Android and then more $ for other platforms as they're sold separately.

So I'm curious what other people are using for just simple daily journaling, random thoughts, etc. If there's an approach I've missed I'd love to hear it. Joplin is so dang close but not having the structure of plaintext files is a no go for me as I don't want to be trapped by any one product should something happen to the development down the road. Doesn't have to be free, but I want control of the entries either on my own server or cloud storage.

I've been seeing some cool software in the church space lately with lots of fancy bells and whistles that handle many different aspects of running a church (social, presentation, tithing, etc.). However, not all churches, especially small ones, can afford them or have members savvy enough to set it all up and maintain/operate them. I thought this could be a cool thread for free and or open source software that churches can use can use (Does not necessarily need to be design specifically for churches).

EDIT
Here is a list of paid examples:

• Renewed Vision
  • ProPresenter
  • ProVideoPlayer
  • ProVideoServer
  • Scoreboard
  • ProContent
• Microsoft Office
  • PowerPoint
  • Excel
• Google
  • Slides
  • Sheets
  • Forms

Here is a short list of FOSS alternatives:

• Free Show
• Owncast
• Rock RMS
• Choyr
• OBS
• OpenLP
• WorshipTools

The vast majority of free and open source software available is well known for being clunky, having very unintuitive UI/UX and being very inaccessible to non-nerds.

We can see this in Linux distros, tools, programs and even fediverse sites.

I understand that a lot of it is because "it's free", but I also feel like a lot of people who make and use FOSS don't actually value user-friendliness at all. I feel like some of it is in order to gatekeep the less tech savvy out, and some of it is "it's good enough for me".

What are the best theories for why this is the case?

EDIT: A lot of replies I've been getting are focusing on the developers. I'm asking more why the users seem okay with it, rather than why the developers make it that way.

The benefits of a free and open Internet is something that the millennial generation created long ago to make this world a better place and full of opportunities for everyone, not just those who can afford access to it. These benefits are something that makers of quora platform themselves used in the form of open source software like Python, Django, HTML, etc. to build that very platform in the first place.

But now, by denying those benefits to others and bringing in a paywall, quora is striking on its own proverbial roots. There are much better ways to reward their content creators than holding their answers hostage with a paywall. The plain old advertising revenue sharing model can be still used, just like Adsense does. This is a win-win thing where everyone gains including the platform, content-creator and advertiser.

It's extremely important to oppose this paywall move by quora because this attacks the very foundation of the free and open Internet as we know it. Imagine what happens tomorrow if other informative sites like StackOverflow, Wikipedia, etc. start following quora's path. Imagine the plight of the poor and under-privileged sections of the society who cannot afford costly subscription to information. And yet, as members of the evolved human race of 2023, they very much deserve access to this information.

I urge all netizens who consider themselves part of this free and open culture tribe to sign this petition and through it, convey our grievance to quora and let them know why this is wrong and what is at stake (our freedom).

If you agree with my cause, I urge you to sign this change.org petition created in this regard requesting Quora to revert the Paywall move.

I know it's a technical question but I want to know specifically from freelancer perspective. A freelancer's decision making differs from that of regular corporate worker in this regard due to many reasons:

1. Freedom to choose: Unlike corporate, a freelancer isn't imposed any process or specific software guidelines to follow. They're free to use Linux and open source if they want to.
2. No team compatibility: A freelancer can work on specific project with a geographically distant team but they don't have to submit to any long-term compatibility constraints.
3. Budget constraints: A freelancer can't typically afford costly licenses. With corporate, they can scale well and bring down the licensing costs which isn't true for freelancers. Hence, open source software is typically more suited to their workflow (even when using a Windows OS).

Given all these factors, do you think a Windows or Linux laptop is more suited for a typical Freelancer? What do you happen to use?

Hello everyone,

This will be a long post because I want to give my post the proper context. I apologize in advance for taking your time.

About five months ago, with the help of relatively high ceiling of Windows 11's system requirements, I finally pushed myself to use Linux exclusively on my desktop. It was a decision between using Windows LTSC or Linux and I went with the better long term option.

I am not a programmer but I'm also not unfamiliar with the Linux world. I believe I've used one distro or another on a spare computer for shorts period of time since at least 2008. But those use cases have always been to satisfy the curious side of my brain as I am always interested in technology. So after installing distros ranging from Ubuntu to Arch, my curiosity waned enough to never look deeper into how these systems work. They were, after all, a hobby project on a spare computer that was often gathering dust.

When I decided to switch exclusively to Linux, the next decision I had to make was to pick a distro. Naturally, I looked for the established players first. Ubuntu was the obvious choice because it has long been the distro for newbies and there are a lot of guides on the internet if I ever needed help, which was inevitable. But then I read about snaps and thought that was a deal breaker. I was moving to Linux specifically because I don't want things shoved down my throat. I had no intention to relive that¹.

So Ubuntu was a no go, but I was certain I wanted a Debian based distro as their support and software availability was unmatched, maybe save for Arch². At this point, why not Debian right? It's known for being rock solid and it's Debian itself, not some derivation. Well, because I had various issues with Debian before. These issues were always fundamental and not very specific too, so I didn't want to risk wasting a lot of time fixing things I didn't understand, only for them to break again after a couple of days. Then I came across Pop!_OS, which seemed like a perfect fit. It was Ubuntu without its worst parts, came with Nvidia drivers and it had a company behind it that seemed to be committed to Linux. I installed it and everything just worked. I had zero issues.

But then I started getting that FOMO itch again. GNOME 42 was out and it looked great, but Pop!_OS was two versions behind. I also found out that they're working on their own DE, which might end up being great (it looked nice) but I didn't want to leave an established player like GNOME behind, including all the benefits you get from its wonderful extensions. I started looking for other distos again and Fedora caught my eye. I was obviously aware of Fedora, I even used it once back when YUM was still a thing, but it didn't leave a lasting impression on me. The fact that it wasn't a Debian based distro was also a disadvantage because that meant something different and at this stage of dipping my toes into Linux, I didn't think different might be the best way to go for me. Still, despite my best judgment, I installed Fedora on a USB and used it live. When my gut feeling was confirmed by my research about how Fedora leaves things as stock as possible and is ahead of the curve in terms of upcoming technology (btrfs, PulseAudio, Wayland et al.³) without sacrificing on stability, I was hooked.

After renewing my Timeshift backup, I formatted my Pop!_OS system and installed Fedora. The installation process could use a facelift, but it handled everything perfectly. I didn't even have some of the issues I had with Pop!_OS right after installation. It was literally problem free. I'm now on day #3 of using Fedora and the experience remains the same. The only issue I had to deal with was trying to get Timeshift to work (apparently it doesn't play nice with btrfs on Fedora), but instead of wasting my time with that, I just installed Déjà Dup and I'm good to go again. Barring any drastic issues, I don't plan on changing my distro again.

Now, onto my plea for guidance.

I'm looking for comprehensive resources that will teach me how Linux works under the hood. Considering my non-programming background, I'd appreciate it if the language is approachable. The reason why I want this, for one thing, is to learn more about the system I'm planning to use probably for the rest of my life (in tandem with macOS) but also, I want to do some cool stuff Linux allows users to do.

Just to give a quick example. Yesterday, I installed Rofi, which is, besides many other things, an app launcher. I got it to work just fine, I even got a configuration of my own with a theme of my choosing, but when it comes to using some scripts, I just couldn't do it. Every video I watched on YouTube told me how easy it is to use scripts with it as if it's a self-explanatory thing, but I was simply clueless. There was a lot of lingo thrown around like environment variables, setting up $PATH, making the scripts executable with chmod etc. I have very little knowledge of these things. I want to learn what they are, why they exist, and how they all tie together. I want to learn how /etc/ is different than /usr/ and the difference between X11 and some DE (or if they're even in the same category of things). Now, at the risk of sounding impatient and maybe even worse, I also don't want to go way too deep into these things. I am not, after all, trying to become a kernel developer. I just want to be better informed.

There are a lot of information on the internet but most of this information is scattered and out of context. If I try to learn more about one thing, I'm bombarded about other things that I don't know, so in the end I learn nothing. In short, I'm looking for a comprehensive, entry level video series or a book about Linux written in an easy to understand language that assumes no prior knowledge.

Additionally, I'd appreciate any website, YouTube channel and what have you to keep up with recent developments in Linux. I already found a couple as there are plenty of them, but I'd like to learn more about how people here keep up with this fast changing environment.

Thank you for reading and sorry for being so verbose! 😊

^{1: I know you can remove snaps, but I didn't want to deal with the hassle of any possible issues deleting a core system functionally might bring about.
2: Despite finding its approach fascinating, I had no intention to get into Arch because it's a rolling distro and I didn't want an advanced system that can break at any moment in the hands of a novice like myself.
3: To be clear, I don't know how most of these technologies are better than alternatives, but the Linux community at large seems to think they're drastically better than alternatives and are the future.}

A project I'm working on requires me to cover a bit of comedy targeting Lennart Poettering as it's tangentially related, and I'd like to have more context even though it's not strictly necessary. I'm a nontechnical Linux user who used the OS before systemd came around, but really the only impact on my life it's had is that I occasionally use systemctl to control services.

Though I wasn't paying as much attention to the community around the time major distributions switched, I've been casually exposed to criticism of it ever since I came back, and I'd like to make sense of it all and form an opinion beyond "I like Fedora and GNOME and it seems to go hand-in-hand with those". I've read The Biggest Myths, the Wikipedia article, some stuff on freedesktop.org, and of course absorbed the venom slung back and forth over systemd in every FOSS community, but it's hard to get a full picture. And a picture from 2022, for that matter, as a lot of this information comes from its early days. Help me out?