1,938 karma · joined February 7, 2014
,----------,
/........../ \
/....______/ \
/..../\ \ \
/..../ \ \ \
/____/ \_____\ \
\ \ /...../ /
\ \ /...../ /
\ \/_____/ /
\ \ /
\ \ /
'----------'
sebboh (registered) @ freenodedave@the-good-guys.net
[ my public key: https://keybase.io/sebboh; my proof: https://keybase.io/sebboh/sigs/esqX2ECySnczctOPm2xHjchgJ3v6SNNcENJba2SoUyQ ]
I stand by my assertion that nobody is trying to "hide" the "superbug" problem.
The human tendency to not self-report failures is a thing. But it's not some kind of biohazard conspiracy.
And one more thing about the death certificates...
> In a statement emailed to Reuters, Frieden said:
> "While death certificates provide helpful
> information, the unfortunate reality is that they
> don't provide in-depth clinical information."
I'm guessing that Frieden, the boss of the whole CDC, went on to say something like: "But it makes sense, because death certificates are primarily legal records. The clinical information lives in medical records." OR, OR, something more accurate. That's why he gets the big bucks. :)I don't think hospitals have any motivation to hide antibiotic-resistant infections ("superbugs") specifically. HOWEVER, the motive to hide hospital-acquired infections[0] is clear!
Here's some mud in the water: what's the difference between a HAI with some bug that is easily killed by antibiotics vs. an antibiotic resistant bug?
As for "tracking it in secret", that's one way to put it, but it will cloud your thinking. :) Your own medical records--specifically blood test lab results--have your name, address, and phone number on them. Consider replacing the word 'secret' with 'private' and re-working the whole thought.
Deathcerts is an interesting dataset. It's not the only one.
Even if death-by-MSRA isn't tracked, I assure you that MSRA itself is tracked.
There's a specific class of lab test called "antibiotic susceptibilities". The results report includes a bunch of numbers that represent just HOW resistant a particular bug is to a standard battery of antibiotics, broken down per antibiotic.
That data is transmitted from the labs that performed the test to the state health department where it is analyzed.
Fascinating article, but there's NO WAY that Reuters had that much contact with state public health folks without being aware that they track lab results. Misleading!
Edit: elaborated about the susceptibilities results.
Now back to my original point: there are things on the Schedule I list that can change people's lives. Some of the most interesting things on the list can, on first use, pull back the veil and allow the user to re-evaluate their most basic beliefs.
My argument is that the establishment does not benefit from people doing that, when so many of their workers have BS jobs.
The list might exist to protect the basic health and safety of our population, or it might exist to protect the status quo.
You say this stuff is great? Well don't be surprised it's on the list, then! :)
For the uninitiated: Some experiences change your life.
All schedule I substances might make a user quit their job. Period.
That's what the list means. There are LOTS of things that will merely kill you which are NOT on the list...
N.B. I have no idea what "Kratom", and "change your life" certainly doesn't always imply "for the better". Stay safe, kids, stay smart.
Things that seemed cool until I looked (even a little) closer at the people behind them: urbit, stockfighter, and ESR's homepage.
In my opinion, the author's goal was to make a blog post. So he searched around for something like an original thought... and he found a glimmer (merely) of a thought: that hand-typing helps you READ content better than copy&pasting does.
It's more of an observation, actually... An independently repeatable one, sure... :)
The recitals are awesome! I wish USAmerica would use this type of exposition in their legalese.
Hm, this is all I found so far about the practice: https://web.archive.org/web/20130622043635/http://eur-lex.eu...
Recital 15
==========
Third, measures going beyond such reasonable traffic management
measures might also be necessary to prevent impending network
congestion, that is, situations where congestion is about to
materialise, and to mitigate the effects of network congestion, where
such congestion occurs only temporarily or in exceptional
circumstances. The principle of proportionality requires that traffic
management measures based on that exception treat equivalent
categories of traffic equally. Temporary congestion should be
understood as referring to specific situations of short duration,
where a sudden increase in the number of users in addition to the
regular users, or a sudden increase in demand for specific content,
applications or services, may overflow the transmission capacity of
some elements of the network and make the rest of the network less
reactive. Temporary congestion might occur especially in mobile
networks, which are subject to more variable conditions, such as
physical obstructions, lower indoor coverage, or a variable number of
active users with changing location. While it may be predictable that
such temporary congestion might occur from time to time at certain
points in the network – such that it cannot be regarded as exceptional
– it might not recur so often or for such extensive periods that a
capacity expansion would be economically justified. Exceptional
congestion should be understood as referring to unpredictable and
unavoidable situations of congestion, both in mobile and fixed
networks. Possible causes of those situations include a technical
failure such as a service outage due to broken cables or other
infrastructure elements, unexpected changes in routing of traffic or
large increases in network traffic due to emergency or other
situations beyond the control of providers of internet access
services. Such congestion problems are likely to be infrequent but may
be severe, and are not necessarily of short duration. The need to
apply traffic management measures going beyond the reasonable traffic
management measures in order to prevent or mitigate the effects of
temporary or exceptional network congestion should not give providers
of internet access services the possibility to circumvent the general
prohibition on blocking, slowing down, altering, restricting,
interfering with, degrading or discriminating between specific
content, applications or services, or specific categories
thereof. Recurrent and more long-lasting network congestion which is
neither exceptional nor temporary should not benefit from that
exception but should rather be tackled through expansion of network
capacity.When we converse in person, the medium (air) doesn't discriminate. Let's have a 'Net like that.
What are you talking about?
These are the first 9, the other 10 are here: https://gist.github.com/daveloyall/a1112bb70412d77bebc809090...
Recital 1 =========
This Regulation aims to establish common rules to safeguard equal and non-discriminatory treatment of traffic in the provision of internet access services and related end-users’ rights. It aims to protect end-users and simultaneously to guarantee the continued functioning of the internet ecosystem as an engine of innovation.
Recital 2 =========
The measures provided for in this Regulation respect the principle of technological neutrality, that is to say they neither impose nor discriminate in favour of the use of a particular type of technology.
Recital 3 =========
The internet has developed over the past decades as an open platform for innovation with low access barriers for end-users, providers of content, applications and services and providers of internet access services. The existing regulatory framework aims to promote the ability of end-users to access and distribute information or run applications and services of their choice. However, a significant number of end-users are affected by traffic management practices which block or slow down specific applications or services. Those tendencies require common rules at the Union level to ensure the openness of the internet and to avoid fragmentation of the internal market resulting from measures adopted by individual Member States.
Recital 4 =========
An internet access service provides access to the internet, and in principle to all the end-points thereof, irrespective of the network technology and terminal equipment used by end-users. However, for reasons outside the control of providers of internet access services, certain end points of the internet may not always be accessible. Therefore, such providers should be deemed to have complied with their obligations related to the provision of an internet access service within the meaning of this Regulation when that service provides connectivity to virtually all end points of the internet. Providers of internet access services should therefore not restrict connectivity to any accessible end-points of the internet.
Recital 5 =========
When accessing the internet, end-users should be free to choose between various types of terminal equipment as defined in Commission Directive 2008/63/EC (1). Providers of internet access services should not impose restrictions on the use of terminal equipment connecting to the network in addition to those imposed by manufacturers or distributors of terminal equipment in accordance with Union law.
Recital 6 =========
End-users should have the right to access and distribute information and content, and to use and provide applications and services without discrimination, via their internet access service. The exercise of this right should be without prejudice to Union law, or national law that complies with Union law, regarding the lawfulness of content, applications or services. This Regulation does not seek to regulate the lawfulness of the content, applications or services, nor does it seek to regulate the procedures, requirements and safeguards related thereto. Those matters therefore remain subject to Union law, or national law that complies with Union law.
Recital 7 =========
In order to exercise their rights to access and distribute information and content and to use and provide applications and services of their choice, end-users should be free to agree with providers of internet access services on tariffs for specific data volumes and speeds of the internet access service. Such agreements, as well as any commercial practices of providers of internet access services, should not limit the exercise of those rights and thus circumvent provisions of this Regulation safeguarding open internet access. National regulatory and other competent authorities should be empowered to intervene against agreements or commercial practices which, by reason of their scale, lead to situations where end-users’ choice is materially reduced in practice. To this end, the assessment of agreements and commercial practices should, inter alia, take into account the respective market positions of those providers of internet access services, and of the providers of content, applications and services, that are involved. National regulatory and other competent authorities should be required, as part of their monitoring and enforcement function, to intervene when agreements or commercial practices would result in the undermining of the essence of the end-users’ rights.
Recital 8 =========
When providing internet access services, providers of those services should treat all traffic equally, without discrimination, restriction or interference, independently of its sender or receiver, content, application or service, or terminal equipment. According to general principles of Union law and settled case-law, comparable situations should not be treated differently and different situations should not be treated in the same way unless such treatment is objectively justified.
Recital 9 =========
The objective of reasonable traffic management is to contribute to an efficient use of network resources and to an optimisation of overall transmission quality responding to the objectively different technical quality of service requirements of specific categories of traffic, and thus of the content, applications and services transmitted. Reasonable traffic management measures applied by providers of internet access services should be transparent, non-discriminatory and proportionate, and should not be based on commercial considerations. The requirement for traffic management measures to be non-discriminatory does not preclude providers of internet access services from implementing, in order to optimise the overall transmission quality, traffic management measures which differentiate between objectively different categories of traffic. Any such differentiation should, in order to optimise overall quality and user experience, be permitted only on the basis of objectively different technical quality of service requirements (for example, in terms of latency, jitter, packet loss, and bandwidth) of the specific categories of traffic, and not on the basis of commercial considerations. Such differentiating measures should be proportionate in relation to the purpose of overall quality optimisation and should treat equivalent traffic equally. Such measures should not be maintained for longer than necessary.
Your post smells like spam. However, other posts on the same blog have content: https://fpgasite.wordpress.com/2016/08/09/pseudo-random-gene...
What's up? What is this blog for?
Would you accept that temacs[0] is written in C and emacs is written in emacs lisp?
I'd argue that sbcl is written in C and the sbcl common lisp implementation is written in common lisp.
Is that not the common way of viewing it?
0: https://www.gnu.org/software/emacs/manual/html_node/elisp/Bu...
In another comment, @bitwize says No. AutoCAD is written in C++. It has a crude Lisp as an extension language, [...]
Same story for emacs. It's written in C and implements something called "emacs lisp". I'm not inclined to call it crude, but few would defend it if I did... :)
But emacs is special, it's more "extension" than not. That means, the elisp-language extensions that it ships with make up the majority of the "basic" functionality of emacs.
> Also if not using asdf, the quickload form should be
> wrapped in an eval-when. It will fail If I Try to
> compile the file (C-c C-k) on a fresh session.
OH! Thank you... :) That's always bugged me!Unendorsed polyseme: Encryption Wizard for Oracle [http://www.relationalwizards.com/]
uh... How can I say this... :)
wut?
For those of you that might be interested in confirming or denying that the "no-name" version of MenuMeters does not contain any malicious code... Here are some links:
Original: http://www.ragingmenace.com/software/download/MenuMeters.tar...
Base of the fork: https://github.com/yujitach/MenuMeters/archive/f71e581819e3d...
You need to confirm that the base of the fork is a 1:1 exact match with the original.
If it is and you accept that, then here are all the differences between the latest version on github[1] and the original: https://github.com/yujitach/MenuMeters/compare/f71e581819e3d...
Footnotes:
1. That link is a moving target. If new commits come in today (or tomorrow), it will change.
2. This project has a health ecosystem of forks, some of which have newer commits than the one linked to in this HN thread.
3. Not like y'all ain't gonna download binaries to your macs anyway!
> "In 2019, the spacecraft will be far enough from the sun
> that we could image it directly with Hubble and figure
> out the rate of spin," said Ossing.
Nice.