> Amid a push to perfect 'casual viewing,' creatives say streaming execs are requiring them to remove nuance and visual cues, and do things like announce when characters enter a room.
Nice... I made "Bulk Git Ops" Bash functions to source into shell and tab-complete to invoke. (nb. I organise my sources like this: ~/src/{github,gitlab,bitbucket}/{usernames..}/{reponames..}).
Examples assume that repos you contribute to are spread across
remote hosts, and (hopefully) namespaced sanely. I organise my
sources as follows.
~/src/{github,gitlab,bitbucket}/{usernames..}/{reponames..}
QUERY: Count repos that are stale:
ls_git_projects ~/src/ | take_stale | count_repos_by_remote
QUERY: Count repos that are active (within 12 hours by default):
ls_git_projects ~/src/ | take_active | count_repos_by_remote
EXECUTE! Use 'xgit' to apply simple git commands to the given repos, with logs to STDERR/stty
ls_git_projects ~/src/bitbucket | xgit fetch # bitbucket-hosted repos
EXECUTE! Use 'proc_repos' to apply custom functions to, with logs to STDERR/stty
ls_git_projects ~/src/bitbucket | proc_repos git_fetch # all repos
ls_git_projects ~/src/bitbucket | take_stale | proc_repos git_fetch # only stale repos
ls_git_projects ~/src/bitbucket | take_active | proc_repos git_fetch # only active repos
EXECUTE! What's the current branch? Logs to STDERR/stty
ls_git_projects ~/src/bitbucket | proc_repos git_branch_current # all repos
EXECUTE! With logs redirected to hidden dir for logging (you must create it by hand first)
mkdir -p "${logdir}"
ls_git_projects ~/src/bitbucket | proc_repos git_branch_current 2>> "${logdir}/bulkops.log"
tail "${logdir}/bulkops.log"
If TikTok turned out to be State sponsored spyware, would you reconsider?
I support your slippery slope argument. I wonder where your red line is relative to "state sponsored spyware" and "typical advertising ID tracking" or "cool new app from company influenced by an adversarial super power".
All spyware should be illegal. A law to reign in the ubiquitous data collection on everyone's computing devices would be great. Maybe start by requiring all data collection to be opt-in and for a specific purpose. Make it illegal to deny functionality that doesn't strictly require the requested data. "Paying with your privacy" shouldn't be a thing. Crush every data broker.
This law is different to that, it's all about specific actors, not about behavior and actions. A "people we don't like" list. CNN could be on a similar list soon. All constitutional of course - the law will specifically mention how this is all for national security. And no one's speech is being suppressed, the journalists can always write for a different news channel.
I use and highly recommend this framework as the starting point for any technical documentation. It helped me learn how to keep the detailed technical explanations out of the how-to documents. Before I learned of Diataxis, my how-to docs were much longer and hard to follow when things go right (because I had lots of, "if this doesn't work, investigate A, B, C...").
It looks like the letter carrier has to reach down to get to that mailbox. Yes, they can reach it, but I wonder about ergonomics. Not all mailboxes are the same height, so you probably have to reach down for some, but if this is a representative mailbox, I worry.
[1]: https://doi.org/10.1017/S0007114512000797
[2]: https://doi.org/10.3390/nu14194079