{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreig3ufltd3wwp42gbxh6eo53utrusealvdh6ncbud2onsxzu73vo5i",
    "uri": "at://did:plc:haakkg7y3xdghcdmprxeexso/app.bsky.feed.post/3mmxvnef5s4h2"
  },
  "path": "/t/is-it-worth-setting-up-my-own-vpn-server-and-what-are-the-possible-use-cases/38217#post_2",
  "publishedAt": "2026-05-29T05:26:44.000Z",
  "site": "https://discuss.privacyguides.net",
  "tags": [
    "Battering RAM"
  ],
  "textContent": "polyester_apricot650:\n\n> It seems like these tools help secure the connection between the client and the server, which is great, but the server still has to connect to the internet.\n\nCorrect, they are typically used for traversing between different internal and external networks.\n\npolyester_apricot650:\n\n> So wouldn’t traffic out of the server could potentially be monitored?\n\nIt is monitored, ISPs have to measure network traffic for billing purposes and acceptable network usage, among others.\n\npolyester_apricot650:\n\n> I guess I could use a secure DNS, but that doesn’t solve everything.\n\nIt solves your DNS queries from being easily eavesdropped on the wire between you and the resolver.\n\npolyester_apricot650:\n\n> Why would anyone do that when they could use Mullvad, where the user can browse privately and securely, and the server is RAM only with no logging?\n\nTrust, either you trust yourself, or someone else, and there are various attacks available against server RAM, such as Battering RAM:\n\nBattering RAM\n\n### Battering RAM\n\nThere are also cold boot attacks, but their effective depends on the generation of the RAM.",
  "title": "Is it worth setting up my own VPN server and what are the possible use cases?"
}