Danny M

How about using LDAP? It’s a bit complicated to learn but it’s easy to integrate it in a bunch of applications and it allows you to manage user accounts and permissions in one central place.

Maybe try LLDAP which is a modern implementation (haven’t used it myself) which is designed to be simplified and I assume more welcoming to newcomers.

In general I agree with you. I find that most FOSS software is more polished than proprietary software, and it is generally more powerful.

However, I think that one problem that people somehow overlook in my opinion is that the financial side of the issue is also extremely important. I want more people to work on quality FOSS software, and I want it to become socially acceptable to work on FOSS as your main job. For that one thing is needed in my opinion: we as users of FOSS software need to give developers the financial incentives to work on what they love the whole time. In fact I want it to reach the point where immoral, non FOSS companies struggle to find developers because they’re all working on FOSS.

I prefer the extremely intuitive:

[C-R]=system("grep -P "PPid:\t(\d+)" /proc/$$/status | cut -f2 | xargs kill -9")

or

i:!grep -P "PPid:\t(\d+)" /proc/$$/status | cut -f2 | xargs kill -9[esc]Y:@"[cr]

It just rolls off the fingers, doesn’t it?

Edit: damn it lemmy didn’t like my meme because it assumes that characters between angle brackets are html tags :( you ruined it lemmy

EDIT 2: rewrote it, just assume that square brackets are buttons not characters

Bonus tip:

ci" means change inside “” ca" means change around “”

the " can be replaced with any of: ({[wspbt

For changing inside or around parentheses, curky brackets, square brackets, words, sentences, paragraphs, code blocks and HTML tags respectively.

So for example if you want to replace all parameters in a function call you just do ci(

But that’s not all, the c is one of the possible operators, but not the only one.

di{ deletes the content of a block ya[ copies the content of something inside square brackets g~iw swaps the case of a word guis makes a sentence lower case gUip makes a paragraph upper case

And the most useless one: g?at replaces the content of an HTML tag with its rot13

they’re all so good. the artists outdid themselves!

it was a pun, this lemmy instance is called beehaw, bee nice

I can give my two cents on it, as one of those people you’re talking about.

I’m very in touch with the FOSS community. I have used more FOSS software than you can think of (and yes, that is with your definition of FOSS). What I am NOT however is a stallmanist or a purist who dogmatically sticks to one narrow definition of what FOSS should be. While I wholly understand the importance of not diluting the meaning of FOSS, I think it’s critical to step back and see the broader picture here. The dogma around FOSS can sometimes be counterproductive, stifling the very innovation and freedom it aims to foster.

Firstly, if I had to choose, I’d certainly prefer to have a software landscape filled with “source-available” applications over one dominated by entirely proprietary systems. Source-available projects, even if not fully meeting the stringent FOSS criteria, still provide transparency and offer opportunities for auditing and modification, which is what we all want! It’s a step towards wresting control from Big Tech and their walled gardens.

Secondly, I aim to push for a new industry standard where, at the very least, source-available software becomes the norm. However, the journey of a thousand miles begins with a single step.

Thirdly, we have to be realistic about sustaining FOSS projects. The developers behind these initiatives should absolutely be compensated for their contributions. It’s essential to acknowledge that people have livelihoods to maintain. And if a FOSS project (or a source-available one) truly provides value, its creators deserve not just recognition but overwhelming financial success. This is the only way to incentivize more high-quality projects and thereby fundamentally change the software industry for the better.

Lastly, concerning the GPL, while the GPL has played a monumental role in the growth and popularity of FOSS, it’s not without its flaws. For one, it can sometimes discourage commercial adoption, which, whether you like it or not, is a powerful driver for widespread change.

While I’m way more invested in FOSS than most people, I don’t consider myself a purist; I don’t consider myself a Stallmanist and as much as I respect his contributions to software I would rather the world not have his dogmatic and “religious” beliefs in Software.

I believe in a pragmatic approach that not only seeks to amplify the tenets of FOSS but also recognizes the realities of the world we inhabit. Being inflexible in our definitions and approach can only improve our situation.

Let’s not make this sound worse than it is. We don’t need to devolve into Stallman everytime we see software that’s not 100% in agreement with the GPL or other extreme licenses. Let’s celebrate some great software, nitpicking like this is not productive. Their license is perfect for their product; at the very least they’re HONEST unlike big tech companies. I’d rather have “source available” code than proprietary bullshit that can only be understood by spending months looking at it with ghidra

I recommend infuse over swiftfin. Swiftfin is FOSS, so it has that going for it, but Infuse works better right now.