Daily posts: Difference between revisions
| Line 36: | Line 36: | ||
| style="padding: 8px; border: 1px solid #ddd;" |Focus Area | | style="padding: 8px; border: 1px solid #ddd;" |Focus Area | ||
|- | |- | ||
| style="padding: 8px; border: 1px solid #ddd;" |Security & Privacy | |||
| style="padding: 8px; border: 1px solid #ddd;" |[[Daily_Post_March_02_2026|Daily Post March 02 2026 - Mailcow]] | | style="padding: 8px; border: 1px solid #ddd;" |[[Daily_Post_March_02_2026|Daily Post March 02 2026 - Mailcow]] | ||
| style="padding: 8px; border: 1px solid #ddd;" |[[Daily_Post_March_03_2026|Daily Post March 03 2026 - ClamAV]] | | style="padding: 8px; border: 1px solid #ddd;" |[[Daily_Post_March_03_2026|Daily Post March 03 2026 - ClamAV]] | ||
| style="padding: 8px; border: 1px solid #ddd;" |[[Daily_Post_March_05_2026|Daily Post March 05 2026 - Manticore Search]] | | style="padding: 8px; border: 1px solid #ddd;" |[[Daily_Post_March_05_2026|Daily Post March 05 2026 - Manticore Search]] | ||
| style="padding: 8px; border: 1px solid #ddd;" |Antivirus Engine | |||
|- | |- | ||
| style="padding: 8px; border: 1px solid #ddd;" |[[Daily_Post_March_06_2026|Daily Post March 06 2026 - LineageOS]] | | style="padding: 8px; border: 1px solid #ddd;" |[[Daily_Post_March_06_2026|Daily Post March 06 2026 - LineageOS]] | ||
Revision as of 01:23, 30 March 2026
| Cost Assessment | Questions?' | Monthly Letter | Monthly Blog | Our Partners |
Email us |TEL: 050-1720-0641 | LinkedIn | English | 日々のブログ | Q & A
2026
March 2026
February 2026
January 2026
2025
December 2025
November 2025
October 2025
September 2025
August 2025
July 2025
June 2025
May 2025
April 2025
March 2025
February 2025
| Daily Post Feb 24 2025 - Debunking | Daily Post Feb 25 2025 - FOSS Solutions | Daily Post Feb 26 2025 - mintarc-Collabora |
日本語の投稿
2026
2026年1月
- スプレッドシートを超えて：ノーコード・データベース「Baserow」徹底解説 1/5/2026
- ハイテク国家の「FAX」と「OSS」：日本の中小企業がオープンソースに抱く違和感の正体 1/6/2026
- 失敗しないためのオープンソース・ライセンス基礎知識 1/7/2026
12月の投稿
- KNIME（ナイム）：データ分析を視覚化するオープンソースプラットフォーム12/1/2025
- Collabora Office、新デスクトップ版を投入：オンラインとオフラインの垣根をなくす12/2/2025
- KumoMTA：コストと信頼性を両立する、アウトバウンドメール配信専用のオープンソースMTA12/4/2025
- Taiga：シンプルさと拡張性を両立した次世代アジャイル・プロジェクト管理ツール12/5/2025
11月の投稿
- 日本のオープンソース（FOSS）の光と影：大企業の牽引と中小企業の孤立11/4/2025
- 日本の小規模ビジネスがDrupalを選ぶべき理由11/6/2025
- Element：安全・分散・相互運用を叶える次世代コミュニケーションツー11/10/2025
10月の投稿
- オープンソースの脆弱性スキャナー OpenVAS：中小企業のセキュリティ強化を支援10/2/2025
- プライバシーを重視した知識管理ツール Logseq：企業での活用とメリット10/3/2025
- Rocket.Chat（ロケット・チャット）：自由度の高いオープンソースのコミュニケーション基盤10/4/2025
- Papra: 軽量で安全なデジタル・アーカイブ10/5/2025
9月の投稿
- pyinfra: Pythonでインフラを自動化するツール 9/1/2025
- Nextcloud Talk: 企業・個人のためのプライバシー重視型コミュニケーションツール 9/5/2025
- Blocky：シンプル、高速、そしてプライバシーを重視したDNSプロキシ9/7/2025
8月の投稿
7月の投稿
- YARA: マルウェア分析の頼れる「スイスナイフ」7/1/2025
- Collabora OfficeとCollabora Online：中小企業のための賢い選択 7/3/2025
- Odooとは？ビジネスを加速する統合型オープンソースERP 7/9/2025
- Matrix: 安全で分散型のコミュニケーションの未来 🌐 7/12/2025
- OpenNebula：柔軟で費用対効果の高いクラウド管理ソリューション 7/13/2025
- NetBird：複雑なVPNはもう不要！ゼロトラストネットワークを簡単に 7/14/2025
6月の投稿
- MediaWiki：共同作業と知識管理のための強力な基盤6/2/2025
- XWiki：コラボレーションと知識管理のためのエンタープライズWikiプラットフォーム6/4/2025
- Clonezilla：ディスククローンとシステム展開のためのオープンソースソリューション6/12/2025
- Apache ECharts：Web向けインタラクティブデータビジュアライゼーションのオープンソースライブラリ6/13/2025
- OpenBoard: 教育現場のためのインタラクティブなホワイトボードアプリケーション6/14/2025
- mintarcが挑む、日本企業のSaaS依存とオープンソースの可能性6/15/2025
- Solr: あなたのウェブサイトやアプリに強力な検索機能をもたらすオープンソースエンジン6/16/2025
- Wazuh：セキュリティを強くするオープンソースの力6/17/2025
5月の投稿
- Nextcloud：自分だけのクラウドを構築できるオープンソースのコラボレーションプラットフォーム 5/7/2025
- プライバシーとデータ所有権：中小企業が知っておくべきこと 5/12/2025
- 中小企業にとってなぜ重要？ウェブブラウザのプライバシー保護 5/14/2025
- AI時代におけるFOSSの力：透明性と責任でリスクを乗り越える 5/20/2025
- Joomla: オープンソースCMSの可能性と中小企業への価値 5/27/2025
- スローガンだけでは見えないFOSSの真価：深く理解し、持続可能なビジネスを築く 5/29/2025
4月の投稿
- 日々の投稿 Post apr 01 2025
- 日々の投稿 Post apr 02 2025
- 中小企業こそ使うべき！無料なのに高機能なマーケティング自動化ツールMautic活用術 Post 4/09/2025
- 日本のオープンソース、大企業の幻想と中小企業の現実：閉ざされた「秘密のクラブ」 4/14/2025
- SaaSの甘い誘惑と隠された罠：データ主権を失うリスクと、真の自律性を取り戻すための選択4/15/2025
- Mautic 6.0 リリース：マーケティング自動化プラットフォームの近代化4/16/2025
- 社長、御社のデータは誰のものですか？～知らないと危ないSaaSの落とし穴～4/22/2025
- 顧客の声、もっとスマートに集めたい？プライバシーも両立するFormbricksという選択肢4/23/2025
- Google Analyticsからの乗り換えも？オープンソースのウェブ解析ツール OWA の実力 4/30/2025
3月の投稿
Answers to Questions
A place for answers to questions we get about the things we post
What is the main difference between FOSS, FLOSS, and OSS
We get this one often, all involve publicly available source code, FOSS (Free and Open Source Software) emphasizes user freedom ("free as in speech"). FLOSS adds "Libre" to clarify that it means liberty, not necessarily zero cost. OSS (Open Source Software) is a broader term that focuses more on the benefits of open development and collaboration rather than the philosophical or ethical parts of user rights.
What are the risks of staying with "Big Tech" SaaS solutions?
This is always a "Prove it to me" questions LOL - Basically the risks include "SaaS Creep" (accumulating unused, subscriptions), lack of data sovereignty, vendor lock-in, and privacy concerns where user data is monetized or mined by the provider. If you as a business do not see that as a risk then its not really a problem.
What is OWASP ZAP and why should a business use it
Its is an open-source web security tool. It acts as a "manipulator-in-the-middle" to find vulnerabilities like SQL injection and Cross-Site Scripting (XSS). It is recommended because it is free, highly customizable, and can be integrated into DevSecOps pipelines.
What is "Shadow IT" and how does FOSS mitigate it?
This is a good one. Because you see it rampant everywhere, so this occurs when employees use unauthorized SaaS apps because they are easier to access than company tools. This creates security gaps. FOSS mitigates this by allowing the company to host its own user-friendly tools (like Listmonk for emails or Matrix for chat) that are managed centrally and securely.
My business runs smoothly on Google services, and I don't currently see a reason to switch. What specific business risks am I ignoring by staying with a proprietary provider rather than exploring Open Source? Is the 'anti-Google' sentiment from FOSS companies based on technical flaws or ideological differences?
The Business Risks You Are "Ignoring"
Even when things are running perfectly, relying on a single proprietary provider creates "silent risks" that don't matter... until they suddenly do.
- The "Price Creep" when a business is deeply integrated into Google (Sheets, Meet, Gmail, Drive, Cloud), the "cost of switching" becomes so high that you effectively lose your bargaining power. If Google increases Workspace prices by 30%, you are forced to pay it because the alternative (migrating years of data) is more expensive than the price hike.
- Data Sovereignty & Jurisdictional Risk the big one for 2026. Even if you are based in Europe or Asia, if you use a US-based provider like Google, your data may be subject to the US CLOUD Act, which allows US authorities to compel disclosure of data held by US companies, regardless of where the server is physically located. For many regulated industries, this is a growing legal liability.
- The "Feature Sunset", Google is notorious for killing products that aren't billion-user successes think aboutit Google Hire, Jamboard, Stadia. If your workflow relies on a specific integration or niche tool within the Google ecosystem, you have zero power to keep it alive if Google decides it’s no longer profitable.
Is anti-Google Technical or Ideological?
- FOSS advocates see Google as a "centralized authority" that goes against the original spirit of the internet (which was meant to be decentralized). To us, informing about what Google does is a way to alert users that they are "digital tenants" rather than "digital owners."
- FOSS companies argue that Google’s code is a "black box." You can’t audit it for security flaws or "backdoors" yourself; you have to take Google's word for it. Many of us FOSS folk believe "given enough eyes, all bugs are shallow" meaning open code is inherently more secure because it can be audited by anyone.
You don't need to quit Google to benefit from Open Source. a "Hybrid Approach"
- Stay on Google Workspace for email and docs because the collaboration is your preference.
- Sensitive Data (Move to FOSS)put your most sensitive client data, internal wikis, or proprietary code to a FOSS tool like Nextcloud or Baserow that you host on your own server.
- Future-Proofing when you are using Open Standards. For example, use standard .csv or .odt formats where possible, so if you ever have to leave Google, your data isn't trapped in a format only they can read.