Bold Browser

Privacy-respecting browser without a token or adware. Work in progress!
Discord:

[Bold Browser @BoldBrowser]

@LGWillmore @RandomFFUser @BraveSampson @techloreistaken @ky1ejj @brave You mean like the Chromie extension for Chrome OS? :) https://t.co/iARQ1dwCf5

Or Chromerly?
https://t.co/7lv83DhYWq

Aside from that, we didn't have a product. It was just a dev community thinking on a prototype who already said they'd rename almost immediately.

[Bold Browser @BoldBrowser]

Due to legal threats sent to one of our community members by a certain party, specifically looking to harm them financially because of what this browser is forked from, we are immediately changing the name and removing all association to "the browser that shall not be named".

[Bold Browser @BoldBrowser]

@shitcoinprotips @decryptmedia @Cointelegraph The Github issue that you mentioned actually was closed by the issue's creator because they realized development is happening in a private repo ;)

[Bold Browser @BoldBrowser]

@shitcoinprotips @decryptmedia @Cointelegraph We had 2 active branches under development but had to take them down due to legal threats from you-know-who. So now we're starting over and working in private branches! :) But you already knew all of this.

Thank you for the update though! You truly are our most loyal follower.

[Bold Browser @BoldBrowser]

@Foss_Hub @TheVarniitNigam Thank you! We'd love to follow up once we have our first build out 👍

[Bold Browser @BoldBrowser]

Why we removed our existing Github repos:

The contents of the forks were being cherry-picked for references to the original browser.

Those were then used in legal threats against one of our community devs to claim they're "purposefully causing financial damage to the creator"

[Bold Browser @BoldBrowser]

@LGWillmore @BraveSampson @techloreistaken @ky1ejj @brave @BraverBrowser We were being misrepresented in a reply to your tweet, so we replied to correct it.

[Bold Browser @BoldBrowser]

@LGWillmore @BraveSampson @techloreistaken @ky1ejj @brave @BraverBrowser You missed the point, but I'm not interested in explaining further.

[Bold Browser @BoldBrowser]

@LGWillmore @BraveSampson @techloreistaken @ky1ejj @brave @BraverBrowser That's a bold assumption.

It wasn't a cookie cutter letter.

There were specific references to the forked repository, where keywords/links to their product (that are obviously in a new fork) were presented as as "exhibits" to claim that contributor was sabotaging their product.

[Bold Browser @BoldBrowser]

@BraveSampson @techloreistaken @ky1ejj @brave Anyone willing to cherry-pick references in a fresh fork to claim trademark infringement and corporate sabotage by a single individual, is obviously not pro-FOSS.

[Bold Browser @BoldBrowser]

@BraveSampson @techloreistaken @ky1ejj @brave FYI: the legal threat contained references to the forked code where it still linked to your browser (URLs, keywords) to claim that a developer was intentionally/repeatedly trying to sabotage your product/brand.

Every fork will have references, especially when it's new.

[Bold Browser @BoldBrowser]

@BraveSampson @techloreistaken @ky1ejj @brave Previously when we made a point to you, you cut off the conversation and said you only wanted to talk code as a developer. Yet now you're on other tweets making new claims against us and our community. Perhaps just stop?

[Bold Browser @BoldBrowser]

@BraveSampson @techloreistaken @ky1ejj @brave And, again, why would that justify holding a single open-source contributor liable? They barely spoke about anything other than code.

[Bold Browser @BoldBrowser]

@LGWillmore @BraveSampson @techloreistaken @ky1ejj @brave @BraverBrowser Someone tasks the lawyer to write that letter. If they already permitted team members to partake in the conversation on Discord, why would they spend time, money, and resources to hold one single open-source contributor legally liable for everything people do on the project?

[Bold Browser @BoldBrowser]

@LGWillmore @BraveSampson @techloreistaken @ky1ejj @brave @BraverBrowser Especially when their company's developers are in our Discord having semi-daily conversations with us. That doesn't really make anyone feel like a potential lawsuit was creeping or that they'd think we're looking to cause financial damages to them.

[Bold Browser @BoldBrowser]

@LGWillmore @BraveSampson @techloreistaken @ky1ejj @brave @BraverBrowser Ask if they're able to contact the project or that one particular developer and see if they can come to an understanding, as threatening to sue one contributor and presenting them as a "blackhat operator specifically & repeatedly looking to harm to their company" might fire back.

[Bold Browser @BoldBrowser]

@LGWillmore @BraveSampson @techloreistaken @ky1ejj @brave @BraverBrowser I disagree there was any hostility. We made the fork for a reason, but our tweets never "hated on" their browser. Otherwise we wouldn't be pointing ppl to it.

Regardless, the tweets on this account don't represent that one particular person who recieved all the legal threats.

[Bold Browser @BoldBrowser]

@LGWillmore @BraveSampson @techloreistaken @ky1ejj @brave @BraverBrowser For context, the replies above were due to us being presented as bad guys being openly antagonistic and accusing them of intentional wrongdoing, which is objectively false.

[Bold Browser @BoldBrowser]

@LGWillmore @BraveSampson @techloreistaken @ky1ejj @brave @BraverBrowser We stopped tweeting about it after the initial day.

We're only replying with context when someone shows up and seeks to harm our reputation by spreading misinformation about the context of the legal threats.

[Bold Browser @BoldBrowser]

@LGWillmore @BraveSampson @techloreistaken @ky1ejj @brave @BraverBrowser If they did, we definitely would have. Considering many were friendly with their team and sincerely looking to contribute to their codebase.

They had the opportunity to ask. Yet their board didn't and flexed with some lawyers to the one person whose name they could find online.

[Bold Browser @BoldBrowser]

@LGWillmore @BraveSampson @techloreistaken @ky1ejj @brave @BraverBrowser We also told them the name was temporary and that we'd change it. They didn't respond. In fact, they had team members in our Discord channel talking with our contributors about improving their codebase. Noone mentioned the name should be changed faster.