#vendorlockin — Public Fediverse posts

Today it is Mythos. Tomorrow it will be something else.

The pattern stayvendorlockin #securitystrategy #appsec #operationalresiliencempanies need urgency to position themselves.

Everyone wants to attach themselves to the next big wave and present themselves as the answer.

Real organizational readiness is not about pushing AI into every layer because the current panic cycle says so. The practical test for any change is much simpler:

• Does it strengthen existing tools and workflows?

• Does it preserve model and vendor optionality?

• Does it reduce backlog and repetitive operational drag?

• Does it reduce attack surface by removing software, access, and exposure you do not need?

• Does it reinforce the boring fundamentals like inventory, patching, least privilege, segmentation, and recovery?

Without those checks, you are mostly just trading places. One dependency gets swapped for another. One vendor stack gets replaced by another. One kind of complexity becomes another. Very little materially improves.

Most of the time, we just kick the ball a few months further down the road and call it progress.

I wrote about many of these ideas in my pragmatic guide:
https://cyfinoid.com/a-pragmatic-guide-to-being-mythos-ready/

#securitystrategy #appsec #operationalresiliencempanies #cybersecurity #aisecurity #attacksurfacereduction #vendorlockin #operationalresilience

Hey FOSS-community, I'm trying to compare #GitLab and @forgejo.

Some important aspects are:

- #DigitalSovereignty (most important)
- #SelfHosting
- #Collaboration between instances (#federation)
- #PublicValues
- Prevention of #VendorLockIn
- #Scalability
- #Robustness
- Guaranteed #support by professionals
- Software #freedom
- #Longevity
- Suitability for the #government

Do you have any thoughts on this? Or any useful links?

cc: @Codeberg

#Git #GitForge #opensource #FOSS #community

Finding a sleek, distraction free #markdown editor for #Android is rough, especially when paired with a cloud storage provider that isn't #Google.

My candidates were #OpenNote and #Quilpad, but both take away power from the user by preventing them from managing their own files.

Both refuse to work with the Android cloud provider backend, to a point where I can't even import my MD files from #Jottacloud.

One has experimental support for #Nextcloud tho, which smells like #vendorlockin.

I'm still not out of the rabbit hole of searching for an #OpenSource #PersonalKnowledgeManagement software. 🐰

I'm gonna give a second try to @zettlr tomorrow! Their docs are *surprisingly* user-friendly and they claim to stick to the pure #CommonMark where probable. It's all the while being nice to researchers with citing, inline usage of #TeXLaTeX, #MermaidJS, and pop-over #footnotes. Provision of the simple #PDF export and #Pandoc customization are welcome, too!

But, to be fair, I may be overexaggerating how good #Zettlr is because of my recent disgust with #VendorLocking. In fact, almost anything that closely follows the common spec and is #FreeSoftware might suffice already. Having something as advanced and closer to the roots is certainly refreshing!

#Markdown #zettelkasten #authoring #Zettlr #ReferenceManager #ReferenceManagers #PKM #NoteTaking #NoteTakingApp #NoteTakingApps #KaTeX #frontmatter #Obsidian #Logseq #Anytype #Notion #VendorLock #VendorLockIn #FOSS #FLOSS