billion-dollar business that comprises of nothing but others' confidence that it is worth something.
To be honest that is an accurate description of the whole stock exchange system.
2711 publicly visible posts • joined 22 Jun 2009
habitude, hackable, hackette, hairlike, hairline, hairwove, halazone, halflife, halfpace, halfpipe, halftime, halftone, halicore, halidome, halimote, hamulate, hamulose, handlike, handmade, handsome, hangable, hangfire, harambee, harangue, hardbake, hardcase, hardedge, hardface, hardline, hardnose, hardwire, harelike, harplike, hateable, hawklike, hawknose, headache, headcase, headgate, headline, headnote, headrace, headrope, healable, healsome, hearable, heatable, heatwave, hebetate, hebetude, hebraize, hegumene, hellfire, hellhole, hellkite, helotage, helpable, helpline, helpmate, hematine, hematite, hemipode, hemocyte, hemolyze, hemplike, henhouse, hepatise, hepatite, hepatize, herblike, herdlike, heritage, herniate, herolike, hesitate, hetaerae, hexamine, hexylene, hiccatee, highlife, highrise, hillside, hireable, hittable, hivelike, holdable, holesome, holocene, holotype, holydame, holytide, homelike, homemade, homepage, homesite, homicide, hominine, hominize, homodyne, homotype, homuncle, honeybee, hoodlike, hooflike, hooklike, hooknose, hooplike, hornlike, hornpipe, horologe, horrible, hoselike, hosepipe, hothouse, hotplate, huarache, huggable, huisache, humanise, humanize, hummable, huntable, hurtable, husklike, hylobate, hymnlike, hyoscine, hyperope, hypnotee, hypobole, hypogene.
Found it !
By any chance do you still have the reject message from that? That would be very interesting to see.
No, I don't. I tend not not collect trash for the fun of it. I have no doubt that you would be very interested in a free audit of your broken model. I -and many here, I suspect- can provide test cases, logs and stats from a variety of systems both senders and receivers. At a price.
Anyway, as anyone even vaguely familiar with the matter might tell you, the "reject message" would be of no interest at all since it's configured by the receiver. Unless you're trying to pinpoint which of your clients let slip that you are the cause of an abusive block, with potentially disastrous consequences. I understand that it would be damaging for your extortion-based business model. In my case the message was something about my IP being listed in some SpamHaus blocklist. It wasn't even in any of the many, many, many languages easily understood by "worldwide" SH operatives, like US English, US Ingrish or US English_Indian -optionnally US English_Boston_Litterary, US English_Southern_States or US English_Midwest but these may carry a surcharge. (none of them a problem for me, but still a concern).
They must have been sitting there waiting for you
The great thing about over-automation is that noone has to be sitting there at all. The automated system sees a direct-to-mx from a yahoo account to one of their customers, blam, IP blocked.
The main metric used by SpamHaus and their ilk to market their lists is the percentage of blocked inbound mails. A blocklists that blocks 86 % of inbound mails is marketted as better than a one blocking "only" 85 % of inbound mails, regardless of false positives. False negatives are visible to the client (the receiver, who pays SH) so they MUST not have them, but false positives are only visible by the sender, who may not be a client and may not have an alternative way of contacting the receiver to report abusive blocks by SH, so who cares ? I actually suspect that SpamHaus clients are automatically added to a do-not-block list, too, even if they deny maintaining such a list.
If Spamhaus lists something(*) there's invariably a bloody good reason for it
Absolutely. In the case of my individual home IP addy, the reason is that I sent one email from a yahoo-hosted account to a fellow of mine who works at the local hospital ("protected" by SpamHaus) to refer a patient.
There is a reason. It's just absolutely idotic.
Spamhaus are worst than Equifax, because the methods are the same but their reach is far wider and they are more moronically entrenched in their sense of self-righteousness.
This happens because we have idle cores sitting around doing nothing. If we made faster cores instead of just throwing more of them at workloads that can't use them, we wouldn't need speculative executions and thus, no spectre. I wonder if IBM would <ant to revive the Power phylosophy.
I would like to reserve a special place in Hell for whoever thought it was a good idea to incorporate web elements into email.
I don't know what you're talking about. I will classify this snippet as "nonsense", that's what I do with the various claims I receive stating that the newest info was in blinking red bold MSComicSans as opposed to the superceded info which was in blue strikedthrough boring old Arial, and how can I not have seen the difference?
Email is for text. Information is most efficiently conveyed through articulate sentences.
Alas, more and more websites just don't work on it at all.
My policy for these is pretty much the same as it has been for decades regarding "your bowser doesn't support this website, please switch to [browser]" websites. In 2 words, rhyming with Duck Goo.
When a contact info is available, I also fire off an email to the webmaster to the same effect - phrased in more polite terms.
themes and styles in MS Word.
The features that are consistently inconsistent in large structured documents, almost impossible to re-use between documents of differing sizes and structures ? I've heard of those, used them even. I now stay way clear off them.
If I want kerning and ligatures I will use Lyx
LyX is a front-end to LaTeX, which pretty much negates your whole argument.
We will have to agree to disagree because I believe there is no shiny (and I did use image search and YouTube just to check and refresh my memory on what was available on UNIX, Mac, ST, Amiga, and even Archimedes) and you believe there is shiny.
OK so you do think I'm unable to change my mind when presented with evidence.
I will gladly admit, in the face of evidence, that my recollection of this era's user interfaces was biased (influenced by previous GUIs and by the fact that I did not interract much with GUIs at the time, mostly command line).
Why do you insist that we will have to disagree ?
Note that my intention was not to diss XWindow, in fact I'm (in)famous among my friends for using twm as my default desktop environment (until recently I've been using a Raspberry 2B as my main work machine for over 2 years, because with my settings it was -much- snappier than the MSWindows tower I was given, but that's a story for another day)
If you see no shiny, perhaps you don't remember what user interfaces looked like at the time.
On a sidenote, I don't adhere to the passive-agressive "we'll have to agree to disagree" motto. I am able to admit that I am wrong without holding a grudge, just prove me so. Halting a constructive discussion by saying, in essence, "I think you're wrong but I won't bother telling you why" always strikes me as unconstructive and borderly insulting.
I don't use LaTEX very much myself, I tend to favor Lout (by Jeffrey H. Kingston from down under) ; despite its limitations, it does pretty much everything I want for print, in a (much) smaller package.
As for "simple html", as you put it, you may want to try AFT from Todd Coram.
On a separate note, in my experience unwanted spaces or newlines are "features" of WYSIWYG tools, I've never seen them in WYSIWYM tools. Unless you deliberately code extra spaces or newlines in, that is.
In the people I personnally know, "penis drawers" are roughly equally distributed between all genders. Mostly because the shapes involved are simple, distinctive, easily drawn with only connected lines, and the conveyed sillyness is immediately perceived by the viewer.
Note that the "symbol" is almost always drawn erect and "upwards", because sideways it woud be an antique gun on wheels, °I° is just a face, and a shrivelled penis is as difficult to render as a vulva - i.e. too much effort. The female equivalent would be (.Y.) , which is again used equally by all genders but VERY difficult to render with connected lines.
Don't assume gender bias until you have ruled out gratuitous silliness and laziness.
like %name% in the body
I guess you read your emails as plaintext, like a sensible person would. This %name% thing is the hallmark of an email tool that relies on client-side code execution. In my previous job I received quite a lot of -legit- emails ending with "<signature>". Silly MS.
there might be also interesting traces in email header) but can't be bothered. Someone will, eventually.
The last series I received were sent from a -most probably miconfigured- server at a foodstuff manufacturing company in Italy. I notified the abuse@ addy as I always do, and I'm not holding my breath as I always don't.
"The levels of sophistication involved in this attack indicate the involvement of a foreign State Actor. Russian and Chinese governments in particular are known to have a knowledge of the existence of Twitter. While the attack was promptly foiled by our elite cyber units, it is important to note that most major industries in the UK use Twitter. In order to prevent a massive disruption of the British economy by foreign hostile actors, it is crucial to keep us very well funded."
IBM just bought Red Hat. DB2 for Open, which was an also-ran to date, may be about to become a Thing. On the Cloud front Oracle can't reallistically compete with Amazon, on the DB front it can't compete with Big Blue and it's newly-aquired fedora. Time to innovate, if you still know how to !
"Sec 101 : This is my passphrase for El Reg" is
- unique
- easy to remember
- virtually uncrackable by automated means
- tedious to type
- not even close to my actual credentials
- as weak as "password123" as soon as your system is compromised, because keylogger.
The "remembering" part is secondary in this problem. Login security will always be hampered by
- Joe Public's unwillingness to type a 20+ characters password to let the world know of their opinion on May's or Trump's latest tweet (see the success of the oh-so-very-innocuous "login with Facebook" option on various websites)
- the hard fact that once your system is compromised, any input, output or locally stored data (including in RAM) can be snooped on (although the efforts needed to do so may vary depending on your security measures).
I was thinking that campus cowboys are getting a tad ridiculous, but again I did not think of this angle. Although these are campus cops and not high-firepower regular cops, they still do sport pepper spray and sometimes tazers. They do tend to occasionnally over-react with those "sub-lethal" tools of theirs.
The way systemd has been pushed means that a lot of userland stuff now assumes it's there (even without explicitely depending on it, in some cases). To counter the trend, there needs to be enough systems out there that do not run systemd.
Also, many managers will be reluctant to switch production from RHEL to *BSD. The switch to Devuan is easier to promote.
Why not BSD? I think both of those are equally effective choices.
Sure, but Joe Public -and non-technical management- has heard of Linux and even often tried it /deployed it in production, while *BSD is still confidential outside some IT circles. And Devuan benefits from the rather impressive hardware support and application base of Debian (and to some exxtent, of RedHat)
By the way, if you do need to patch, you can find the perfect patch at freebsd.org
While I kinda* agree with the general sentiment, the reason why systemd became an issue at all is that it is backed by RedHat, the most trusted *NIX distro in the Big Biz world (unlikely to change since they were just gobbled by the most trusted Big Iron company in the Big Biz world...). That gives systemd considerable traction. I do currently work for Big Biz. Big Biz doesn't care for reliablity, stability or elegance terribly much, these are just bonusses. Big Biz cares for support contracts, monetary penalties, and above all, for "case open with the supplier so it's not our problem anymore" clauses.
Something is rotten in the State of IT. Goodpractices, I knew thee well, etc. But again, I'm old enough to remember that it's always been the case. Same general mindset, same errors, different offenders. The only difference is that some of us here were hoping for an improvement when Linux hit the limelight, and that's only a generation thing. Hope is a renewable resource, disappointment is a constant ;-)
Resistance is NOT futile though. The most efficient way of resistance IMHO is Devuan at this time, not *BSD, because of the trust built around Linux by now-traitors RHEL and Debian (to cite only 2). The path of least resistance is often the fastest. Not that I don't believe in unicorns, mind : I am myself eagerly waiting for -and occasionnally minutely contributing to- the Raise of the Mighty GNU HURD Complete With Its Own MACH Microkernel. Not holding my breath though (renewable resources, constants, etc).
*For personnal -and rather shallow- reasons I prefer dabbling with DragonFlyBSD myself, but that's besides the point
Boieng is notoriously struggling (to use the weakest possible term) with its space program, suffers very serious reliability issues on some of its latest crafts (even resorting to "the pilot held it wrong", an excuse more often used by peddlers of less-critical pieces of tech) and recently bought Embraer to cover for their inability to develop reliable short-courriers of their own (OK, this last one might be a bit of an extrapolation).
There are also allegations that data seized by three-letters US agencies under various "terrist" acts were at some point fed directly to various US stakeholder, including tipping local authorities on drug smugglers but also giving Boeing details on Airbus tech. That practice allegedely stopped, perhaps leeaving a gap in information-gathering by one or several parties.
Meanwhile, China just successfuly sent a craft where No One had Ever Been Before (no, going to the hidden side of the Moon is no small feat).
Pick the most probable culprit.