MAKE GENTRIFY TOTAL DESTROY.
conferencecall.biz

Previously, previously, previously, previously, previously, previously.
Higgins Time
index 7166380..5e27d85 100644
--- a/asia
+++ b/asia
@@ -2939,15 +2939,34 @@ Link Asia/Qatar Asia/Bahrain
#
Previously, previously, previously, previously, previously, previously, previously.
Major Open Source Project Revokes Access to Companies That Work with ICE

On Tuesday, the developers behind a widely used open source code-management software called Lerna modified the terms and conditions of its use to prohibit any organization that collaborates with ICE from using the software. Among the companies and organizations that were specifically banned were Palantir, Microsoft, Amazon, Northeastern University, Motorola, Dell, UPS, and Johns Hopkins University. [...]
"Recently, it has come to my attention that many of these companies which are being paid millions of dollars by ICE are also using some of the open source software that I helped build," Jamie Kyle, an open source developer and one of the lead programmers on the Lerna project, wrote in a statement. "It's not news to me that people can use open source for evil, that's part of the whole deal. But it's really hard for me to sit back and ignore what these companies are doing with my code." [...]
Before he changed the license, Kyle left a comment on Palantir's Github asking the company to stop using the software. "Apologies to any contributors who aren't employees of Palantir, but to those who are, please find jobs elsewhere and stop helping Palantir do horrible things," Kyle wrote last week, linking to an article in The Intercept about the company's collaboration with ICE. "Also, stop using my tools. I don't support you and I don't want my work to benefit your awful company." [...]
After Kyle discussed his concerns with some of the other lead developers on the Lerna project, they assented to a change to the Lerna license that would effectively bar any organization that collaborates with ICE from continuing to use the software. This led to some developers calling the change illegitimate and lamenting that it technically meant the project was no longer open source. [...]
"I've been around the block enough to know how every company affected is going to respond," Kyle told me. "They're not going to try and find a loophole. I kinda hope they do try to keep using my tools though -- I'm really excited about the idea of actually getting to take Microsoft, Palantir or Amazon to court."
As for the hate he has received online about how open source projects shouldn't be politicized, Kyle said this misses the point.
"I believe that all technology is political, especially open source," he told me. "I believe that the technology industry should have a code of ethics like science or medicine. Working with ICE in any capacity is accepting money in exchange for morality. I am under no obligation to have a rigid code of ethics allowing everyone to use my open source software when the people using it follow no such code of ethics."
Previously, previously, previously, previously, previously, previously, previously.
U.S. Senator Bans Funding for Beerbots That Don't Exist
None of the amounts appropriated or otherwise made available by this Act may be obligated or expended for the development of a beerbot or other robot bartender.The issue here is that Senator Flake is conflating a student demonstration of how research could potentially be applied (delivering beer) with the fundamental objective of the research (in this case, multi-robot planning under uncertainty). Senator Flake also does not make any reference to what the objective of the research actually was: solving real-world logistics challenges. Instead, he seems to think that MIT was using government funding to develop a commercial robotic bartender, and his solution is to amend the DoD budget to prevent something that wasn't even happening in the first place, from happening again. [...]
"This is unlikely to actually be a 'misunderstanding'." Instead, Levitan says, Senator Flake is most likely using this research as an opportunity to take on supposedly wasteful spending, by finding perfectly reasonable government funded research projects that can, says Levitan, "be made to sound ridiculous when put a certain way. He almost certainly does it on purpose, ignoring the true value of the research and counting on the public to not be well enough informed to push back. And no fact-checking happened because that would have ruined the bit."
Previously, previously, previously, previously, previously, previously, previously, previously, previously.
now-you-have-two-problems.el

Yes:
PCRE has a complicated syntax and semantics, only some of which can be translated into Elisp. The following subset of PCRE should be correctly parsed and converted:
- parenthesis grouping
( .. ) , including shy matches(?: ... ) - backreferences (various syntaxes), but only up to 9 per expression
- alternation |
- greedy and non-greedy quantifiers *, *?, +, +?, ? and ?? (all of which are the same in Elisp as in PCRE)
- numerical quantifiers {M,N}
- beginning/end of string \A, \Z
- string quoting \Q .. \E
- word boundaries \b, \B (these are the same in Elisp)
- single character escapes \a, \c, \e, \f, \n, \r, \t, \x, and \octal digits (but see below about non-ASCII characters)
- character classes [...] including Posix escapes
- character classes \d, \D, \h, \H, \s, \S, \v, \V both within character class brackets and outside
- word and non-word characters \w and \W (Emacs has the same syntax, but its meaning is different)
- s (single line) and x (extended syntax) flags, in regexp literals, or set within the expression via
(?xs-xs) or(?xs-xs: .... ) syntax- comments
(?# ... ) Most of the more esoteric PCRE features can't really be supported by simple translation to Elisp regexps. These include the different lookaround assertions, conditionals, and the "backtracking control verbs"
(* ...)
I am sad to report, however, that I can't get it to work in either xemacs 21.5.28 or emacs 22.1.1. (And MacPorts won't let you install emacs and xemacs simultaneously! How partisan!)
Amusing as it would have been had they tried to translate from one regexp syntax to another using regexps... they did not do that.
Also, my heart grew three sizes when I saw that the first line of the file contains
Previously, previously, previously, previously, previously, previously, previously, previously.