As a Chrome apologist really this pisses me off but I've been waiting for this forever and applaud the team (especially if they beat Chrome to landing this in a stable release)
It's not a bug to disallow "distribution of hacked material" in your Terms of Service.
If you think it was political, you should certainly inform the FEC! They found that Twitter had acted "for commercial reasons and not for the purpose of influencing an election" so they'd appreciate the heads up.
Which would've been more believable, if they literally did nothing about the thousands of tweets sharing the hacked Trucker rally database. And it wasn't just random accounts, a lot of major north American/Canadian newspapers shared articles that not only mentionned the hacks and hinted at where to find them, but also explicitly detailed the contents of the database.
Yes that's the go-to copypasta reply. ("Literally" here meaning "not literally.")
Twitter changed their policy in response to criticism of the Biden tweets to "no longer remove hacked material unless it’s directly shared by hackers or those working with them" including the rally database, and they restored previously removed tweets about Biden.
That's very convenient! The problem is that they didn't enforce that policy before the laptop leaks either. Not in any significant way and no media outlet ever got their account banned for reporting on a hack before (or after).
The ~7000 QAnon accounts they banned don't fit your narrative I'm afraid.
There are now several intermediate steps they've added since then, like clear warnings [1]. This allows the account to stay active and still report on stolen data. Much better IMO, banning accounts is common practice, but too heavy-handed as to be the only tool Twitter has.
ah yes, because when a federal agency doesn't punish a multi billion dollar corporation, we all know it's because they definitely didn't do anything wrong. They're so trustworthy!
Please refrain from replies without content. Why did the FEC fine the DNC and Clinton for violating rules related to the Steele dossier? My understanding is that the DNC also has a few dollars. Did they forget their bias?
My point isn't about the FEC being biased, I just reject appeals to the authority of US federal agencies, because they aren't trustworthy. They don't (meaningfully) punish rich people, and they are usually staffed by various former/future C-level people from the organizations they're supposed to be regulating.
For sake of discussion: aren't there uses of this that aren't nefarious?
Their claim that employees intending to leave "may put the organization at risk of malicious or inadvertent data exfiltration upon departure" is, cynically, corporate bs; but data theft or vandalism isn't entirely unheard of by departing employees.
Ever moved your source code to a thumb driver before you left your job, even though your contract technically forbids it, you've signed away the IP rights, etc?
It's weird to assume that noone would copy the data before resigning instead of after resigning though. Especially if your company might immediately garden leave you.
Studies I've read in the past have claimed the same thing, yet still excluded people that would skew their results without reporting it.
I have a friend who does statistical analysis for a living, and we have a game where he points out the flaws that are only obvious to those that know statistics and research well, and us laymen are oblivious.
A medical doctor once told me "coffee must be good for you because I drink it!". It seems common that people just want science to agree with them, and they don't care how or why.
I can't prove my point on this article (not enough time/energy/will) but I have watched health articles for years and you can go back to news sites and find this same exact study done over and over, reported in news organizations as if it's new every time.
One stupid example, articles from just CNN going back to 2010 just on one page of search results:
> there may be other lifestyle factors contributing to that lower mortality risk among people who drink coffee, like a healthy diet or a consistent exercise routine
> the data cannot conclusively prove that coffee itself lowers the risk of dying; there may be other lifestyle factors contributing to that lower mortality risk among people who drink coffee, like a healthy diet or a consistent exercise routine
...and controlled for in the study
> lifestyle, sociodemographic, and clinical factors
I would just caution people to understand that saying that something is "controlled for" in an observational study (which is something I do all the time, I'm not saying it's bad) is not the same as saying that we've eliminated confounders, leaving a causal effect.
I've had people try to guess my login with Company ABC once they learned of my CompanyXYZ@mydomain.com address. Avoiding the reuse of email addresses helps here, the same way avoiding the reuse of passwords does.
For blackhats, with catchalls you can create multiple accounts on sites that try to prevent it by assuming everyone only has 1 email address.
For me the biggest drawback is migrating ALL those emails if your provider decides to end support for catchalls (like Dreamhost).
> For me the biggest drawback is migrating ALL those emails if your provider decides to end support for catchalls (like Dreamhost).
With Gmail for Business / GSuite / Workspace, I had gone through the trouble of adding aliases through the Gmail.com UI when I wanted a from address. And I had created a bunch of dead accounts with aliases to reduce spam.
But when I switched away from Workspace to NameCheap, I just set up my one account as a catch-all, and in Thunderbird, when I want to send from one of those aliases, I just type it in, and it works fine. (Gmail had a setting that if you got it wrong, it sent it as an alias, but also used your mail address as the actual from/reply-to, which I found annoying!)
I also stopped bothering setting up those "honeypot" accounts. I get more spam, but... it's almost all detected as spam and put in the spam folder, so I don't worry too much. A few weeks ago, I had a day where a couple dozen gibberish addresses came in, like 8aeef09lk@domain.com, but then it stopped again.
Of course, all that is to say, if my current host does end support, it would be a pain!
Calendar apps are so complicated and tightly integrated with other productivity apps now I'm not sure the benefit of simplicity here outweighs the cost of losing that.
My Google cal emails me notifications, works with desktop calendar apps, integrates with Maps, etc. It autofills addresses, adjusts for time zones, syncs across my 4000 devices, allows me to edits dates via text input or GUI/drag 'n drop, etc. (Not shilling, Apple cal is probably similar.)
Even my todo list went from org mode to Google Tasks because of the integrations with Android, Google Calendar, etc.
I think you have it slightly backwards (or should).
There's an open standard, icalendar (https://icalendar.org/) which represents calendar entries. Invitations you get in the mail come this format too. The easiest way for your map, address book, reminders etc to integrate is just to talk to your calendar server. The apps need not know about each other at all.
Google and microsoft of course may do some non-standard futzing around within their proprietary stacks: you can often see these problems when you try to connect to something outside their silos, though in my experience the standards integration in google calendaring is pretty good (especially when compared to their mail system). It's been a few years since I had to interface with Exchange calendaring but back then it...wasn't good.
So in any case there's no reason you couldn't write a small service that spoke ical over the network and this plain text calendar's format locally. Then it would appear normally in your partner's iphone, handle your kids' schools' calendars etc.
Whether it would be worth doing that is literally an exercise for the reader...but you'd get the same level of integration as you would with, say, Apple's icloud calendar services.
That's fine in theory but honestly I have bigger fish to fry than rolling my own networked calendar. Much as I'm a big advocate for open source and open specs (even being an author and contributor to a few open source projects too), I have to use these proprietory systems for authentication and email at work anyway. So the convenience of using them for my calendar too far outweighs the cost of rolling my own solution.
This is one of those situations were worse is better.
> There's an open standard, icalendar (https://icalendar.org/) which represents calendar entries. Invitations you get in the mail come this format too. The easiest way for your map, address book, reminders etc to integrate is just to talk to your calendar server. The apps need not know about each other at all.
> Google and microsoft of course may do some non-standard futzing around within their proprietary stacks: you can often see these problems when you try to connect to something outside their silos, though in my experience the standards integration in google calendaring is pretty good (especially when compared to their mail system).
Yes, crossing the two is often still a hot mess.
The first paragraph sounds great in theory. The second paragraph sounds more like what happens in practice...
> Calendar apps are so complicated and tightly integrated with other productivity apps now I'm not sure the benefit of simplicity here outweighs the cost of losing that.
I've been looking for something like this that will let me edit in plaintext but also sync both ways with gCal for the benefits of plaintext but also the caveats that you mentioned.
I actually built something exactly like this, using the google calendar API and FUSE. It wasn't very difficult at all, I think it took half a day. I'll try to find the code, it's been about a year since I used it since it was just a toy and I didn't want to maintain it.
If you work alone, your calendar and todo lists are what you put there with you as the only editor. So whether, you use pen & paper, a spreadsheet, a text file in Google Drive, or whatever, does not matter to anyone except you. So, whatever works for you. I'm a pen & paper guy. But as soon as you are not working alone, you need different tools. Mostly, my pen & paper work eventually ends up in a proper tool.
Any time slot that matters to me goes into a proper calendar so my time is marked as blocked and people know that I'm busy and don't dump meetings in it. I literally block time to code. Likewise, a lot of my work is coordinating work with others and we use Asana and Github issues for that sort of thing. Other tools are available. But the key feature usually is that you can use them with a team and assign stuff to each other, edit them concurrently, and have some non technical team members doing so as well.
Doing csv exports and imports is feasible for calendars and issue trackers but it doesn't solve a problem I have (except when migrating to different tools). As data input tool that seems not really great. It's actually why I like Asana; I can just type an issue, hit enter, type another one, etc. It feels like a spread sheet tool.
The problem is that Google Calendar (and most other widely used calendars) has poor portability. I too use it, because my work uses it, so I have no choice, if I don't want to end up with multiple calendar apps. I hate it for this reason.
