home.social

#lockin — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #lockin, aggregated by home.social.

  1. Beware the software "Lock-In" effect!

    New AI agent templates from Anthropic for financial services firms are the thin edge of the wedge for establishing Lock-In by Anthropic - IMHO.

    Each template is designed to be "customized" with a firm's internal standards.

    This is a the same go to market used by traditional enterprise software vendors (Microsoft, Oracle, SAP, Cisco, etc. etc.) Once created and deployed - these systems are next to impossible to remove/replace!

    Deployment "options" complete the Lock-In by tying a company's software environment to the underlying 3rd party provided production infrastructure - which is also a risk to be carefully assessed. qz.com/anthropic-ai-agents-fin #Anthropic #AIAgents #FinancialServices #LockIn #Risk #Customization #AI #Agent #Banks #Insurance #Claude #Software #EnterpriseSoftware

  2. #UnplugBigTech Tipp 4: Der Netzwerkeffekt

    Gestern haben wir dir empfohlen, auf den Messenger #Signal umzusteigen. Technisch ist das schnell erledigt, aber wie motivierst du deinen Freundeskreis zum Wechsel? Dasselbe gilt für Social-Media-Netzwerke. Hier einige soziale Hacks und Gedanken, die helfen: Besser Leben mit dem Netzwerkeffekt – diese Tipps unterstützen dich auch beim Wechsel zu alternativen Messengern. 👇

    kuketz-blog.de/gutes-leben-mit

    #NetzwerkEffekt #Signal #LockIn #Messenger #SocialMedia

  3. Palentir and the NHS

    The FT has slipped up here - publishing a whitewashing article regarding Palentir and the (English) NHS -part of the companies attempts to avoid questions on (a) how effective the software is (2) how safe the data is given it is an American company and I can guarantee some of it will be exported and (3) lockin. The comments are worth a read - especially the one highlighted.

    archive.today/2026.04.16-07125

    #Palentir #England #NHS #Lockin #Privacy

  4. "Lesson 1: There’s no such thing as a free lunch
    Then: In the early 2020s, a series of cyberattacks linked to Russia, China and Iran left the federal government reeling. The Biden administration called on major tech companies to help the U.S. bolster its defenses. In response, Microsoft CEO Satya Nadella pledged to give the government $150 million in technical services to help upgrade its digital security. It also offered a “free” security upgrade for government customers.

    Now: Last year, the Trump administration announced a raft of agreements with tech companies that were meant to help federal agencies “purchase enterprise AI tools at government-friendly pricing.” Agencies could use OpenAI’s ChatGPT for $1. Google’s Gemini for 47 cents. Grok by xAI for 42 cents. The administration hoped that the low-cost pricing would make it “easier for federal teams to acquire powerful AI capabilities … to enhance mission delivery and operational efficiency.”

    The takeaway: Be wary of freebies. Our investigation into Microsoft’s seemingly straightforward commitment revealed a more complex, profit-driven agenda. After installing the upgrades, federal customers would be effectively locked in, because shifting to a competitor after the free trial would be cumbersome and costly. At that point, the customer would have little choice but to pay for the higher subscription fees. The plan worked: One former Microsoft salesperson told me “it was successful beyond what any of us could have imagined.”
    (...)
    Agencies looking to buy AI tools at discounted rates today must consider how the costs might balloon down the road. The General Services Administration warns that AI “usage costs can grow quickly without proper monitoring and management controls” and advises agencies to “set usage limits and regularly review consumption reports.”"

    propublica.org/article/federal

    #USA #FederalGovernment #BigTech #CyberSecurity #Microsoft #RentSeeking #LockIn

  5. @miXsed Vorsicht: lesbar bedeutet nicht, dass man es mit Tools gut weiterverwenden kann. Gerade #Markdown hat hier ein massives Problem mit den vielen Dutzenden von Flavors: karl-voit.at/2025/08/17/Markdo

    Weil meine Frau was gegen #Emacs #Orgmode hat(te), habe ich ihr notgedrungen #logseq mit #orgdown (Org-mode Syntax) aufgesetzt. Leider bereue ich das inzwischen massiv, da das logseq orgdown in dieser Form in Org-mode nicht direkt nachnutzbar ist: karl-voit.at/2024/01/28/logseq

    Die DB-Version werden wir garantiert nicht mitmachen.

    Entweder ich migriere meine Frau gleich nach Org-mode (IMO das Beste am Markt karl-voit.at/orgmode/) oder ich schaue mir mal #SilverBullet an. Die sind wenigstens sehr offen mit den #MD-Einschränkungen: silverbullet.md/Markdown

    Insofern ein klassisches Beispiel von "Klartextdateien aber trotzdem #lockin". 😔

    Mir war's wenigstens bewusst, hab das Risiko akzeptiert und bin leider damit nach relativ kurzer Zeit eingefahren. Wird mir eine Lehre sein.

    #PKM #PIM

  6. @miXsed Vorsicht: lesbar bedeutet nicht, dass man es mit Tools gut weiterverwenden kann. Gerade #Markdown hat hier ein massives Problem mit den vielen Dutzenden von Flavors: karl-voit.at/2025/08/17/Markdo

    Weil meine Frau was gegen #Emacs #Orgmode hat(te), habe ich ihr notgedrungen #logseq mit #orgdown (Org-mode Syntax) aufgesetzt. Leider bereue ich das inzwischen massiv, da das logseq orgdown in dieser Form in Org-mode nicht direkt nachnutzbar ist: karl-voit.at/2024/01/28/logseq

    Die DB-Version werden wir garantiert nicht mitmachen.

    Entweder ich migriere meine Frau gleich nach Org-mode (IMO das Beste am Markt karl-voit.at/orgmode/) oder ich schaue mir mal #SilverBullet an. Die sind wenigstens sehr offen mit den #MD-Einschränkungen: silverbullet.md/Markdown

    Insofern ein klassisches Beispiel von "Klartextdateien aber trotzdem #lockin". 😔

    Mir war's wenigstens bewusst, hab das Risiko akzeptiert und bin leider damit nach relativ kurzer Zeit eingefahren. Wird mir eine Lehre sein.

    #PKM #PIM

  7. @miXsed Vorsicht: lesbar bedeutet nicht, dass man es mit Tools gut weiterverwenden kann. Gerade #Markdown hat hier ein massives Problem mit den vielen Dutzenden von Flavors: karl-voit.at/2025/08/17/Markdo

    Weil meine Frau was gegen #Emacs #Orgmode hat(te), habe ich ihr notgedrungen #logseq mit #orgdown (Org-mode Syntax) aufgesetzt. Leider bereue ich das inzwischen massiv, da das logseq orgdown in dieser Form in Org-mode nicht direkt nachnutzbar ist: karl-voit.at/2024/01/28/logseq

    Die DB-Version werden wir garantiert nicht mitmachen.

    Entweder ich migriere meine Frau gleich nach Org-mode (IMO das Beste am Markt karl-voit.at/orgmode/) oder ich schaue mir mal #SilverBullet an. Die sind wenigstens sehr offen mit den #MD-Einschränkungen: silverbullet.md/Markdown

    Insofern ein klassisches Beispiel von "Klartextdateien aber trotzdem #lockin". 😔

    Mir war's wenigstens bewusst, hab das Risiko akzeptiert und bin leider damit nach relativ kurzer Zeit eingefahren. Wird mir eine Lehre sein.

    #PKM #PIM

  8. @miXsed Vorsicht: lesbar bedeutet nicht, dass man es mit Tools gut weiterverwenden kann. Gerade #Markdown hat hier ein massives Problem mit den vielen Dutzenden von Flavors: karl-voit.at/2025/08/17/Markdo

    Weil meine Frau was gegen #Emacs #Orgmode hat(te), habe ich ihr notgedrungen #logseq mit #orgdown (Org-mode Syntax) aufgesetzt. Leider bereue ich das inzwischen massiv, da das logseq orgdown in dieser Form in Org-mode nicht direkt nachnutzbar ist: karl-voit.at/2024/01/28/logseq

    Die DB-Version werden wir garantiert nicht mitmachen.

    Entweder ich migriere meine Frau gleich nach Org-mode (IMO das Beste am Markt karl-voit.at/orgmode/) oder ich schaue mir mal #SilverBullet an. Die sind wenigstens sehr offen mit den #MD-Einschränkungen: silverbullet.md/Markdown

    Insofern ein klassisches Beispiel von "Klartextdateien aber trotzdem #lockin". 😔

    Mir war's wenigstens bewusst, hab das Risiko akzeptiert und bin leider damit nach relativ kurzer Zeit eingefahren. Wird mir eine Lehre sein.

    #PKM #PIM

  9. @miXsed Vorsicht: lesbar bedeutet nicht, dass man es mit Tools gut weiterverwenden kann. Gerade #Markdown hat hier ein massives Problem mit den vielen Dutzenden von Flavors: karl-voit.at/2025/08/17/Markdo

    Weil meine Frau was gegen #Emacs #Orgmode hat(te), habe ich ihr notgedrungen #logseq mit #orgdown (Org-mode Syntax) aufgesetzt. Leider bereue ich das inzwischen massiv, da das logseq orgdown in dieser Form in Org-mode nicht direkt nachnutzbar ist: karl-voit.at/2024/01/28/logseq

    Die DB-Version werden wir garantiert nicht mitmachen.

    Entweder ich migriere meine Frau gleich nach Org-mode (IMO das Beste am Markt karl-voit.at/orgmode/) oder ich schaue mir mal #SilverBullet an. Die sind wenigstens sehr offen mit den #MD-Einschränkungen: silverbullet.md/Markdown

    Insofern ein klassisches Beispiel von "Klartextdateien aber trotzdem #lockin". 😔

    Mir war's wenigstens bewusst, hab das Risiko akzeptiert und bin leider damit nach relativ kurzer Zeit eingefahren. Wird mir eine Lehre sein.

    #PKM #PIM

  10. @sysedit As the president of #orgdown, I can only do so much.

    It's dependency on the Org-mode community is obvious - so the community should be president. And this is mixed up with the tooling side of the topic.

    Related to the syntax side, my wishes are summarized on gitlab.com/publicvoit/orgdown/

    Also karl-voit.at/2025/08/17/Markdo where I tried not only to explain the issues with #Markdown but also suggest that the syntax of #Orgmode should be used more often to avoid all the current issues with #MD. My suggestion.

    I'd urge #pypi to support orgdown for README files.

    I'd urge the AI bubble to adapt orgdown for their tool chains instead of MD. There are many cool tools that freshly start with the MD blind alley.

    I'd generally urge all the people to prefer orgdown-based workflows in general in particular for current non-text-based workflows. It empowers them. It enables people to adapt workflows and control what happens to their data and it's necessary to avoid #lockin situations.

  11. @sysedit As the president of #orgdown, I can only do so much.

    It's dependency on the Org-mode community is obvious - so the community should be president. And this is mixed up with the tooling side of the topic.

    Related to the syntax side, my wishes are summarized on gitlab.com/publicvoit/orgdown/

    Also karl-voit.at/2025/08/17/Markdo where I tried not only to explain the issues with #Markdown but also suggest that the syntax of #Orgmode should be used more often to avoid all the current issues with #MD. My suggestion.

    I'd urge #pypi to support orgdown for README files.

    I'd urge the AI bubble to adapt orgdown for their tool chains instead of MD. There are many cool tools that freshly start with the MD blind alley.

    I'd generally urge all the people to prefer orgdown-based workflows in general in particular for current non-text-based workflows. It empowers them. It enables people to adapt workflows and control what happens to their data and it's necessary to avoid #lockin situations.

  12. @sysedit As the president of #orgdown, I can only do so much.

    It's dependency on the Org-mode community is obvious - so the community should be president. And this is mixed up with the tooling side of the topic.

    Related to the syntax side, my wishes are summarized on gitlab.com/publicvoit/orgdown/

    Also karl-voit.at/2025/08/17/Markdo where I tried not only to explain the issues with #Markdown but also suggest that the syntax of #Orgmode should be used more often to avoid all the current issues with #MD. My suggestion.

    I'd urge #pypi to support orgdown for README files.

    I'd urge the AI bubble to adapt orgdown for their tool chains instead of MD. There are many cool tools that freshly start with the MD blind alley.

    I'd generally urge all the people to prefer orgdown-based workflows in general in particular for current non-text-based workflows. It empowers them. It enables people to adapt workflows and control what happens to their data and it's necessary to avoid #lockin situations.

  13. @sysedit As the president of #orgdown, I can only do so much.

    It's dependency on the Org-mode community is obvious - so the community should be president. And this is mixed up with the tooling side of the topic.

    Related to the syntax side, my wishes are summarized on gitlab.com/publicvoit/orgdown/

    Also karl-voit.at/2025/08/17/Markdo where I tried not only to explain the issues with #Markdown but also suggest that the syntax of #Orgmode should be used more often to avoid all the current issues with #MD. My suggestion.

    I'd urge #pypi to support orgdown for README files.

    I'd urge the AI bubble to adapt orgdown for their tool chains instead of MD. There are many cool tools that freshly start with the MD blind alley.

    I'd generally urge all the people to prefer orgdown-based workflows in general in particular for current non-text-based workflows. It empowers them. It enables people to adapt workflows and control what happens to their data and it's necessary to avoid #lockin situations.

  14. @sysedit As the president of #orgdown, I can only do so much.

    It's dependency on the Org-mode community is obvious - so the community should be president. And this is mixed up with the tooling side of the topic.

    Related to the syntax side, my wishes are summarized on gitlab.com/publicvoit/orgdown/

    Also karl-voit.at/2025/08/17/Markdo where I tried not only to explain the issues with #Markdown but also suggest that the syntax of #Orgmode should be used more often to avoid all the current issues with #MD. My suggestion.

    I'd urge #pypi to support orgdown for README files.

    I'd urge the AI bubble to adapt orgdown for their tool chains instead of MD. There are many cool tools that freshly start with the MD blind alley.

    I'd generally urge all the people to prefer orgdown-based workflows in general in particular for current non-text-based workflows. It empowers them. It enables people to adapt workflows and control what happens to their data and it's necessary to avoid #lockin situations.

  15. A quotation from John Scalzi

    Rich people show their appreciation through favors. When everyone you know has more money than they know what to do with, money stops being a useful transactional tool. So instead you offer favors. Deals. Quid pro quos. Things that involve personal involvement rather than money. Because when you’re that rich, your personal time is your limiting factor.

    John Scalzi (b. 1969) American writer
    Lock In, ch. 3 [Shane] (2014)

    More about this quote: wist.info/scalzi-john/35293/

    #quote #quotes #quotation #qotd #scalzi #johnscalzi #lockin #cost #deal #exchange #favor #involvement #money #onepercent #price #quidproquo #rich #service #transaction #wealth #wealthy

  16. @Linux_in_a_Bit Yes!

    And this is why I'm involved with #LinuxCafé, #Linux #installparties, #Linuxdays, #diday ... events, giving #PIM lectures and talks and hopefully publishing a book on how to organize yourself and your data some day.

    To me, it's all one common topic:
    Helping people to help themselves without #lockin effects.

    #Graz #digitalsovereignty #FOSS #education

  17. I've been only able to read this IT note today due to band with constraints. It read like a Stephen King short. Horrific!

    IMHO, In my humble opinion, the company involved used tactics that I can describe as blatantly criminal.

    I have some stories and I may talk about one in another post, using similar of obfuscation techniques

    You would be wise to read this story at least twice.

    Read between the lines.

    Observe that the company was selling open source services yet used criminal tactics to keep people locked in

    Link

    it-notes.dragas.net/2025/10/08

    #Story #Stefano #horrible #ethics #unethical #OpenSource #programming #vendor #lockin

  18. @iammannyj I looked into not too long ago. What dissuaded me most was their . I avoid whenever possible. That said, it’s an interesting write-up.

  19. #Microsoft nennt es "Vereinheitlichung".

    Die Auswirkung ist, dass sehr viele Firmen nun noch mehr Lizenzkosten an Microsoft überweisen.

    derstandard.at/story/300000028

    Weniger know-how bei uns in den Firmen. Mehr Geldexport nach Übersee. Weniger #digitaleSouveränität. Mehr Abhängigkeit. Mehr Datenabfluss in die #Cloud. Mehr #lockin.

    Der Risikoappettit der Entscheider muss ja beinahe unendlich groß sein ... 🤷

    Hoffentlich gibt's hierzulande auch mal ein Nachrechnen und Risikoabschätzungen, sodass langfristig planende Entscheider mehr und mehr sich am Beispiel Italien, Frankreich und Dänemark orientieren und Microsoft adieu sagen, um mehr Kontrolle in finanzieller als auch technischer Art zu bekommen. Nebenbei auch von #Ransomware als Risiko vermehrt wegzukommen.

    #EA #MSPA #Microsoft365 #M365 #Windows365 #Dynamics365

  20. #Markdown Is a Disaster: Why and What to Do Instead
    karl-voit.at/2025/08/17/Markdo

    Here's my article where I summarize the subtle and no so subtle downsides when you choose Markdown for your information instead of a different markup syntax that doesn't come with all the downsides of #MD.

    #publicvoit #orgdown #orgmode #LML #pandoc #rst #restructuredtext #asciidoc #Wikitext #BBCode #Creole #Crossmark #Djot #CommonMark #lockin

  21. @tschenkel @lproven

    Yes, it is: karl-voit.at/2017/09/23/orgmod

    However, I'll publish at least 2 articles over the next weeks that summarize the issues and #lockin effects of #Markdown.

    The solution is not just #orgdown but any lightweight markup language (#LML) that lacks the downsides of Markdown: heavy fragmentation, too many issues when processed via tools, inconsistent design, hard to learn and type, ...

    Orgdown is just one of many candidates. 🙇

    (IMO the best but that's open to subjective opinion.)

  22. Tutanota — это такой сервис, который вроде как про приватность, но по факту больше про то, чтобы ты ни с кем не мог нормально взаимодействовать. Забудьте про SMTP и IMAP, это слишком небезопасно по их версии реальности. Поэтому подключить почту к своему клиенту? Нет. Сделать рассылку с CRM? Нет. Перенести архив писем на другую платформу? Ну-у-у… теоретически когда-нибудь. Зато внутри своего уютного гетто всё шифруется насмерть, а если вы хотите написать внешнему миру, то собеседник должен пройти квест с паролями и временными ссылками. Очень удобно, да. И да, сервера строго в Германии, потому что если уж быть заложником системы, то хотя бы с немецким паспортом. Tutanota — это не «почта нового поколения», это скорее почта без почты. Без протоколов, без совместимости, без вариантов. Полностью безопасно, потому что полностью изолировано. Лучше сразу голубями, там хотя бы SMTP не нужен.

    #Tutanota #Email #Privacy #SecureButUseless #NoSMTP #NoIMAP #LockIn #TechRant #Encryption #DigitalPrivacy #Germany #EmailClients #WalledGarden #PrivacyMyth #UserExperience #EmailGatekeeping #BetterUsePigeons #ModernTech #PrivacyForWho #GDRPApprovedPigeons mastodon.social/@Tutanota/1111

  23. Of course, if you do have long-time plans for your personal #knowledgemanagement, you should not use proprietary tools like #Obsidian, #OneNote, #Evernote and alike.

    You also should think of switching to a much better (learnability, portability/compatibility, typobility, logic, featureset) markup syntax like #orgdown which is used in #Emacs #Orgmode (among other tools).

    But if you start with Org-mode, you need to know the right way of doing it, as so many web pages recommend. Here's my take:

    #UOMF: The Right Way to Use #OrgMode
    karl-voit.at/2021/08/30/the-or

    ad syntax/Markdown/Orgdown/#LML: karl-voit.at/2017/09/23/orgmod

    A specific blog post about the #lockin effects of Obsidian and Co (despite using some tool-specific flavor of MD) is in the making. (Please don't start a religious discussion here.)

    #publicvoit #PIM #PKM

  24. Abhängigkeit von USA und China: Deutsche #Wirtschaft will #digitaleSouveränität heise.de/news/Abhaengigkeit-vo

    Oh, ich bin mir sicher, dass sie das möchte. Allerdings wird sie genauso wie in der #EU allgemein vor den notwendigen teuren und sehr langfristigen Maßnahmen wieder zurückschrecken - wie immer, wenn's d'rauf ankommt. 😔

    Nennt mir bitte ein Gegenbeispiel, wo wir unserer verlorene digitale Eigenständigkeit wesentlich(!) zurückerlangt haben. 🤔

    Dabei wäre es soooo wichtig für sehr viele kommende Generationen. Wir verlieren schon seit zu vielen Jahren massiv #KnowHow durch #Outsourcing, #Cloud, usw..

    #lockin #hardware

  25. Just dusted off my newsletter to publish a proposal for the glut of consumer AI we're seeing now, with a simple proposal:

    Build as much AI as you would like into your products, but do so in a way that allows users to bring their own AIs, instead of being forced to use the platforms':

    notesfromthevoid.cc/p/consumer

    #GenerativeAI #Enshittfication #LockIn #ConsumerChoice #UserControl #Antitrust #ArtificialIntelligence #LargeLanguageModels #Android #GoogleIO

  26. #AI and the Evolution of #SocialMedia
    There is a lot we can learn about social media’s #unregulated evolution over the past decade that directly applies to AI companies and technologies. These lessons can help us avoid making the same mistakes with AI that we did with social media.
    1, #Advertising
    2. #Surveillance
    3. #Virality
    4. #LockIn
    5. #Monopoly
    schneier.com/blog/archives/202

  27. #Ofcom has asked #CMA to investigate #Microsoft and #Amazon’s dominance of #cloud computing

    It's great that Competitions and Markets Authority will look at this

    I also wonder about the breadth of the problem of #lockin

    What else is happening when organisations are locked-in?

    For instance, when #Research, #dev staff have to use the cloud provider's tools without technical support or when that support turns out to be a sales pitch.

    I'm seeing #burnout, I've experienced #burnout. How widespread is this in organisations using #CloudProviders?

    theguardian.com/business/2023/
    ft.com/content/51253c21-4cfb-4

    #IntellectualMonopoly #Capitalism #Technology #IaaS #BigTech #AI #DigitalEconomy