lobsters-ansible

yea this is bad, i had kinda forgotten about this https://github.com/lobsters/lobsters-ansible/issues/45#issue... i dont know, firefox is very buggy and unstable, crashes or just log me out of everything every few weeks, we dont really have great choices, wishful thinking, but i hope brave straightened up

I care a good deal that I trust the people who developed my browser. It's about the most critical piece of software in my life. From banking to professionally to personal life. The people who developed brave used brave to impersonate people and defraud their users out of money by asking for donations using other peoples names [1]. I don't trust them at all. Thus I don't use their browser. And, unsurprisingly, this is part of a pattern of bad behavior, not a one off criminal act by otherwise trustworthy people, for some examples [2]. [1] https://web.archive.org/web/20181221180137/https://twitter.c... / https://news.ycombinator.com/item?id=18734999 [2] https://github.com/lobsters/lobsters-ansible/issues/45#issue... and https://lobste.rs/s/iopw1d/what_s_up_with_lobste_rs_blocking...

Where did they make a big deal of blocking Brave on "ethical" grounds? https://github.com/lobsters/lobsters-ansible/issues/45 They outline a very specific behaviour that Brave engaged in but Chrome, Edge, and Safari do not. Brave was engaging in fraudulent behaviour, wherein it posed a fake donations scheme to users of the browser under the guise of supporting website owners with their implicit but nonexistent consent, and in actuality took the money for itself. Brave then also specifically and publicly singled out Lobsters in an issue. Lobsters devs do not want to spend dev time engaging with scammers operating in bad faith. Seems fair to me. See also an HN thread about the fraud scheme: https://news.ycombinator.com/item?id=18734999

This is why Brave was blocked [1.]. I'd have felt the same way, and people are entitled to their grudges. I think the grudge is reasonable. [1.] https://github.com/lobsters/lobsters-ansible/issues/45#issue...

For context: https://github.com/lobsters/lobsters-ansible/issues/45 It's pretty disgusting behaviour by Brave.

Why Brave is blocked: https://github.com/lobsters/lobsters-ansible/issues/45

The actual text that all Brave users are seeing when they visit Lobste.rs is: Blocking a cryptocurrency scam where the Brave browser pretended to be fundraising on behalf of a site without that site's knowledge or consent, then lied about funds being held in escrow and kept them for itself. For details: https://lobste.rs/c/bwbssx https://github.com/lobsters/lobsters-ansible/issues/45 and https://github.com/lobsters/lobsters/issues/761 Edit: repeated below comment. As I understand it, Brave added a "donate to lobste.rs" link when viewed in their browser, and then kept all the money. If you are using Brave, confirm any donation (and maybe anything else involving money) in another browser.

No. When I ban sockpuppets I excerpt and save relevant logs from their abuse. Older material is discarded by logrotate: https://github.com/lobsters/lobsters-ansible/blob/a9beccc573... I save these logs because people who sockpuppet and get banned often try to sneak back on under other names. Some odd quirk of the psychology. I realize saving all logs indefinitely might help in spotting them, but the marginal improvement in accuracy isn’t worth the significantly increased potential for loss in a data breach.

Did we read the same comment? Could you please follow this link and try to explain this behavior? https://github.com/lobsters/lobsters-ansible/issues/45 > They added UI to the browser to claim users could pay individual site creators who'd signed up, but had scraped the names and photos of site creators who'd never heard of them. Brave planned to take the payments after they were unclaimed for 90 days. When caught, they claimed the funds were held "in escrow" but later admitted there were holding the funds themselves.

https://github.com/lobsters/lobsters-ansible/issues/45 > They added UI to the browser to claim users could pay individual site creators who'd signed up, but had scraped the names and photos of site creators who'd never heard of them. Brave planned to take the payments after they were unclaimed for 90 days. When caught, they claimed the funds were held "in escrow" but later admitted there were holding the funds themselves. Story broke here: https://news.ycombinator.com/item?id=18734999

Here's a discussion about why lobste.rs blocks (or blocked?) the Brave user agent: https://github.com/lobsters/lobsters-ansible/issues/45 Here's a hacker news discussion about same issue but affecting Tom Scott rather than the lobste.rs people: https://news.ycombinator.com/item?id=18734999 (archive of the linked tweet: https://web.archive.org/web/20190203094117/https://twitter.c...) EDIT: Oh, and we can't forget the time when they silently changed links to contain their own referral codes: https://www.theblock.co/linked/67594/braves-browser-has-been... (HN discussion: https://news.ycombinator.com/item?id=23441605)

The slate article is better than the BBC one. https://slate.com/technology/2014/04/brendan-eich-why-mozill... Brave had technical scams too: https://github.com/lobsters/lobsters/issues/761 https://github.com/lobsters/lobsters-ansible/issues/45 https://web.archive.org/web/20181221180137if_/https://twitte... https://web.archive.org/web/20181221231556if_/https://twitte... https://news.ycombinator.com/item?id=18734999

Some links supporting this view: [1] https://github.com/lobsters/lobsters/issues/761 [2] https://github.com/lobsters/lobsters-ansible/issues/45 [3] https://news.ycombinator.com/item?id=18734999 [4] https://web.archive.org/web/20181221180137if_/https://twitte... [5] https://web.archive.org/web/20181221231556if_/https://twitte... [6] https://news.ycombinator.com/item?id=27549604 [7] https://slate.com/technology/2014/04/brendan-eich-why-mozill...

I think there's more, but here are some: [1] https://github.com/lobsters/lobsters/issues/761 [2] https://github.com/lobsters/lobsters-ansible/issues/45 [3] https://news.ycombinator.com/item?id=18734999 [4] https://web.archive.org/web/20181221180137if_/https://twitte... [5] https://web.archive.org/web/20181221231556if_/https://twitte...