<?xml version="1.0" encoding="UTF-8"?><rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>foss &amp;mdash; Bruno&#39;s ramblings</title>
    <link>https://infosec.press/brunomiguel/tag:foss</link>
    <description>A blog where I ramble about... well... stuff.</description>
    <pubDate>Sat, 30 May 2026 21:57:48 +0000</pubDate>
    <item>
      <title>📝 Is Mozilla trying hard to kill itself?</title>
      <link>https://infosec.press/brunomiguel/is-mozilla-trying-hard-to-kill-itself</link>
      <description>&lt;![CDATA[In an interview with &#34;The Verge&#34;, the new Mozilla CEO, Enzor-DeMeo, IMHO hints that axing adblockers is something that, at the very least, was on the table in some form and at some point. From the article:&#xA;&#xA;  He says he could begin to block ad blockers in Firefox and estimates that’d bring in another $150 million, but he doesn’t want to do that. It feels off-mission.&#xA;&#xA;It may be just me, but I read this as &#34;I don&#39;t want to 😜 😜 but I&#39;ll kill AdBlockers in Firefox for buckerinos 😂&#34;. This disappoints and saddens me a lot, and I hope I&#39;m wrong.&#xA;!--more--&#xA;I&#39;ve been using Firefox before it was called that. Heck, I even used the Mozilla Application Suite back in the day. It was its commitment to open standards and the open web, and its powerful add-on system, that attracted me to its software.&#xA;&#xA;Honestly, that&#39;s what&#39;s been keeping me. I think that&#39;s also what&#39;s been keeping their loyal base of users with the project, the geeks and nerds that care about privacy. It&#39;s the same group of people who helped it get very popular at one point.&#xA;&#xA;Killing one of its advantages over the Chromium engine, being able to have a fucking adblocker that&#39;s actually useful, and that nowadays is a fucking security feature due to malvertising, will be another nail in the coffin, IMHO. The core community will feel disenfranchised, and this may have negative consequences for the project. You know why? Because these are some of the people that the normies turn to when they want tech advice.&#xA;&#xA;For fuck sake, for-profit side of Mozilla, get a damn grip!&#xA;&#xA;Update, since this is getting traction on Reddit&#xA;&#xA;I&#39;m not against Mozilla making money. Like a regular citizen needs to make money, companies and even nonprofits need it too. That&#39;s the world we live in, whether we like it or not.&#xA;&#xA;What bothers me is how the new CEO mentions something that he could do but doesn&#39;t want to. If he doesn&#39;t want to, why say it? It has the potential to cause bad PR, and it has. &#xA;&#xA;Of course, I know I may not be interpreting this correctly.&#xA;&#xA;Right now, I&#39;m on the fence. His statement leads me to believe that the option is still very much on the table; otherwise, he wouldn&#39;t mention it.&#xA;&#xA;#Mozilla #Firefox #AdBlocker #OpenSource #FOSS]]&gt;</description>
      <content:encoded><![CDATA[<p>In an interview with “The Verge”, the new Mozilla CEO, Enzor-DeMeo, IMHO hints that axing adblockers is something that, at the very least, was on the table in some form and at some point. From <a href="https://www.theverge.com/tech/845216/mozilla-ceo-anthony-enzor-demeo" rel="nofollow">the article</a>:</p>

<blockquote><p>He says he could begin to block ad blockers in Firefox and estimates that’d bring in another $150 million, but he doesn’t want to do that. It feels off-mission.</p></blockquote>

<p>It may be just me, but I read this as “I don&#39;t want to 😜 😜 but I&#39;ll kill AdBlockers in Firefox for buckerinos 😂”. This disappoints and saddens me a lot, and I hope I&#39;m wrong.

I&#39;ve been using Firefox before it was called that. Heck, I even used the Mozilla Application Suite back in the day. It was its commitment to open standards and the open web, and its powerful add-on system, that attracted me to its software.</p>

<p>Honestly, that&#39;s what&#39;s been keeping me. I think that&#39;s also what&#39;s been keeping their loyal base of users with the project, the geeks and nerds that care about privacy. It&#39;s the same group of people who helped it get very popular at one point.</p>

<p>Killing one of its advantages over the Chromium engine, being able to have a fucking adblocker that&#39;s actually useful, and that nowadays is a fucking security feature due to malvertising, will be another nail in the coffin, IMHO. The core community will feel disenfranchised, and this may have negative consequences for the project. You know why? Because these are some of the people that the <em>normies</em> turn to when they want tech advice.</p>

<p>For fuck sake, for-profit side of Mozilla, get a damn grip!</p>

<p><strong>Update, since this is getting traction on Reddit</strong></p>

<p>I&#39;m not against Mozilla making money. Like a regular citizen needs to make money, companies and even nonprofits need it too. That&#39;s the world we live in, whether we like it or not.</p>

<p>What bothers me is how the new CEO mentions something that he could do but doesn&#39;t want to. If he doesn&#39;t want to, why say it? It has the potential to cause bad PR, and it has.</p>

<p>Of course, I know I may not be interpreting this correctly.</p>

<p>Right now, I&#39;m on the fence. His statement leads me to believe that the option is still very much on the table; otherwise, he wouldn&#39;t mention it.</p>

<p><a href="/brunomiguel/tag:Mozilla" class="hashtag" rel="nofollow"><span>#</span><span class="p-category">Mozilla</span></a> <a href="/brunomiguel/tag:Firefox" class="hashtag" rel="nofollow"><span>#</span><span class="p-category">Firefox</span></a> <a href="/brunomiguel/tag:AdBlocker" class="hashtag" rel="nofollow"><span>#</span><span class="p-category">AdBlocker</span></a> <a href="/brunomiguel/tag:OpenSource" class="hashtag" rel="nofollow"><span>#</span><span class="p-category">OpenSource</span></a> <a href="/brunomiguel/tag:FOSS" class="hashtag" rel="nofollow"><span>#</span><span class="p-category">FOSS</span></a></p>
]]></content:encoded>
      <guid>https://infosec.press/brunomiguel/is-mozilla-trying-hard-to-kill-itself</guid>
      <pubDate>Wed, 17 Dec 2025 01:25:58 +0000</pubDate>
    </item>
    <item>
      <title>📝 Mozilla might have a tech-bro infestation</title>
      <link>https://infosec.press/brunomiguel/mozilla-might-have-a-tech-bro-infestation</link>
      <description>&lt;![CDATA[I think Mozilla might have a &#39;tech-bro&#39; infestation that also doubles as a &#39;business-bro&#39; infestation. I was skeptical of the latter, but after exchanging a few messages with someone on the Fediverse, I&#39;m inclined to include it, too.&#xA;&#xA;All this nonsense they&#39;ve been doing for a few years now is indicative of this type of infestation:&#xA;&#xA;AI plans;&#xA;buying an Ad company;&#xA;removing info about not selling users&#39; data;&#xA;applying Terms of Service to their distributed Firefox binaries;&#xA;continued Firefox usage decline; &#xA;massive bonuses and/or pay increases for executives;&#xA;all those failed projects, too many to list;&#xA;etc, etc, etc...&#xA;&#xA;It feels like Mozilla is walking back on promises made. What the actual fuck, Mozilla Foundation?&#xA;&#xA;#Mozilla #MozillaFoundation #Firefox #TechBro #FOSS #OpenSource]]&gt;</description>
      <content:encoded><![CDATA[<p>I think Mozilla might have a &#39;tech-bro&#39; infestation that also doubles as a &#39;business-bro&#39; infestation. I was skeptical of the latter, but after exchanging a few messages with someone on the Fediverse, I&#39;m inclined to include it, too.</p>

<p>All this nonsense they&#39;ve been doing for a few years now is indicative of this type of infestation:</p>
<ul><li>AI plans;</li>
<li>buying an Ad company;</li>
<li><a href="https://circumstances.run/@davidgerard/114078708183574404" rel="nofollow">removing</a> info about not selling users&#39; data;</li>
<li>applying Terms of Service to their distributed Firefox binaries;</li>
<li>continued Firefox usage decline;</li>
<li>massive bonuses and/or pay increases for executives;</li>
<li>all those failed projects, too many to list;</li>
<li>etc, etc, etc...</li></ul>

<p>It feels like Mozilla is <a href="https://www.wired.com/2015/12/mozilla-is-flailing-when-the-web-needs-it-the-most/" rel="nofollow">walking</a> back on promises made. What the actual fuck, Mozilla Foundation?</p>

<p><a href="/brunomiguel/tag:Mozilla" class="hashtag" rel="nofollow"><span>#</span><span class="p-category">Mozilla</span></a> <a href="/brunomiguel/tag:MozillaFoundation" class="hashtag" rel="nofollow"><span>#</span><span class="p-category">MozillaFoundation</span></a> <a href="/brunomiguel/tag:Firefox" class="hashtag" rel="nofollow"><span>#</span><span class="p-category">Firefox</span></a> <a href="/brunomiguel/tag:TechBro" class="hashtag" rel="nofollow"><span>#</span><span class="p-category">TechBro</span></a> <a href="/brunomiguel/tag:FOSS" class="hashtag" rel="nofollow"><span>#</span><span class="p-category">FOSS</span></a> <a href="/brunomiguel/tag:OpenSource" class="hashtag" rel="nofollow"><span>#</span><span class="p-category">OpenSource</span></a></p>
]]></content:encoded>
      <guid>https://infosec.press/brunomiguel/mozilla-might-have-a-tech-bro-infestation</guid>
      <pubDate>Fri, 28 Feb 2025 15:57:42 +0000</pubDate>
    </item>
    <item>
      <title>💻 Goodbye, Neofetch, and thanks for all the fish</title>
      <link>https://infosec.press/brunomiguel/goodbye-neofetch-and-thanks-for-all-the-fish</link>
      <description>&lt;![CDATA[Fastfetch custom configuration&#xA;&#xA;Neofetch is no more. The git repository for the venerable tool to show off the users&#39; window manager configurations on /r/unixporn was archived and will no longer be maintained. Granted, it hadn&#39;t received a commit for around 3 years, so this is not unexpected.&#xA;!--more--&#xA;Thankfully, many tools of this kind abound in the FOSS world. One is Fastfetch, which is very similar to Neofetch but supposedly faster. Moments ago, I installed Fastfech and wasted a little bit of time configuring it. Why? Because.&#xA;&#xA;The main difference between the two, from a user point of view, is that JSONC is used for Fastfetch&#39;s configuration. You can see all the options for the built-in modules on the schema present at the tool&#39;s repository or the documentation. You can also use my configuration below as a starting point.&#xA;&#xA;{&#xA;    &#34;$schema&#34;: &#34;https://github.com/fastfetch-cli/fastfetch/raw/dev/doc/jsonschema.json&#34;,&#xA;    &#34;logo&#34;: {&#xA;        &#34;type&#34;: &#34;file&#34;,&#xA;        &#34;source&#34;: &#34;$HOME/.config/fastfetch/logo.txt&#34;&#xA;    },&#xA;    &#34;display&#34;: {&#xA;        &#34;separator&#34;: &#34;  -  &#34;&#xA;    },&#xA;    &#34;modules&#34;: [&#xA;        {&#xA;            &#34;type&#34;: &#34;custom&#34;,&#xA;            &#34;format&#34;: &#34;┌────────────────────────────────────────────────────────────┐&#34;&#xA;        },&#xA;        {&#xA;            &#34;type&#34;: &#34;os&#34;,&#xA;            &#34;key&#34;: &#34;│  OS&#34;&#xA;        },&#xA;        {&#xA;                &#34;type&#34;: &#34;kernel&#34;,&#xA;                &#34;key&#34;: &#34;│  Kernel&#34;&#xA;        },&#xA;        {&#xA;            &#34;type&#34;: &#34;packages&#34;,&#xA;            &#34;key&#34;: &#34;│  Packages&#34;,&#xA;        },&#xA;        {&#xA;            &#34;type&#34;: &#34;wm&#34;,&#xA;            &#34;key&#34;: &#34;│  WM&#34;,&#xA;        },&#xA;        {&#xA;            &#34;type&#34;: &#34;terminal&#34;,&#xA;            &#34;key&#34;: &#34;│  Terminal&#34;,&#xA;        },&#xA;        {&#xA;            &#34;type&#34;: &#34;shell&#34;,&#xA;            &#34;key&#34;: &#34;│  Shell&#34;&#xA;        },&#xA;        {&#xA;            &#34;type&#34;: &#34;display&#34;,&#xA;            &#34;key&#34;: &#34;│  Display&#34;&#xA;        },&#xA;        {&#xA;            &#34;type&#34;: &#34;cpu&#34;,&#xA;            &#34;key&#34;: &#34;│  CPU&#34;,&#xA;        },&#xA;        {&#xA;            &#34;type&#34;: &#34;gpu&#34;,&#xA;            &#34;key&#34;: &#34;│  GPU&#34;,&#xA;        },&#xA;        {&#xA;            &#34;type&#34;: &#34;memory&#34;,&#xA;            &#34;key&#34;: &#34;│  Memory&#34;,&#xA;        },&#xA;        {&#xA;            &#34;type&#34;: &#34;swap&#34;,&#xA;            &#34;key&#34;: &#34;│  Swap&#34;&#xA;        },&#xA;        {&#xA;            &#34;type&#34;: &#34;custom&#34;,&#xA;            &#34;format&#34;: &#34;└────────────────────────────────────────────────────────────┘&#34;&#xA;        },&#xA;        &#34;break&#34;,&#xA;        {&#xA;            &#34;type&#34;: &#34;colors&#34;&#xA;        }&#xA;    ]&#xA;}&#xA;&#xA;If you want something different, there are several options, such as Nitch, Pfetch, Catnip, and Meowfetch. I&#39;m the maintainer for the meowfetch-git package on Arch Linux&#39;s AUR, and I recommend it if you want to see a kitty every time you display your system info on the terminal.&#xA;&#xA;smallvia It&#39;s FOSS/small&#xA;&#xA;#Neofetch #Fastfetch #UnixPorn #Linux #FOSS ]]&gt;</description>
      <content:encoded><![CDATA[<p><img src="https://cld.pt/dl/download/26fcefc2-8b73-40e9-8126-5d4d7c90b81f/584db0621e3091b5.png" alt="Fastfetch custom configuration" title="Fastfetch custom configuration"></p>

<p><a href="https://news.itsfoss.com/neofetch-rip/" rel="nofollow">Neofetch</a> is no more. The git repository for the venerable tool to show off the users&#39; window manager configurations on /r/unixporn was archived and will no longer be maintained. Granted, it hadn&#39;t received a commit for around 3 years, so this is not unexpected.

Thankfully, many tools of this kind abound in the FOSS world. One is <a href="https://github.com/fastfetch-cli/fastfetch" rel="nofollow">Fastfetch</a>, which is very similar to Neofetch but supposedly faster. Moments ago, I installed Fastfech and wasted a little bit of time configuring it. Why? Because.</p>

<p>The main difference between the two, from a user point of view, is that JSONC is used for Fastfetch&#39;s configuration. You can see all the options for the built-in modules on the schema present at the tool&#39;s <a href="https://github.com/fastfetch-cli/fastfetch/blob/dev/doc/json_schema.json" rel="nofollow">repository</a> or the <a href="https://github.com/fastfetch-cli/fastfetch/wiki/Json-Schema" rel="nofollow">documentation</a>. You can also use my configuration below as a starting point.</p>

<pre><code class="language-json">{
    &#34;$schema&#34;: &#34;https://github.com/fastfetch-cli/fastfetch/raw/dev/doc/json_schema.json&#34;,
    &#34;logo&#34;: {
        &#34;type&#34;: &#34;file&#34;,
        &#34;source&#34;: &#34;$HOME/.config/fastfetch/logo.txt&#34;
    },
    &#34;display&#34;: {
        &#34;separator&#34;: &#34;  -&gt; &#34;
    },
    &#34;modules&#34;: [
        {
            &#34;type&#34;: &#34;custom&#34;,
            &#34;format&#34;: &#34;┌────────────────────────────────────────────────────────────┐&#34;
        },
        {
            &#34;type&#34;: &#34;os&#34;,
            &#34;key&#34;: &#34;│  OS&#34;
        },
        {
                &#34;type&#34;: &#34;kernel&#34;,
                &#34;key&#34;: &#34;│  Kernel&#34;
        },
        {
            &#34;type&#34;: &#34;packages&#34;,
            &#34;key&#34;: &#34;│  Packages&#34;,
        },
        {
            &#34;type&#34;: &#34;wm&#34;,
            &#34;key&#34;: &#34;│  WM&#34;,
        },
        {
            &#34;type&#34;: &#34;terminal&#34;,
            &#34;key&#34;: &#34;│  Terminal&#34;,
        },
        {
            &#34;type&#34;: &#34;shell&#34;,
            &#34;key&#34;: &#34;│  Shell&#34;
        },
        {
            &#34;type&#34;: &#34;display&#34;,
            &#34;key&#34;: &#34;│  Display&#34;
        },
        {
            &#34;type&#34;: &#34;cpu&#34;,
            &#34;key&#34;: &#34;│  CPU&#34;,
        },
        {
            &#34;type&#34;: &#34;gpu&#34;,
            &#34;key&#34;: &#34;│  GPU&#34;,
        },
        {
            &#34;type&#34;: &#34;memory&#34;,
            &#34;key&#34;: &#34;│  Memory&#34;,
        },
        {
            &#34;type&#34;: &#34;swap&#34;,
            &#34;key&#34;: &#34;│  Swap&#34;
        },
        {
            &#34;type&#34;: &#34;custom&#34;,
            &#34;format&#34;: &#34;└────────────────────────────────────────────────────────────┘&#34;
        },
        &#34;break&#34;,
        {
            &#34;type&#34;: &#34;colors&#34;
        }
    ]
}

</code></pre>

<p>If you want something different, there are several options, such as Nitch, Pfetch, Catnip, and Meowfetch. I&#39;m the maintainer for the <a href="https://aur.archlinux.org/packages/meowfetch-git" rel="nofollow">meowfetch-git package</a> on Arch Linux&#39;s AUR, and I recommend it if you want to see a kitty every time you display your system info on the terminal.</p>

<p><small>via <a href="https://news.itsfoss.com/neofetch-rip/" rel="nofollow">It&#39;s FOSS</a></small></p>

<p><a href="/brunomiguel/tag:Neofetch" class="hashtag" rel="nofollow"><span>#</span><span class="p-category">Neofetch</span></a> <a href="/brunomiguel/tag:Fastfetch" class="hashtag" rel="nofollow"><span>#</span><span class="p-category">Fastfetch</span></a> <a href="/brunomiguel/tag:UnixPorn" class="hashtag" rel="nofollow"><span>#</span><span class="p-category">UnixPorn</span></a> <a href="/brunomiguel/tag:Linux" class="hashtag" rel="nofollow"><span>#</span><span class="p-category">Linux</span></a> <a href="/brunomiguel/tag:FOSS" class="hashtag" rel="nofollow"><span>#</span><span class="p-category">FOSS</span></a></p>
]]></content:encoded>
      <guid>https://infosec.press/brunomiguel/goodbye-neofetch-and-thanks-for-all-the-fish</guid>
      <pubDate>Wed, 01 May 2024 20:53:57 +0000</pubDate>
    </item>
  </channel>
</rss>