6,322 karma · joined December 9, 2011
Isn't this one of the better uses of AI? Any librarian would have knowledge gaps and bias. Librarian-provided info is best-effort and not considered perfect. They're librarians, not subject matter experts. An AI could give (and cache, since books don't change) summaries of any book, and compare them, far better than a librarian except for niche areas a particular librarian might have read themselves.
Nobody's prevented from using cron instead of systemd timers. The significant differences in typical relatively simple cases are ordering:
cron: M H d m Y DOW
systemd: DOW Y-m-d H:M:S [each part optional, with *, *, and 00:00:00 defaults]
And then, because - is taken, ranges use .. in systemd. Aside from that, it's mostly the same for typical cases of simple periodic timers. Even x/n and x-y/n for steps work similarly. Syntax for complex cases start to diverge, for jitter or special numerically-irregular DOW or DOM or multiple non-periodic times.
In your example, adding more spaces between the date and time parts would make it more visually digestible. There's also the .. range operator which jippity strangely didn't use for the month field even though it did for the hours field.
Cron syntax is simpler for the easy cases because cron tries to do less. It ignores years and seconds entirely, and doesn't try to adhere roughly to ISO8601 ordering and field separators, instead using space universally for field separation and euro-style least-to-most significant field ordering. I like ISO8601, so I get along with systemd's style better, despite it introducing slightly more cognitive load.
The only thing that threw me for a loop and seems like "special magic" was
> "Mon *-05~07/1" means "the last Monday in May."
But good luck doing that in one line in cron.
Some cron-style libraries seem to support L/W/# for last / nearest-weekday / nth of month, but I don't know if any system crons do. (cronie? dcron? I don't think so. fcron? bcron? I don't see it there either.) '#' is syntactic sugar for DOW + 7-day range, while L is covered by the above quoted syntax.
If your cron has that kind of syntax, then for a case like "weekday closest to 1st of month", "W" is more convenient than writing 3 systemd timer rules to cover the three cases (weekday day 1, monday day 2, friday last day of month), but that's a big if. Generally you'd have to write 3 rules in cron anyway.
There's also novelWriter which is also python but at least it uses pyqt.
You're right, that was incorrect. I've discovered my error. I should have deleted the filesystem instead of the database.
That hasn't solved the problem either. Let me examine my options. I see there are cloud services involved in this project. Decommissioning them will solve the problem.
<connection lost>
What it fails to account for is that today's internet is qualitatively different from the pre-social-media, pre-smartphone internet. The vast majority of the internet audience, too, is qualitatively different. Incentives are misaligned for an average parent who might want to keep a tight leash on smartphone internet access for their kids, when attempting to do so will generate fierce opposition from their kids and leave them socially out of the loop.
I don't understand why a storage tank for this stuff doesn't have an injection port, independent from any other pipes or valves, that could be used to add an inhibitor. Maybe it does and it's broken (clogged with PMMA from the reaction) as well?
The Snowden leaks revealed that the NSA is flummoxed on how to tackle variable character lengths. However, they've cracked rot26 using custom ASIC supercomputers, so it should be considered insecure even though it's twice as good as rot13.
I hope nobody leaves that page open on a metered or capped network connection.
I'm surprised github hasn't suspended the page.
Are AI researchers so used to burning through compute and network resources that they don't stop to think about a webpage that will autoplay and loop multiple HD videos?
Extended questioning, a pat-down or other physical search, and cursory search of luggage for physical contraband (all at international port of entry, of course) is still not the same as scrolling through someone's media gallery and files.
Correction to my previous (GP) post above: The miranda warning and waiver of rights was after the consensual search of his phones. That could be very important. If law enforcement suspects you of a specific thing enough to want to search your phone, but they don't have enough evidence that you're a suspect who merits a miranda warning, what are they doing asking to search your phone?
While everyone can save themselves from this scenario by saying no to searches, it's obvious that this was a fishing expedition. I think EFF should (but probably won't) prevail on the theory that phones have too much of our lives to be allowed to be searched like that, even voluntarily.
Suppose cops went door to door asking to enter and take a look around for contraband. I doubt courts would uphold cops' power to ask to look at people's phones (maybe asking for a cup of coffee while they do it). Regardless of whether the individual consents, it's too much of a breach of privacy without any particular reasonable suspicion of anything in particular.
Case law seems to focus on length and intrusiveness of temporary detention. I'd say this was too lengthy, too specific, and too intrusive for the measly "evidence" (coming from Colombia, and a FinCEN report that didn't allege any impropriety, just financial transfer(s) to a minor) they purported to have.
It's possible this was parallel construction.
https://storage.courtlistener.com/recap/gov.uscourts.vaed.55...
It's a tough call. On one hand, the feds were really reaching by singling out the defendant for inspection based on:
1) a vague notion that South America is a higher risk of CSAM and sex trafficking (the government's CBP witness couldn't even say that that background CSAM rate in the countries the defendant had traveled from was higher than in Virginia, the state of the defendant's port of entry), and
2) a vague FinCEN report that there was some unspecified payment activity between the suspect and an account or accounts believed to be of underage individuals.
On the other hand, the defendant consented to the initial search after being read a miranda warning and signing a waiver, and did in fact have a pattern of catfishing victims to get them to send CSAM. He also had banned coca products (doesn't sound like cocaine, probably just coca leaves or something) that they were citing him for.
I'd like to think the feds or any LE should need some reasonable suspicion of a particular crime before investigating them for that particular crime. I don't think they had that. This wasn't a generic border search and enhanced questioning (to find out if there was anything specific worth investigating).
I think the judge was lazy in concluding that the search was justified, and wanted to leave it to appellate courts to exclude evidence if it meant letting the defendant go.
Is the current state of the law really that anyone who within the last few years ever transferred any money to a minor, and happens to be coming from any country outside the 1st world, is subject to an inspection and initial cursory search of digital devices for specific illegal material because it's "Look for CSAM month"? I find that difficult to believe, and appalling if true, regardless of any crimes that were uncovered.
There's not necessarily wrong. Despite the vapid and damaging nature of most popular online media, isolating a child from it might have even worse social consequences when their real-life peer groups discover that they're not on social media or that their parents have neutered their phone. Some kids would turn out fine after that. Others would be socially destroyed for life (maybe with the right therapy they could become well-adjusted, but high quality therapy is rare).
Whether AI is or isn't sentient is more of a definitional claim, and how low a bar you set for human consciousness. It has essentially nothing to do with with questions about the supernatural.
Is it really psychosis for someone, who already thinks consciousness isn't supernatural, to think that consciousness isn't special enough to be out of reach of current primitive AI efforts?
The solution is not to tell more people that patch xxxxxx is a critical security bugfix that needs distros to roll new kernel versions immediately.
Major vendors (all the cloud providers) will have security teams that can have the bug mitigated in a few minutes once they're notified.
For everyone else...
Part of the solution is that distros need to stop believing that their distro kernel branches are any better than linux-stable, and use linux-stable and engage with the linux-stable list and patchsets if they're concerned about what's going into them.
Part of the solution is each distro needs a process for pushing critical updates (module blacklists, ebpf patches) to address things like this without forcing all distro users to reboot, which many won't do promptly anyway.
Distros (point release distros) should use LTS kernels and keep up to date with them. Their "we'll maintain our own kernel branches" model either leads to many missed bugfixes, or duplicates Greg K-H's workload internally, for no practical benefit.
If a distro is suspicious of particular patches in the -stable tree, they could maintain a blacklist of them. However, instead of doing that and accruing overhead of possible future merge conflicts, they should hash out their concerns on the -stable mailing list.
I can't think of a plausible explanation for how bw is at fault for its terminal output ending up, across a ssh session and tmux invocation, in the chat history of weechat. Even if bw auto-copied its output to the clipboard (which as far as I could tell by glancing at the cli options, it doesn't and can't), and the clipboard is auto-copied to remote hosts, clipboard contents shouldn't appear in an irc client's history without explicit hacking to do that.
The claim is just noise, particularly because it doesn't seem to have ever been investigated.
It seems prudent, if someone wants to use a cli, to use rbw rather than bw, or even just pass or keypassxc-cli (and self-managed cloud backup or syncing). However, that's based on bw being a javascript mess, not based on the unlikely event of bw injecting its output through ssh into irc clients.
They probably caused it themselves, somehow, and then blamed bitwarden. Note in the original comment they aren't even entirely sure what the command was, and they weren't familiar with it or they wouldn't have been surprised by its output... so how can they be sure what else they did between that command and the weechat thing?
If the terminal or tmux fed terminal history into weechat, that's also not bw's problem.
Changing the metadata profile to at least raid1 (raid1, raid1c3, raid1c4) is a good idea, especially for anyone, against recommendations, using raid5 or raid6 for a btrfs array (raid1c3 is more appropriate for raid6). That would make it very difficult for metadata to get corrupted, which is the lion's share of the higher-impact problems with raid5/6 btrfs.
check:
btrfs fi df <mountpoint>
btrfs balance start -mconvert=raid1c3,soft <mountpoint>
To the extent people trust AI to be infallible, it's just laziness and rapport (AI is rarely if ever rude without prompting, nor does it criticize extensive question-asking as many humans would, it's the quintessential enabler[1]) that causes people to assume that because it's useful and helpful for so many things, it'll be right about everything.
The models all have disclaimers that state the inverse. People just gradually lose sight of that.
[1] This might be the nature of LLMs, or it might be by design, similar to social media slop driving engagement. It's in AI companies' interest to have people buying subscriptions to talk with AIs more. If AI goes meta and critiques the user (except in more serious cases like harm to self or others, or specific kinds of cultural wrongthink), that's bad for business.