<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Internet on Ulveon's Thoughts</title><link>https://ulveon-thoughts-f210db.gitlab.io/category/internet/</link><description>Recent content in Internet on Ulveon's Thoughts</description><generator>Hugo</generator><language>en-IE</language><lastBuildDate>Fri, 12 Dec 2025 20:00:00 +0100</lastBuildDate><atom:link href="https://ulveon-thoughts-f210db.gitlab.io/category/internet/index.xml" rel="self" type="application/rss+xml"/><item><title>Adventures with vibe-coding: TLD racketeering</title><link>https://ulveon-thoughts-f210db.gitlab.io/p/2025-12-12-adventures-with-vibe-coding-tld-racketeering/</link><pubDate>Fri, 12 Dec 2025 20:00:00 +0100</pubDate><guid>https://ulveon-thoughts-f210db.gitlab.io/p/2025-12-12-adventures-with-vibe-coding-tld-racketeering/</guid><description>&lt;aside class="notice notice--warning" aria-label="Warning notice"&gt;
 &lt;div class="notice__content"&gt;
 Disclaimer: This post isn&amp;rsquo;t really about vibe-coding or AI-assisted coding; it&amp;rsquo;s about the domain name system, WHOIS, and how modern TLD operators have recreated the same domain-squatting problem we spent decades trying to get rid of.
 &lt;/div&gt;
&lt;/aside&gt;

&lt;p&gt;While vibe-coding a small tool to hunt for interesting domain names, I stumbled into something I didn&amp;rsquo;t expect, and, honestly, something a bit worrying.&lt;/p&gt;</description></item><item><title>Vanguard (Part 1): Telegram raid protection</title><link>https://ulveon-thoughts-f210db.gitlab.io/p/2025-08-09-vanguard-part-1-telegram-raid-protection/</link><pubDate>Sat, 09 Aug 2025 00:00:00 +0000</pubDate><guid>https://ulveon-thoughts-f210db.gitlab.io/p/2025-08-09-vanguard-part-1-telegram-raid-protection/</guid><description>&lt;p&gt;I&amp;rsquo;ve been developing Vanguard over the past few months. Initially it was little more than a hack, which was developed quickly and without much consideration regarding the cleanliness of the code. I needed a way to have public Telegram links without the risk of raids, or getting botted.&lt;/p&gt;</description></item><item><title>Effective security beyond encryption</title><link>https://ulveon-thoughts-f210db.gitlab.io/p/2025-05-25-effective-security-beyond-encryption/</link><pubDate>Sun, 25 May 2025 00:00:00 +0000</pubDate><guid>https://ulveon-thoughts-f210db.gitlab.io/p/2025-05-25-effective-security-beyond-encryption/</guid><description>&lt;p&gt;To highly technical audiences, it is unsurprising that Telegram is not cryptographically secure and that Signal is much better.&lt;/p&gt;
&lt;p&gt;Numerous security experts have pointed out that Telegram&amp;rsquo;s reputation as a secure messenger is primarily a result of its marketing rather than its technical architecture.&lt;/p&gt;</description></item><item><title>Software toggles are evil</title><link>https://ulveon-thoughts-f210db.gitlab.io/p/2025-05-13-software-toggles-are-evil/</link><pubDate>Tue, 13 May 2025 00:00:00 +0000</pubDate><guid>https://ulveon-thoughts-f210db.gitlab.io/p/2025-05-13-software-toggles-are-evil/</guid><description>&lt;p&gt;&amp;ldquo;Do not sell my personal information&amp;rdquo;, &amp;ldquo;Reject all cookies&amp;rdquo;, &amp;ldquo;Do not show me personalised ads&amp;rdquo;, &amp;ldquo;Do not use my Maps activity for improvements&amp;rdquo;, &amp;ldquo;Do not store my voice recordings&amp;rdquo;, &amp;ldquo;Permanently delete my account&amp;rdquo;&lt;/p&gt;</description></item><item><title>Operational Security: Staying safe online</title><link>https://ulveon-thoughts-f210db.gitlab.io/p/2024-10-05-operational-security-staying-safe-online/</link><pubDate>Sat, 05 Oct 2024 23:39:19 +0100</pubDate><guid>https://ulveon-thoughts-f210db.gitlab.io/p/2024-10-05-operational-security-staying-safe-online/</guid><description>&lt;p&gt;The Internet is a dangerous place. Especially if you are LGBTQ, furry, have unconventional sexual tendencies (CNC, BDSM, FinDom, etc) or are a member of a religious or racial minority group.&lt;/p&gt;
&lt;p&gt;The Internet was not designed with safety or security in mind. In its ARPANET beginnings, many systems didn&amp;rsquo;t even have passwords because only privileged users were supposed to access them. As such, privacy and security features are often little more than layers added on top of aging protocols, like HTTPS is just SSL applied on top of HTTP.&lt;/p&gt;</description></item><item><title>Nobody is going to shut down Telegram</title><link>https://ulveon-thoughts-f210db.gitlab.io/p/2024-08-25-nobody-is-going-to-shut-down-telegram/</link><pubDate>Sun, 25 Aug 2024 15:10:16 +0100</pubDate><guid>https://ulveon-thoughts-f210db.gitlab.io/p/2024-08-25-nobody-is-going-to-shut-down-telegram/</guid><description>&lt;p&gt;At the time of writing, Pavel Durov, the founder of Telegram was &lt;a href="https://www.reuters.com/world/europe/telegram-messaging-app-ceo-pavel-durov-arrested-france-tf1-tv-says-2024-08-24/"&gt;arrested by French authorities&lt;/a&gt; [&lt;a href="https://archive.is/20240825062334/https://www.reuters.com/world/europe/telegram-messaging-app-ceo-pavel-durov-arrested-france-tf1-tv-says-2024-08-24/"&gt;archived version&lt;/a&gt;].&lt;/p&gt;
&lt;p&gt;As usual, a flurry of theories and panic ensued. I want to give my opinion on what&amp;rsquo;s going to happen next. At this time, I don&amp;rsquo;t believe Telegram is in any significant danger. Of course, things could change, but there&amp;rsquo;s absolutely no reason to panic right now.&lt;/p&gt;</description></item></channel></rss>