... and it works fabulously. I have been running Bluefin (same folks as Bazzite) from one of these templates for about 6 months and it has been a near on flawless experience. I have moved from Fedora 40->41->42 without having to touch a traditional "upgrade".
I think the logic is to differentiate the "identity" from a "user"
One identity can have multiple users (one for each organization)
At the same time, a user can have multiple identities. (e.g. username/password, Google oAuth, SAML etc.)
My garden bed has a slug problem. How can FarmBot help me with this? Is there a tool, like a grabber, that automatically catches intruders and carries them away?
The source code seems to be on sourceforge.net.
I site once important, but now when I see it I either think "the project is most-likely dead" or "can this project be legit? Am I getting malware here?"
> The source code seems to be on sourceforge.net. I site once important, but now when I see it I either think "the project is most-likely dead" or "can this project be legit? Am I getting malware here?"
This is such a sad thing for me. When I was a kid, Sourceforge.net is where I would always go first to look for software, because I knew that it was a reputable host and that open-source projects participated in a culture of greater respect for users than most freeware projects demonstrate.
Sourceforge changed hands and as far as I can tell, the new owners put some effort into getting rid of all the crap and even into protecting users from crap added by the original authors.
Filezilla, for example, initially participated in SourceForge's adware program under the old owner, but after the owner change, actually provided a clean version on Sourceforge (while the version on the website was and still is adware-bundled).
Not saying anything from 2018 isn't valuable... I'm currently working on PDF scraping tools, and my lord, the stuff we're left to work with is abysmal... this could be state of the art.
What is missing in my opinion? It is consistency between the atlassian products and/or adherence of industry “standards”
Confluence and JIRA use a different markup language for posts and none of them uses Markdown (in any flavour), which I would also use to write in-code documentation, like in a README file
The larger problem is that you cannot (AFAICT) edit the markup directly in Confluence or JIRA. I believe this used to be possible, but has been removed in the cloud version, and will die with the server version.
The markup you write gets turned into in-editor "objects" (for lack of a better term) as you type it out. This makes editing an incredibly painful experience. I am occasionally asked to document something on Confluence for a client and every time I feel like I am fighting a battle just to make a basic document.
For example, I strongly dislike their implementation of ordered list editing. They have tried to make the ordered list editing mode "smart", but it mostly just gets in the way, and is harder than writing it out manually. Additionally, you cannot embed other "objects" in an ordered list. If you attempt to insert a file object, or something similar, it splits your ordered list into two, with the second list starting its ordering at the beginning. This would seem to defeat the purpose of having a rich editor with embeddable objects, since I cannot use them if I am making an ordered list, such as set of "how to" steps.
I usually give up an hour in and switch to writing in my text editor instead, but even then Confluence will mangle my input in surprising ways when I paste it in. Rule #1 of making an editor in my book is that it has to be, at a minimum, as easy and useful as a basic text editor. Microsoft Word and LibreOffice, in spite of their faults, are quite good at this. I would guess most software shops could not implement a WYSIWYG editor at that level of polish, and they would be better off just providing editable markup.
