<?xml version="1.0" encoding="UTF-8"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
    <title></title>
    <link rel="self" type="application/atom+xml" href="https://blog.16px.eu/atom.xml"/>
    <link rel="alternate" type="text/html" href="https://blog.16px.eu"/>
    <generator uri="https://www.getzola.org/">Zola</generator>
    <updated>2026-08-12T00:00:00+00:00</updated>
    <id>https://blog.16px.eu/atom.xml</id>
    <entry xml:lang="en">
        <title>16px.eu is a lot more safer! (and cooler!)</title>
        <published>2026-08-12T00:00:00+00:00</published>
        <updated>2026-08-12T00:00:00+00:00</updated>
        
        <author>
          <name>
            
              Unknown
            
          </name>
        </author>
        
        <link rel="alternate" type="text/html" href="https://blog.16px.eu/posts/safety/"/>
        <id>https://blog.16px.eu/posts/safety/</id>
        
        <content type="html" xml:base="https://blog.16px.eu/posts/safety/">&lt;p&gt;Hey! It&#x27;s been a bit, hasn&#x27;t it? While we were taking a &quot;break&quot; from writing blog posts, we worked tirelessly to implement many features, but the most important ones are of course the ones targetting security.&lt;&#x2F;p&gt;
&lt;p&gt;Running a file uploader service is a difficult endeavour for, in many peoples&#x27; opinions, little reward. I (fzorb) am not one of those people. I am very stubborn. As such, I have decided to go on an adventure of making this as &quot;risk free&quot; as possible while keeping the experience good.&lt;&#x2F;p&gt;
&lt;p&gt;One of the risk-reduction measures in place is the whitelist of approved files for guests, which has mostly worked, however, for a while only the extension was checked, not the actual file contents. As such, anyone who wants to upload whatever could have just changed the extension in the file name.&lt;&#x2F;p&gt;
&lt;h2 id=&quot;a-first-attempt&quot;&gt;A first attempt&lt;&#x2F;h2&gt;
&lt;p&gt;One of the ways you can more accurately check for such files is by checking the file signature. We have used the &lt;a rel=&quot;external&quot; href=&quot;https:&#x2F;&#x2F;pypi.org&#x2F;project&#x2F;fleep&#x2F;&quot;&gt;fleep&lt;&#x2F;a&gt; library in order to achieve this. Unfortunately, this had a lot of innacuracies and we really did need a better solution for this.&lt;&#x2F;p&gt;
&lt;h2 id=&quot;enter-google-s-magika&quot;&gt;Enter Google&#x27;s Magika&lt;&#x2F;h2&gt;
&lt;p&gt;Magika is an AI model which determines the file type based on the file&#x27;s actual contents. It is incredibly lightweight and it is probably the best way to do this at the moment. At a first glance you might think &quot;.. Google Magika uses complex, heavy AI systems instead of... you know... file extensions. ..&quot; &lt;a rel=&quot;external&quot; href=&quot;https:&#x2F;&#x2F;nitter.net&#x2F;LundukeJournal&#x2F;status&#x2F;1989056823144452197&quot;&gt;~ idiotic &quot;journalist&quot;&lt;&#x2F;a&gt;, but it makes sure that the files are actually what they claim to be.&lt;&#x2F;p&gt;
&lt;p&gt;It has genuinely been working extremely well, except for some niche file formats (TempleOS-related) for which we have (temporarily) implemented whitelists.&lt;&#x2F;p&gt;
&lt;h2 id=&quot;but-this-doesn-t-eliminate-all-of-the-risk&quot;&gt;But this doesn&#x27;t eliminate all of the risk&lt;&#x2F;h2&gt;
&lt;p&gt;People can still upload all kinds of illegal material which &lt;strong&gt;must&lt;&#x2F;strong&gt; be moderated, however, it certainly makes the service less and less appealing for circles which spread such appaling materials.&lt;&#x2F;p&gt;
&lt;p&gt;We have a lot more ideas in the back of our heads we want to implement soon, such as file expiration dates and pasting, so stay tuned!&lt;&#x2F;p&gt;
</content>
        
    </entry>
    <entry xml:lang="en">
        <title>Welcome to the 16px.eu blog!</title>
        <published>2026-05-04T00:00:00+00:00</published>
        <updated>2026-05-04T00:00:00+00:00</updated>
        
        <author>
          <name>
            
              Unknown
            
          </name>
        </author>
        
        <link rel="alternate" type="text/html" href="https://blog.16px.eu/posts/welcome/"/>
        <id>https://blog.16px.eu/posts/welcome/</id>
        
        <content type="html" xml:base="https://blog.16px.eu/posts/welcome/">&lt;p&gt;Hello world! Welcome to the 16px.eu blog! From now on, here we will be making the latest announcements regarding our platform.&lt;&#x2F;p&gt;
&lt;p&gt;This is part of the ample redesign we are undergoing. Because this is our first post, we&#x27;ve asked our staff members to introduce themselves:&lt;&#x2F;p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;fzorb&lt;&#x2F;strong&gt;: words words words im chief mouser&lt;&#x2F;li&gt;
&lt;li&gt;&lt;strong&gt;powerpc64&lt;&#x2F;strong&gt;: one two three four five six seven&lt;&#x2F;li&gt;
&lt;li&gt;&lt;strong&gt;tiramisou&lt;&#x2F;strong&gt;: i made the logo while eating chicken&lt;&#x2F;li&gt;
&lt;li&gt;&lt;strong&gt;charli&lt;&#x2F;strong&gt;: the horses compelled me to do it. they know all.&lt;&#x2F;li&gt;
&lt;&#x2F;ul&gt;
&lt;p&gt;We have a lot of things we cannot wait to tell you about, so stay tuned!&lt;&#x2F;p&gt;
</content>
        
    </entry>
</feed>
