ai_security
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revision | |||
| ai_security [2026/05/26 00:30] – removed - external edit (Unknown date) 127.0.0.1 | ai_security [2026/05/26 00:30] (current) – ↷ Page name changed from ai-sec to ai_security particles | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | ====== Always Intercepted ====== | ||
| + | I'll keep this one short and sweet: anyone who cares about the fact that [[https:// | ||
| + | |||
| + | If you use any hosted AI model, that data is easily intercepted by the US government or any other government. If you use any app that has integration with an AI model that is on by-default or isn't manually invoked, that is also a risk. | ||
| + | |||
| + | In the past, if you wanted to get access to someone' | ||
| + | |||
| + | Hosted AI models centralize everything: they create massive single points-of-failure *and* single points-of-interception. Sure, you trust the government now, but will you always? What if the government is overthrown? What if it's a foreign government instead? | ||
| + | |||
| + | And what if an AI service provider gets hacked, or has a security vulnerability? | ||
