Random Articles (Page 2)
Have a deep view into what people are curious about.
π Cabin Fever
Cabin fever refers to the distressing claustrophobic irritability or restlessness experienced when a person, or group, is stuck at an isolated location or in confined quarters for an extended period of time. A person may be referred to as stir-crazy, derived from the use of stir to mean 'prison'.
A person may experience cabin fever in a situation such as being isolated within a vacation cottage out in the country, spending long periods underwater in a submarine, or being otherwise isolated from civilization. During cabin fever, a person may experience sleepiness or sleeplessness, have a distrust of anyone they are with, or have an urge to go outside even in adverse conditions such as poor weather or limited visibility. The concept is also invoked humorously to indicate simple boredom from being home alone for an extended period of time.
Cabin fever is not itself a disease and there is no prognosis. However, related symptoms can lead the sufferer to make irrational decisions that could potentially threaten their life or the life of the group with whom they are confined. Some examples would be suicide or paranoia, or leaving the safety of a cabin during a terrible snow storm that one may be stuck in.
Discussed on
- "Cabin Fever" | 2020-03-20 | 76 Upvotes 48 Comments
π Circle-Ellipse Problem
The circleβellipse problem in software development (sometimes called the squareβrectangle problem) illustrates several pitfalls which can arise when using subtype polymorphism in object modelling. The issues are most commonly encountered when using object-oriented programming (OOP). By definition, this problem is a violation of the Liskov substitution principle, one of the SOLID principles.
The problem concerns which subtyping or inheritance relationship should exist between classes which represent circles and ellipses (or, similarly, squares and rectangles). More generally, the problem illustrates the difficulties which can occur when a base class contains methods which mutate an object in a manner which may invalidate a (stronger) invariant found in a derived class, causing the Liskov substitution principle to be violated.
The existence of the circleβellipse problem is sometimes used to criticize object-oriented programming. It may also imply that hierarchical taxonomies are difficult to make universal, implying that situational classification systems may be more practical.
Discussed on
- "Circle-Ellipse Problem" | 2011-04-17 | 21 Upvotes 20 Comments
π PainStation
Painstation is an art object and arcade game based on Pong developed by the artists' group "/////////fur//// art entertainment interfaces", with pain feedback.
Discussed on
- "PainStation" | 2023-12-12 | 213 Upvotes 58 Comments
π The eastern coyote, a wild N. American canine with coyote-wolf and dog parentage
The eastern coyote (Canis latrans var.) is a wild North American canine of both coyote and wolf parentage. The hybridization likely first occurred in the Great Lakes region, as western coyotes moved east. It was first noticed during the early 1930s to the late 1940s, and likely originated in the aftermath of the extirpation of the gray wolf in southeastern Ontario, Labrador and Quebec, thus allowing coyotes to colonize the former wolf ranges and mix with the remnant wolf populations. This hybrid is smaller than the eastern wolf and holds smaller territories, but is larger and holds more extensive home ranges than the typical western coyote.
Discussed on
- "The eastern coyote, a wild N. American canine with coyote-wolf and dog parentage" | 2018-02-25 | 47 Upvotes 11 Comments
π Capability Based Security
Capability-based security is a concept in the design of secure computing systems, one of the existing security models. A capability (known in some systems as a key) is a communicable, unforgeable token of authority. It refers to a value that references an object along with an associated set of access rights. A user program on a capability-based operating system must use a capability to access an object. Capability-based security refers to the principle of designing user programs such that they directly share capabilities with each other according to the principle of least privilege, and to the operating system infrastructure necessary to make such transactions efficient and secure. Capability-based security is to be contrasted with an approach that uses hierarchical protection domains.
Although most operating systems implement a facility which resembles capabilities, they typically do not provide enough support to allow for the exchange of capabilities among possibly mutually untrusting entities to be the primary means of granting and distributing access rights throughout the system. A capability-based system, in contrast, is designed with that goal in mind.
Capabilities as discussed in this article should not be confused with POSIX 1e/2c "Capabilities". The latter are coarse-grained privileges that cannot be transferred between processes.
Discussed on
- "Capability Based Security" | 2015-12-06 | 44 Upvotes 35 Comments
π Demon Core
The demon core was a spherical 6.2-kilogram (14Β lb) subcritical mass of plutonium 89 millimetres (3.5Β in) in diameter, that was involved in two criticality accidents, on August 21, 1945 and May 21, 1946. The core was intended for use in a third nuclear weapon, but remained in use for testing after Japan's surrender. It was designed with a small safety margin to ensure a successful explosion of the bomb. The device briefly went supercritical when it was accidentally placed in supercritical configurations during two separate experiments intended to guarantee the core was indeed close to the critical point. The incidents happened at the Los Alamos Laboratory in 1945 and 1946, both resulting in the acute radiation poisoning and subsequent deaths of scientists: Harry Daghlian and Louis Slotin. After these incidents the spherical plutonium core was referred to as the "demon core".
Discussed on
- "Demon Core" | 2019-06-17 | 153 Upvotes 55 Comments
- "The Demon Core" | 2012-10-07 | 20 Upvotes 1 Comments
π CS Alert (1890)
CS Alert, or HMTS Alert, was a cable-laying ship that had a significant role in World War I. She was launched in 1871 for the Submarine Telegraph Company with the name The Lady Carmichael. In 1890 the ship was acquired by the General Post Office (GPO) as part of the nationalisation of the British telegraph network. At the outbreak of World War I, Alert was immediately dispatched to cut German telegraph cables in the English Channel, seriously damaging Germany's ability to securely communicate with the rest of the world. Alert was taken out of service as a cable ship in 1915 but her cable-handling gear was retained for fitting on her replacement. After the war, she worked as a merchant ship under various names, finally being wrecked at Redcar under the name Norham in 1932.
Discussed on
- "CS Alert (1890)" | 2019-08-29 | 35 Upvotes 17 Comments
π Fundamental Attribution Error
In social psychology, fundamental attribution error (FAE), also known as correspondence bias or attribution effect, is the tendency for people to under-emphasize situational explanations for an individual's observed behavior while over-emphasizing dispositional and personality-based explanations for their behavior. This effect has been described as "the tendency to believe that what people do reflects who they are".
Discussed on
- "Fundamental Attribution Error" | 2013-05-06 | 41 Upvotes 12 Comments
- "Fundamental attribution error" | 2010-02-06 | 30 Upvotes 15 Comments
π Doorway Effect
The 'doorway effect' or βlocation updating effectβ is a replicable psychological phenomenon characterized by short-term memory loss when passing through a doorway or moving from one location to another. We tend to forget items of recent significance immediately after crossing a boundary and often forget what we were thinking about or planning on doing upon entering a different room. Research suggests that this phenomenon occurs both at literal boundaries (e.g., moving from one room to another via a door) and metaphorical boundaries (e.g., imagining traversing a doorway, or even when moving from one desktop window to another on a computer).
Memory is organized around specific events or episodes, such as attending a lecture or having a family meal, rather than being a continuous stream interrupted by sleep. This organization is called episodic memory, which involves receiving and storing information about events that are temporarily dated, along with their time and place relationships.
Numerous psychological studies have indicated that the external context, including the location where events occur, plays a significant role in how memories are separated. This context helps establish distinctions between different remembered events. Memories of events that happen in the environment we're currently in are easier to access compared to those from different places. As a result, when we experience spatial changes and move to a different location, it can act as a boundary marker that separates and categorizes our continuous flow of memories into distinct segments.
Discussed on
- "Doorway Effect" | 2024-02-08 | 313 Upvotes 146 Comments
π Zero Knowledge Proofs
In cryptography, a zero-knowledge proof or zero-knowledge protocol is a method by which one party (the prover) can prove to another party (the verifier) that they know a value x, without conveying any information apart from the fact that they know the value x. The essence of zero-knowledge proofs is that it is trivial to prove that one possesses knowledge of certain information by simply revealing it; the challenge is to prove such possession without revealing the information itself or any additional information.
If proving a statement requires that the prover possesses some secret information, then the verifier will not be able to prove the statement to anyone else without possessing the secret information. The statement being proved must include the assertion that the prover has such knowledge, but not the knowledge itself. Otherwise, the statement would not be proved in zero-knowledge because it provides the verifier with additional information about the statement by the end of the protocol. A zero-knowledge proof of knowledge is a special case when the statement consists only of the fact that the prover possesses the secret information.
Interactive zero-knowledge proofs require interaction between the individual (or computer system) proving their knowledge and the individual validating the proof.
A protocol implementing zero-knowledge proofs of knowledge must necessarily require interactive input from the verifier. This interactive input is usually in the form of one or more challenges such that the responses from the prover will convince the verifier if and only if the statement is true, i.e., if the prover does possess the claimed knowledge. If this were not the case, the verifier could record the execution of the protocol and replay it to convince someone else that they possess the secret information. The new party's acceptance is either justified since the replayer does possess the information (which implies that the protocol leaked information, and thus, is not proved in zero-knowledge), or the acceptance is spurious, i.e., was accepted from someone who does not actually possess the information.
Some forms of non-interactive zero-knowledge proofs exist, but the validity of the proof relies on computational assumptions (typically the assumptions of an ideal cryptographic hash function).
Discussed on
- "Zero Knowledge Proofs" | 2013-04-14 | 60 Upvotes 19 Comments