<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0"
    xmlns:content="http://purl.org/rss/1.0/modules/content/"
    xmlns:dc="http://purl.org/dc/elements/1.1/"
    xmlns:atom="http://www.w3.org/2005/Atom">
    <channel>
        <title>backblaze — LowEndSpirit DEV</title>
        <link>https://dev.lowendspirit.com/index.php?p=/</link>
        <pubDate>Thu, 09 Apr 2026 05:42:39 +0000</pubDate>
        <language>en</language>
            <description>backblaze — LowEndSpirit DEV</description>
    <atom:link href="https://dev.lowendspirit.com/index.php?p=/discussions/tagged/backblaze/feed.rss" rel="self" type="application/rss+xml"/>
    <item>
        <title>Pagely acquired by GoDaddy, Backblaze a public company</title>
        <link>https://dev.lowendspirit.com/index.php?p=/discussion/3519/pagely-acquired-by-godaddy-backblaze-a-public-company</link>
        <pubDate>Sat, 13 Nov 2021 01:39:54 +0000</pubDate>
        <category>Industry News</category>
        <dc:creator>vyas</dc:creator>
        <guid isPermaLink="false">3519@/index.php?p=/discussions</guid>
        <description><![CDATA[<p>"Entreprise" level WordPress hosting... brought to you by GoDaddy</p>

<p><a href="https://pagely.com/blog/we-did-it/" rel="nofollow">https://pagely.com/blog/we-did-it/</a></p>

<p>Meanwhile...</p>

<p>Backblaze went public</p>

<p><a href="https://www.cnbc.com/2021/11/12/backblaze-ipo-takes-opposite-approach-to-rivian-going-public-small.html" rel="nofollow">https://www.cnbc.com/2021/11/12/backblaze-ipo-takes-opposite-approach-to-rivian-going-public-small.html</a></p>
]]>
        </description>
    </item>
    <item>
        <title>Is anyone using the Backblaze B2 + Cloudflare combo?</title>
        <link>https://dev.lowendspirit.com/index.php?p=/discussion/3412/is-anyone-using-the-backblaze-b2-cloudflare-combo</link>
        <pubDate>Tue, 05 Oct 2021 16:37:01 +0000</pubDate>
        <category>General</category>
        <dc:creator>Sova</dc:creator>
        <guid isPermaLink="false">3412@/index.php?p=/discussions</guid>
        <description><![CDATA[<p>As the title says. Looking to see if anyone is using the above combo successfully with different files.<br />
I'm torn between using the above if it works as expected (no transfer/download fees for files) or going for a storage VPS. <br />
Files are a mish-mash of different media, archives, roms etc.</p>
]]>
        </description>
    </item>
    <item>
        <title>Backblaze and Facebook Pixel Tracking</title>
        <link>https://dev.lowendspirit.com/index.php?p=/discussion/2919/backblaze-and-facebook-pixel-tracking</link>
        <pubDate>Fri, 14 May 2021 04:02:13 +0000</pubDate>
        <category>Industry News</category>
        <dc:creator>vyas</dc:creator>
        <guid isPermaLink="false">2919@/index.php?p=/discussions</guid>
        <description><![CDATA[<p>Received this message from Backblaze.</p>

<p>Apologising for incorrectly sending tracking ads in my Facebook feed. I do not recall signing in (i use 2fa and the log did not show me using backblaze in March) but..</p>

<p>Moral of the story: if you see “fbclkid” or similar in the url, delete the tracking link,or do not sign in.</p>

<blockquote><div>
  <p>We are writing to inform you of a recent event that may have involved your account. On March 8, 2021, a new Backblaze marketing campaign was incorrectly configured to potentially trigger an advertising pixel on a signed-in page “b2_browse_files2.htm.” The issue was discovered on March 21, 2021 and promptly fixed the same day.</p>
  
  <p>You are receiving this correspondence because, based on our investigation, we believe that you may have accessed that page during this time frame. If you accessed that page and you took the additional steps of browsing your files AND clicking on a file to preview file information, certain metadata consisting of the file name, file size, and upload timestamp may have been shared with Facebook. No customer files, nor the content of any customer files, were shared. Facebook is obligated to only process information based on our instructions and we have instructed them to not further process this data and to delete it. We therefore have no reason to believe this event had any impact on your account, but we nevertheless wanted to provide you with this update and apologize for this mistake.</p>
  
  <p>If you would like more information, please see the following link:  Privacy Update: Third-party Tracking (backblaze.com).</p>
</div></blockquote>
]]>
        </description>
    </item>
   </channel>
</rss>
