Brave is built on Chromium. So, by default, no they are not safe from this. Without extra effort, Brave will have this feature. I don’t know if its feasible but there’s a chance the Brave devs can remove the code from their distribution, but that’s the best case scenario and just puts them in the same position as Firefox: they get locked out because they refuse to implement the spec.
Colloquial use of that word is not related to its technical use to describe a female dog in dog breeding. Colloquial use of the word is precisely driven by misogyny. Don’t try to play that game, it’s dishonest. Do you think the homophobic f-slur is acceptable because, after all, it is a technical term relating to bound wood fuel? If not, why is that not acceptable, but the one you’re using is? Historical linguistic justification for a word whose colloquial use has not been related to its historical meaning for a very long time is dishonest.
By “otherwise discriminatory” I meant discriminatory in ways other than the two (sexism, ableism) that I explicitly mentioned; can you not think of other ways to discriminate? “Otherwise discriminatory” can include words that are specificaly xenophobic or racist, or homophobic. I didn’t bother doing a full inventory when I was illustrating a point.
I find casual use of opaque blocklists without any second thought to their impact disturbing.
It’s not opaque. The entire block list regex is publicly visible for every single instance. In fact, it’s in the page source of every single page you load. You’re simply uninformed. Moreover, if you think there was no second thought to it’s impact, you’re yet again uninformed. There was (and has been) discussion about it amongst developers and (early) users, and discussion continues; in fact, there was a post about it with large engagement maybe three days ago.
I am not sure how I feel about enforcing a block list (and I said that in my previous comment), but one thing it does do, repeatedly, is illuminate how little people think about offensive things they say. Interestingly, more often than not, people would rather defend their use of misogynist language than consider using literally any other word in English or another language.
It’s in the blocked word list because it’s misogynist. The fact that it’s used so commonly with no second thought is disturbing.
I don’t know if I agree with the blocked word list being enforced, but I definitely have a problem with rampant misogynist, ableist, and otherwise discriminatory language used with no thought.
Ah I see you mentioned the cuts are only a few seconds long. This wouldn’t catch that very well.
If you have a server outside of your network you could simply hold open a TCP connection and report when it breaks, but I’ll admit at that point it’s outside of what I’ve had to deal with.
Depends on how much you want to set up. For my purposes, I just check for connectivity every minute, and record true or false as a new row in a sqlite database if there is connectivity.
This is what I use on my raspberry pi,
#!/usr/bin/env python3
from datetime import datetime
import sqlite3
import socket
from pathlib import Path
try:
host = socket.gethostbyname("one.one.one.one")
s = socket.create_connection((host, 80), 2)
s.close()
connected = True
except:
connected = False
timestamp = datetime.now().isoformat()
db_file = Path(__file__).resolve().parent / 'Database.sqlite3'
conn = sqlite3.connect(db_file)
curs = conn.cursor()
curs.execute('''CREATE TABLE IF NOT EXISTS checks (id INTEGER PRIMARY KEY AUTOINCREMENT, timestamp TEXT, connected INTEGER)>
curs.execute('''INSERT INTO checks (timestamp, connected) VALUES (?, ?);''', (timestamp, 1 if connected else 0))
conn.commit()
conn.close()
and I just have a crontab entry * * * * * ~/connectivity_check/check.py >/dev/null 2>&1 to run it every minute.
Then I just check for recent disconnects via:
$ sqlite3 ./connectivity_check/Database.sqlite3 'select count(*) from checks where connected = 0 order by timestamp desc;'
Obviously, it’s not as full-featured as something with configurable options or a web UI etc, but for my purposes, it does exactly what I need with absolutely zero overhead.
What a weird take. You’re allowed to pay for whatever you’d like. Personally, I can’t afford to pay for any JetBrains product, even if I wanted to.
Not only are there alternatives which may be better overall or better suited to someone’s needs, that wasn’t even my point. My point was more that it is only temporarily free, and so the parent commenter’s comment of “it’s free” should be taken with a grain of salt if you’re considering the product.
Moreover, we’re in the Open Source community: Fleet is neither free nor open source, and pointing that out here is relevant.
Quoting JetBrains,
Fleet is free to use during the public preview
(emphasis mine)
So it is only temporarily free. Once it’s polished it will no longer be free. Better to not get tied in to something that will be taken away from you before long.
It’s not just Java. It supports a few other languages as well. I am pretty sure it supports Rust, HTML, JavaScript and maybe a couple others. It doesn’t support Python, Go, PHP, C/C++, or Ruby (as they have separate products for those).
Correct.
Pi hole does not work for YouTube (or Twitch or many others). It doesn’t work for services who distribute ads from their own servers.
If you had Android instead of iOS you may have been able to use an ad-free youtube client and cast to TV, but if you’re streaming on the TV, or from iOS, I don’t know how you’d go about blocking ads.
Me too. The exact same app. I rarely open the play store with other app stores existing but good lord this is bad.
The plural of Linux is Linus.
Have you been keeping up with the story? Few people are saying there is absolutely zero value in telemetry as a concept. Most people have an issue with it being on by default. For a FOSS community, especially one who tries to act as if privacy matters, the very nature of the concept “telemetry that’s on by default” is the problem. I wouldn’t personally use the phrase corporate shilling because I think it’s not the most precise descriptor of the situation, but it’s not entirely innacurate either. I think all of their talk about “it’s anonymized” or “it’s not excessive” or what have you is just distraction: the real issue is that it’s on by default.
Not surprising unfortunately. There’s no accountability or transparency; they can deny any application they want for any reason, and don’t have to tell you why. As long as they don’t come out and say it’s due to being a member of a protected class (which they can act on indirectly, just can’t say it out loud), they can get away with any reasoning.
Oh it’s vile.
Lots of people list a property, take loads of applications, each with a nonrefundable application fee (often $100+), then close the listing and pretend it was leased out. They wait a bit and repeat the play. They can rake in thousands of dollars for literally making a posting on a website, and repeat this often. And it’s often desperate people victimized too: not only are these people renting so they’re already in a vulnerable situation, the people willing to pay high application fees typically are desperate to get a lease.
I’ve also seen places that make you pay an application fee, and as part of the screening process they run a credit check; if they aren’t satisfied with your credit score, they’ll deny you and of course keep the application fee. What’s more nefarious about this though is that they don’t give you a score cutoff; you don’t know if your score meets their criteria until after you’ve paid a nonrefundable fee.
I consider their past behavior to be counter to their stated goal of privacy, and counter to the notion that they deserve to be trusted.
They have sent out direct mailers that basically equated to a customer list leak; also I’d take a peek at the wikipedia entry about their business model, which mentions some stuff that isn’t the most savory:
… Brave earns revenue from ads by taking a 15% cut of publisher ads and a 30% cut of user ads. User ads are notification-style pop-ups, while publisher ads are viewed on or in association with publisher content.
On 6 June 2020, a Twitter user pointed out that Brave inserts affiliate referral codes when users navigate to Binance
In regards to the mailers, they messed up and passed blame,
In this process, our EDDM vendor made a significant mistake by not excluding names, but instead including names before addresses, resulting in the distribution of personalized mailers.
With regards to the CEO, he made a donation to an anti-LGBT cause when he was CEO of Mozilla in 2008. He lost his job at Mozilla due to his anti-LGBT stance. He also spreads COVID misinformation.
As others have pointed out, it’s also Chromium based, and so it is just helping Google destroy the web more than they already have.
Ah I see they did say seal. I still read it as one of these stickers, but reading it as gasket seems sensible too.
Someone correct me if I’m wrong but my first guess is: you pronounce is like the moderately common name Simone.
I don’t think they’re referring to something like a “rubber seal”, I think they mean these things:
It may be dead to its users anyway depending on how forceful Google is with this. If Brave doesn’t work on 98.8% of all websites with advertising or indeed on 49.5% of all websites (approximately Google’s ad network’s reach), it becomes as niche as lynx.