@networkpro/blog 1.5.4 → 1.5.5

package/.github/workflows/build-and-deploy.yml

@@ -40,7 +40,7 @@ jobs:
       - name: Set up Node.js
         uses: actions/setup-node@v6
         with:
-          node-version: 22
+          node-version: 24
           cache: npm
           cache-dependency-path: package-lock.json
 
@@ -60,6 +60,7 @@ jobs:
         uses: actions/setup-python@v6
         with:
           python-version-file: .python-version
+          cache: 'pip'
 
       - name: Install Python dependencies
         run: pip install -r requirements.txt

package/.github/workflows/publish-test.yml

@@ -36,7 +36,7 @@ jobs:
       - name: Set up Node.js
         uses: actions/setup-node@v6
         with:
-          node-version: 22
+          node-version: 24
           cache: npm
           cache-dependency-path: package-lock.json
 
@@ -53,6 +53,7 @@ jobs:
         uses: actions/setup-python@v6
         with:
           python-version-file: .python-version
+          cache: 'pip'
 
       - name: Install Python dependencies
         run: pip install -r requirements.txt
@@ -95,7 +96,7 @@ jobs:
       - name: Set up Node.js for npmjs
         uses: actions/setup-node@v6
         with:
-          node-version: 22
+          node-version: 24
           registry-url: https://registry.npmjs.org/
           cache: npm
 
@@ -143,7 +144,7 @@ jobs:
       - name: Set up Node.js for GPR
         uses: actions/setup-node@v6
         with:
-          node-version: 22
+          node-version: 24
           registry-url: https://npm.pkg.github.com/
           cache: npm
 

package/.github/workflows/publish.yml

@@ -38,7 +38,7 @@ jobs:
       - name: Set up Node.js
         uses: actions/setup-node@v6
         with:
-          node-version: 22
+          node-version: 24
           cache: npm
           cache-dependency-path: package-lock.json
 
@@ -55,6 +55,7 @@ jobs:
         uses: actions/setup-python@v6
         with:
           python-version-file: .python-version
+          cache: 'pip'
 
       - name: Install Python dependencies
         run: pip install -r requirements.txt
@@ -97,7 +98,7 @@ jobs:
       - name: Set up Node.js for npmjs
         uses: actions/setup-node@v6
         with:
-          node-version: 22
+          node-version: 24
           registry-url: https://registry.npmjs.org/
           cache: npm
           cache-dependency-path: package-lock.json
@@ -115,24 +116,6 @@ jobs:
           git config --global user.email "github@sl.neteng.cc"
           git config --global user.name "SunDevil311"
 
-      #- name: Print npm config and registry info
-      #  run: |
-      #    echo "🔍 NPM registry (from config):"
-      #    npm config get registry
-
-      #    echo "🔍 NPM user config location:"
-      #    echo "$NPM_CONFIG_USERCONFIG"
-
-      #    echo "🔍 .npmrc contents:"
-      #    cat "$NPM_CONFIG_USERCONFIG" || echo "❌ No .npmrc found"
-      #  env:
-      #    NODE_AUTH_TOKEN: ${{ secrets.NPM_NETPRO }}
-
-      #- name: Verify npm authentication
-      #  run: npm whoami
-      #  env:
-      #    NODE_AUTH_TOKEN: ${{ secrets.NPM_NETPRO }}
-
       - name: Publish package to npmjs
         run: npm publish --access public
         env:
@@ -158,7 +141,7 @@ jobs:
       - name: Set up Node.js for GPR
         uses: actions/setup-node@v6
         with:
-          node-version: 22
+          node-version: 24
           registry-url: https://npm.pkg.github.com/
           cache: npm
           cache-dependency-path: package-lock.json
@@ -180,24 +163,6 @@ jobs:
         run: |
           sed -i 's/"name": "[^"]*"/"name": "@netwk-pro\/blog"/' package.json
 
-      #- name: Print npm config and registry info
-      #  run: |
-      #    echo "🔍 NPM registry (from config):"
-      #    npm config get registry
-
-      #    echo "🔍 NPM user config location:"
-      #    echo "$NPM_CONFIG_USERCONFIG"
-
-      #    echo "🔍 .npmrc contents:"
-      #    cat "$NPM_CONFIG_USERCONFIG" || echo "❌ No .npmrc found"
-      #  env:
-      #    NODE_AUTH_TOKEN: ${{ secrets.NWPRO_GPR }}
-
-      #- name: Verify npm authentication
-      #  run: npm whoami --registry=https://npm.pkg.github.com/
-      #  env:
-      #    NODE_AUTH_TOKEN: ${{ secrets.NWPRO_GPR }}
-
       - name: Publish package to GPR
         run: npm publish --registry=https://npm.pkg.github.com/
         env:

package/.python-version

@@ -1 +1 @@
-3.13
+3.14

package/CHANGELOG.md

@@ -16,6 +16,43 @@ formatting may vary.
 
 ---
 
+## [1.5.5] - 2025-11-09
+
+### Added
+
+- Added `src/posts/2025-11-09-privacy-and-security.md`, along with image assets:
+  - `src/img/privacy-security-promo.png`
+  - `src/img/privacy-security-promo.webp`
+- Added `src/posts/2025-11-09-sideloading.md`, along with image assets:
+  - `src/img/sideloading-promo.png`
+  - `src/img/sideloading-promo.webp`
+- Introduced `npm-run-all` devDependency for more efficient linting.
+
+### Changed
+
+- Refactored `src/contributing.md` to accurately reflect the proper method of
+  contributing.
+- Revised emphasis in the **Message authentication codes** section of
+  `/src/posts/secure-secure-shell.md`.
+- Updated CI workflows to utilize **Node.js v24** (LTS):
+  - `build-and-deploy.yml`
+  - `publish-test.yml`
+  - `publish.yml`
+- Revised scripts in `package.json` for more efficient use by utilizing
+  `npm-run-all`.
+- Updated `.python-version` to reflect **Python v3.14**.
+- Bumped project version to `v1.5.5`.
+- Updated **Node.js** dependencies:
+  - `@eslint/js` `^9.38.0` → `^9.39.1`
+  - `@eslint/json` `^0.13.2` → `^0.14.0`
+  - `eslint` `^9.38.0` → `^9.39.1`
+  - `globals` `^16.4.0` → `^16.5.0`
+- Updated **Python** dependencies:
+  - `mkdocs-material` `9.6.22` → `9.6.23`
+  - `mkdocs-rss-plugin` `1.17.4` → `1.17.5`
+
+---
+
 ## [1.5.4] - 2025-10-28
 
 ### Added
@@ -399,7 +436,8 @@ formatting may vary.
 
 <!-- Link references -->
 
-[Unreleased]: https://github.com/netwk-pro/blog/compare/v1.5.4...HEAD
+[Unreleased]: https://github.com/netwk-pro/blog/compare/v1.5.5...HEAD
+[1.5.5]: https://github.com/netwk-pro/blog/releases/tag/v1.5.5
 [1.5.4]: https://github.com/netwk-pro/blog/releases/tag/v1.5.4
 [1.5.3]: https://github.com/netwk-pro/blog/releases/tag/v1.5.3
 [1.5.2]: https://github.com/netwk-pro/blog/releases/tag/v1.5.2

package/cspell.json

@@ -17,9 +17,11 @@
     "Heli",
     "heliboard",
     "homescreen",
+    "issuetrack",
     "lastmod",
     "mkdocs",
     "msauth",
+    "ncurc",
     "neteng",
     "NETPRO",
     "netwk",
@@ -29,6 +31,7 @@
     "otphelper",
     "pozil",
     "robotstxt",
+    "sideloading",
     "sonicwall",
     "Squircle",
     "srcset",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@networkpro/blog",
-  "version": "1.5.4",
+  "version": "1.5.5",
   "description": "The official blog of Network Pro Strategies (Network Pro™).",
   "keywords": [
     "advisory",
@@ -43,21 +43,22 @@
     "lint:fix": "eslint . --ext .mjs,.js,.json,.jsonc --fix",
     "lint:md": "npx markdownlint-cli2 \"**/*.{md,markdown}\" \"#node_modules/**\" \"#build/**\"",
     "lint:css": "npx stylelint \"**/*.css\" --ignore-path .stylelintignore",
-    "lint:all": "npm run lint && npm run lint:md && npm run lint:css && npm run format",
+    "lint:all": "npm-run-all --parallel lint lint:md lint:css --sequential format",
     "checkout": "npm run lint:all",
     "verify": "npm run checkout",
     "upgrade": "npx npm-check-updates -u"
   },
   "devDependencies": {
-    "@eslint/js": "^9.38.0",
-    "@eslint/json": "^0.13.2",
+    "@eslint/js": "^9.39.1",
+    "@eslint/json": "^0.14.0",
     "autoprefixer": "^10.4.21",
     "browserslist": "^4.27.0",
-    "eslint": "^9.38.0",
+    "eslint": "^9.39.1",
     "eslint-config-prettier": "^10.1.8",
-    "globals": "^16.4.0",
+    "globals": "^16.5.0",
     "markdownlint": "^0.39.0",
     "markdownlint-cli2": "^0.18.1",
+    "npm-run-all": "^4.1.5",
     "postcss": "^8.5.6",
     "prettier": "3.6.2",
     "stylelint": "^16.25.0",

package/ref/README.md

@@ -51,7 +51,7 @@ docs/
     blog/               # The directory that all blog content goes into (first blog instance)
         posts/          # the place to put your posts
         author/         # Author profiles
-        .authors.yml    # Author information to be added to posts (shared betwe
+        .authors.yml    # Author information to be added to posts
 ext/                    # Directory that contains code for the custom slugs
 hooks/                  # Directory for a hook that adds social media share buttons
 ```

package/requirements.txt

@@ -1,5 +1,5 @@
 mkdocs==1.6.1
-mkdocs-material==9.6.22
+mkdocs-material==9.6.23
 mkdocs-material-extensions==1.3.1
 mkdocs-get-deps==0.2.0
-mkdocs-rss-plugin==1.17.4
+mkdocs-rss-plugin==1.17.5

package/src/contributing.md

@@ -1,7 +1,7 @@
 ---
 date:
-  created: 2025-06-07
-  updated: 2025-09-23
+  created: 2025-07-05
+  updated: 2025-10-29
 title: Contributing to Network Pro™
 summary:
   Instructions for getting involved and contributing to Network Pro Strategies.
@@ -12,15 +12,28 @@ tags:
   - contributing
 ---
 
-<a name="top"></a>
-
-<sup>[SPDX-License-Identifier](https://spdx.dev/learn/handling-license-info):
+<sup>[SPDX-License-Identifier](https://spdx.dev/learn/handling-license-info/):
 `CC-BY-4.0 OR GPL-3.0-or-later`</sup>
 
+<a name="top"></a>
+
 # 🤝 Contributing to Network Pro Strategies
 
 **Network Pro Strategies**  
-**Effective Date:** September 23, 2025
+**Effective Date:** October 29, 2025
+
+&nbsp;
+
+## Contents
+
+- [Using the Issue Tracker](#issuetrack)
+- [Bug Reports](#bug-reports)
+- [Feature Requests](#feature-requests)
+- [Before You Begin](#before-you-begin)
+- [Dependency Management](#dependency-management)
+- [Pull Requests](#pull-requests)
+- [Coding & Style Notes](#coding)
+- [Legal Notice](#legal)
 
 &nbsp;
 
@@ -33,6 +46,8 @@ respectfully. 🙌
 
 ---
 
+<a name="issuetrack"></a>
+
 ## 🐛 Using the Issue Tracker
 
 Use the [issue tracker](https://github.com/netwk-pro/netwk-pro.github.io/issues)
@@ -48,6 +63,16 @@ for:
 - [GitHub Discussions](https://discuss.neteng.pro)
 - [Discord](https://discord.neteng.pro)
 
+**Please refer to the following documentation before initiating any feature or
+pull requests:**
+
+- [Before You Begin](#before-you-begin)
+- [Dependency Management](#dependency-management)
+
+&nbsp;
+
+<sub>[Back to top](#top)</sub>
+
 ---
 
 <a name="bug-reports"></a>
@@ -57,7 +82,7 @@ for:
 A bug is a clear, reproducible issue in the code. High-quality reports help us
 fix problems faster.
 
-### ✅ A good bug report includes
+### A good bug report includes
 
 - A **descriptive title**
 - Steps to reproduce
@@ -81,6 +106,8 @@ _Example_:
 
 <!-- markdownlint-enable MD042 -->
 
+&nbsp;
+
 <sub>[Back to top](#top)</sub>
 
 ---
@@ -100,6 +127,165 @@ Before posting:
 
 Strong proposals help us prioritize.
 
+&nbsp;
+
+<sub>[Back to top](#top)</sub>
+
+---
+
+<a name="before-you-begin"></a>
+
+## 🧭 Before You Begin
+
+Before opening a pull request, please make sure your environment and commits
+follow the project’s conventions.
+
+### Prerequisites
+
+- **Node.js:** v24.x (LTS)
+- **npm:** v11.x  
+  _(See package.json → `engines` field for exact supported versions.)_
+
+Install dependencies with:
+
+```bash
+cp .env.template .env
+npm ci
+npx playwright install
+```
+
+### Code Style & Linting
+
+This project uses:
+
+- **[Prettier](https://prettier.io)** for formatting
+- **[ESLint](https://eslint.org)** for static analysis
+- **[Vitest](https://vitest.dev)** for testing
+
+Please refer to
+**[Editor Configuration](https://github.com/netwk-pro/netwk-pro.github.io/wiki/Editor-Configuration)**
+in the [Wiki](https://github.com/netwk-pro/netwk-pro.github.io/wiki) for the
+full toolchain.
+
+To ensure consistency, please run:
+
+```bash
+npm run checkout
+```
+
+This will:
+
+- Verify Node and npm versions
+- Run all tests (client + server)
+- Lint and format your code
+- Run SvelteKit’s type and build checks
+
+> ✅ Tip: Run this before committing to catch issues early.  
+> If Prettier check fails, use `npm run format:fix` to correct formatting, then
+> re-run `npm run checkout`.
+
+### Branch Naming Convention
+
+Use clear, consistent names for feature branches:
+
+| Type     | Example                        | Description                    |
+| -------- | ------------------------------ | ------------------------------ |
+| Feature  | `feature/auth0-integration`    | New feature or enhancement     |
+| Fix      | `fix/login-redirect`           | Bug fix or regression          |
+| Chore    | `chore/deps-update`            | Dependency or tooling updates  |
+| Docs     | `docs/contributing-update`     | Documentation-only changes     |
+| Refactor | `refactor/component-structure` | Code cleanup or reorganization |
+
+### Commit Messages
+
+Please use clear, descriptive commit messages.  
+If you prefer a convention, **Conventional Commits** are supported:
+
+```cpp
+type(scope): short description
+
+[optional body]
+```
+
+Examples:
+
+```scss
+fix(auth): handle expired access token
+chore(deps): pin vitest to 3.2.4 for compatibility
+docs(contributing): clarify build process for SvelteKit
+```
+
+&nbsp;
+
+<sub>[Back to top](#top)</sub>
+
+---
+
+<a name="dependency-management"></a>
+
+## 📦 Dependency Management
+
+This project uses
+[`npm-check-updates`](https://github.com/raineorshine/npm-check-updates) (NCU)
+to manage dependency upgrades safely and predictably.
+
+### Configuration
+
+All upgrade rules and exclusions are defined in the root `.ncurc.cjs` file.  
+This configuration ensures we only upgrade compatible dependencies and avoid
+breakage in core tooling.
+
+**Example rules:**
+
+- Only upgrade **production** and **dev** dependencies.
+- Reject potentially breaking tools (e.g., `vitest`, `@vitest/coverage-v8`,
+  `prettier`).
+- Maintain clean, grouped CLI output during upgrade runs.
+
+### 🪄 Commands
+
+| Command                 | Description                                                          |
+| ----------------------- | -------------------------------------------------------------------- |
+| `npm run check:updates` | Lists available dependency updates without modifying `package.json`. |
+| `npm run upgrade`       | Applies safe upgrades using `.ncurc.cjs` rules.                      |
+
+These commands are wrappers around NCU, keeping the behavior consistent across
+environments.
+
+### Rejected Packages
+
+Certain packages are **intentionally pinned** due to breaking changes between
+major versions or ongoing test compatibility work.  
+Do **not manually upgrade** these unless the project maintainer specifically
+approves it.
+
+Commonly pinned packages include:
+
+- `vitest`
+- `@vitest/coverage-v8`
+- `prettier`
+- `jsdom`
+
+If you think one of these can be safely updated, open a discussion issue or
+mention it in your PR description before upgrading.
+
+### Why We Use This Approach
+
+We separate **rules** (in `.ncurc.cjs`) from **presentation** (via npm scripts)
+to keep updates consistent:
+
+- `.ncurc.cjs` defines _what_ can change
+- `npm run upgrade` defines _how_ it’s displayed
+- Contributors don’t need to remember CLI flags or project-specific exclusions
+
+This ensures every update is:
+
+- predictable
+- consistent
+- and easy to review
+
+&nbsp;
+
 <sub>[Back to top](#top)</sub>
 
 ---
@@ -110,22 +296,22 @@ Strong proposals help us prioritize.
 
 Well-scoped, well-documented pull requests are the lifeblood of open-source.
 
-### ⚠️ Ask First
+### Ask First
 
-Before large PRs (new features, refactors, dependency upgrades), please check
-with maintainers first.
+Before starting large PRs (new features, major refactors, or dependency
+upgrades), please open an issue or discussion first to align on approach.
 
-### 📋 Steps
+### Steps
 
-`1.` **Fork the repo & set remotes**:
+`1.` **Fork and clone the repo:**
 
 ```bash
-git clone https://github.com/<your-username>/blog.git
-cd blog
-git remote add upstream https://github.com/netwk-pro/blog.git
+git clone https://github.com/<your-username>/netwk-pro.github.io.git
+cd netwk-pro.github.io
+git remote add upstream https://github.com/netwk-pro/netwk-pro.github.io.git
 ```
 
-`2.` **Stay Updated**
+`2.` **Stay up to date with upstream:**
 
 ```bash
 git checkout master
@@ -135,74 +321,125 @@ git pull upstream master
 `3.` **Create a topic branch:**
 
 ```bash
-git checkout -b my-feature
+git checkout -b feature/my-feature
 ```
 
-`4.` **Install & test locally:**
+`4.` **Install:**
 
 ```bash
+cp .env.template .env
 npm ci
+npx playwright install
+```
+
+`5.` **Make and commit your changes:**
+
+- Use clear, descriptive commit messages.
+- Group related changes together logically.
+
+`6.` **Test locally:**
+
+```bash
+npm run dev
 npm run checkout
 ```
 
-`5.` **Make your changes**
+`7.` **Do not commit build artifacts.**
 
-(and commit them in logical chunks with good commit messages).
+⚠️ SvelteKit builds are environment-specific and should not be checked into
+source control. The CI/CD pipeline will automatically build, test, and deploy
+your changes.
 
-`6.` **Build:**
+Please **do not commit**:
+
+- `.svelte-kit/`
+- `build/`
+- `node_modules/`
+
+  To ensure your local environment matches CI:
 
 ```bash
 npm run build
-git add build/
-git commit -m "Build: update assets"
 ```
 
-`7.` **Push and open a PR:**
+(This validates your build works, but does not need to be committed.)
+
+`8.` **Push and open your PR:**
 
 ```bash
-git push origin my-feature
+git push origin feature/my-feature
 ```
 
-Open your PR with a clear title, description, and reference the related issue
-(if any).
+`9.` **Open your PR on GitHub:**
+
+- Use a clear title and description.
+- Reference any related issues.
+- Include screenshots or logs if relevant.
+
+---
+
+✅ Tip: Keep your PRs small and focused — it’s easier to review and merge
+quickly.
+
+&nbsp;
 
 <sub>[Back to top](#top)</sub>
 
 ---
 
+<a name="coding"></a>
+
 ## ✅ Coding & Style Notes
 
-- Use the defined code style (Prettier, ESLint, Stylelint, markdownlint)
-- Avoid unrelated changes in the same PR
-- Keep PRs focused and test-covered when appropriate
+- Use the defined code style (Prettier, ESLint, Stylelint, markdownlint).
+- Avoid unrelated changes in the same PR.
+- Keep PRs focused and test-covered when appropriate.
 
 &nbsp;
 
+<a name="legal"></a>
+
 ## 🔐 Legal Notice
 
 By submitting a pull request, you agree to license your contributions under:
 
-- [CC BY 4.0](https://netwk.pro/license#cc-by)
-- [GNU GPL 3.0 or later](https://netwk.pro/license#gnu-gpl)
+- [CC BY 4.0](https://netwk.pro/legal#cc-by)
+- [GNU GPL 3.0 or later](https://netwk.pro/legal#gnu-gpl)
+
+&nbsp;
 
 <sub>[Back to top](#top)</sub>
 
 &nbsp;
 
-_Thanks again for your contribution and for being part of the Network Pro
+_Thanks again for your contribution and for being part of the Network Pro&trade;
 community!_
 
 ---
 
+<span style="font-size: 12px; font-weight: bold; text-align: center;">
+
+[Home](https://netwk.pro) &nbsp; | &nbsp;
+[Terms of Use](https://netwk.pro/terms-of-use)  
+[Privacy Policy](https://netwk.pro/privacy) &nbsp; | &nbsp;
+[Legal](https://netwk.pro/license)
+
+</span>
+
+&nbsp;
+
 <span style="font-size: 12px; text-align: center;">
 
+Copyright &copy; 2025 **[Network Pro Strategies](https://netwk.pro/)** (Network
+Pro&trade;)
+
 Network Pro&trade;, the shield logo, and the "Locking Down Networks...&trade;"
-slogan are [trademarks](https://netwk.pro/license#trademark) of Network Pro
+slogan are [trademarks](https://netwk.pro/legal#trademark) of Network Pro
 Strategies.
 
-Licensed under **[CC BY 4.0](https://creativecommons.org/licenses/by/4.0/)** and
-the **[GNU GPL](https://spdx.org/licenses/GPL-3.0-or-later.html)**, as published
-by the Free Software Foundation, either version 3 of the License, or (at your
-option) any later version.
+Licensed under **[CC BY 4.0](https://netwk.pro/legal#cc-by)** and the
+**[GNU GPL](https://netwk.pro/legal#gnu-gpl)**, as published by the Free
+Software Foundation, either version 3 of the License, or (at your option) any
+later version.
 
 </span>

package/src/posts/2025-11-09-privacy-and-security.md

@@ -0,0 +1,87 @@
+---
+date:
+  created: 2025-11-09
+title: Introducing Our New Privacy & Security Apps & Services Portal
+summary:
+  'In a digital world where personal data has become the new currency,
+  protecting privacy isn’t just a choice — it’s a necessity. That’s why we’re
+  excited to announce the launch of our new site: apps.netwk.pro — your trusted
+  destination for discovering the best tools and services designed to safeguard
+  your digital life.'
+authors:
+  - team
+categories:
+  - Open-Source
+  - Android
+  - Privacy
+  - Security
+tags:
+  - networkpro
+  - website
+  - android
+  - open-source
+  - privacy
+  - security
+---
+
+# Introducing Our New Privacy & Security Apps & Services Portal
+
+In a digital world where personal data has become the new currency, protecting
+privacy isn’t just a choice — it’s a necessity. That’s why we’re excited to
+announce the launch of our new site: [apps.netwk.pro](https://apps.netwk.pro) —
+your trusted destination for discovering the best tools and services designed to
+safeguard your digital life.
+
+<!-- more -->
+
+## 🔐 A Curated Guide to the Best in Privacy & Security
+
+The new portal brings together a hand-picked collection of **privacy and
+security apps for mobile and desktop**, chosen for their proven track records,
+transparency, and technical integrity. From encrypted messaging platforms and
+secure browsers to password managers, VPNs, firewalls, and data-protection
+tools, each recommendation is carefully evaluated for performance and ethical
+standards.
+
+Wherever possible, we prioritize **open-source software** — because true
+security starts with transparency. Open-source projects allow communities to
+verify code integrity, audit vulnerabilities, and ensure that privacy claims are
+backed by evidence, not marketing.
+
+## 📱 Built for Users Who Value Control
+
+At _[apps.netwk.pro](https://apps.netwk.pro)_, you won’t find ad-driven rankings
+or pay-to-play listings. Every featured app or service has been selected through
+technical analysis and real-world testing. Our goal is to help users — from
+everyday consumers to professionals — find tools that respect their data,
+enhance their privacy, and strengthen their security posture across platforms.
+
+Whether you’re looking to **de-Google your phone**, improve your **network
+security**, or discover **FOSS alternatives** to mainstream apps, the site
+provides curated insights, installation guidance, and direct links to trusted
+sources.
+
+## 🌍 A Step Toward Digital Independence
+
+This launch represents our commitment to promoting **digital autonomy** —
+empowering individuals and organizations to take control of their privacy,
+rather than surrendering it to default settings or proprietary ecosystems.
+
+Explore the growing catalog now at [apps.netwk.pro](https://apps.netwk.pro) and
+start building your personal security stack with confidence.
+
+Because in a connected world, **privacy isn’t just protection — it’s freedom**.
+
+Check out the new site:  
+🔗 [apps.netwk.pro](https://apps.netwk.pro)
+
+&nbsp;
+
+<figure class="poster-figure">
+  <picture>
+  <source srcset="/img/privacy-security-promo.webp" type="image/webp" />
+  <img src="/img/privacy-security-promo.png" alt="Introducing Our New Privacy & Security Apps & Services Portal" style="width: 60%; height: 60%">
+  <figcaption>
+  Introducing Our New Privacy & Security Apps & Services Portal – featured visual
+  </figcaption>
+</figure>

package/src/posts/2025-11-09-sideloading.md

@@ -0,0 +1,79 @@
+---
+date:
+  created: 2025-11-09
+title: 'The End of True Sideloading'
+summary:
+  Google’s new restrictions will soon mean only registered apps can be installed
+  on Android. That’s not security — it’s control.
+authors:
+  - team
+categories:
+  - Open-Source
+  - Privacy
+  - Security
+  - Android
+tags:
+  - google
+  - android
+  - sideloading
+  - apps
+  - open-source
+  - privacy
+---
+
+# The End of True Sideloading
+
+## How Google Is Tightening Its Grip on Android
+
+For years, **sideloading** — the ability to install apps outside of official app
+stores — has been one of Android’s defining features. It’s what set the platform
+apart from Apple’s closed ecosystem, giving users the freedom to choose where
+their software comes from and how they use their devices.
+
+<!-- more -->
+
+That freedom, however, is about to change.
+
+According to a
+[recent F-Droid article](https://f-droid.org/en/2025/10/28/sideloading.html),
+Google’s new policies will soon make it impossible to install apps that haven’t
+been pre-approved through its registration systems. In other words, sideloading
+as we know it will be replaced with a **"managed installation"** model — one
+where every app must be part of Google’s controlled ecosystem.
+
+## A Shift From Freedom To Control
+
+This change is being framed as a security improvement, but it raises fundamental
+questions about **digital sovereignty**. If every app has to be “verified”
+through Google’s channels, then users effectively lose the ability to make
+independent decisions about what software they trust or use.
+
+Projects like **F-Droid**, which champion open-source, privacy-respecting apps,
+could be severely impacted. Developers who distribute apps independently —
+outside of Play Store policies or monetization structures — may find themselves
+locked out entirely.
+
+## The Bigger Picture
+
+What’s happening isn’t just about Android. It’s part of a broader industry shift
+toward closed ecosystems and controlled user experiences. By restricting
+sideloading, Google is limiting not only user freedom but also innovation,
+competition, and transparency.
+
+For those who value openness, privacy, and true digital ownership, now is the
+time to pay attention.
+
+As F-Droid emphasizes, sideloading isn’t a loophole — it’s a fundamental right
+of computing freedom. Losing it means ceding more control over our devices,
+data, and choices to corporate gatekeepers.
+
+Read more at the link below:  
+🔗 [f-droid.org/en/2025/10/28/sideloading.html](https://f-droid.org/en/2025/10/28/sideloading.html)
+
+&nbsp;
+
+<figure class="poster-figure">
+  <source srcset="/img/sideloading-promo.webp" type="image/webp" />
+  <img src="/img/sideloading-promo.png" alt="The End of True Sideloading" style="width: 60%; height: 60%;">
+  <figcaption>The End of True Sideloading – featured visual</figcaption>
+</figure>

package/src/posts/secure-secure-shell.md

@@ -1,7 +1,7 @@
 ---
 date:
   created: 2015-01-04
-  updated: 2025-07-27
+  updated: 2025-11-09
 title: Secure Secure Shell
 summary: Secure shell (SSHD) hardening guide.
 authors:
@@ -12,6 +12,7 @@ categories:
 tags:
   - cybersecurity
   - guides
+  - security
 ---
 
 # Secure Secure Shell
@@ -370,18 +371,18 @@ Here are the available MAC choices:
 1. hmac-md5-96
 1. hmac-sha1
 1. hmac-sha1-96
-1. hmac-sha2-256
-1. hmac-sha2-512
+1. **hmac-sha2-256**
+1. **hmac-sha2-512**
 1. umac-64
-1. umac-128
-1. <hmac-md5-etm@openssh.com>
-1. <hmac-md5-96-etm@openssh.com>
-1. <hmac-sha1-etm@openssh.com>
-1. <hmac-sha1-96-etm@openssh.com>
-1. **<hmac-sha2-256-etm@openssh.com>**
-1. **<hmac-sha2-512-etm@openssh.com>**
-1. <umac-64-etm@openssh.com>
-1. <umac-128-etm@openssh.com>
+1. **umac-128**
+1. hmac-md5-etm@openssh.com
+1. hmac-md5-96-etm@openssh.com
+1. hmac-sha1-etm@openssh.com
+1. hmac-sha1-96-etm@openssh.com
+1. **hmac-sha2-256-etm@openssh.com**
+1. **hmac-sha2-512-etm@openssh.com**
+1. umac-64-etm@openssh.com
+1. **umac-128-etm@openssh.com**
 
 The selection considerations: