Stephen Davies, Javier Velez-Morales, & Roger King (2005), "Building the memex sixty years later: trends and directions in personal knowledge bases", Department of Computer Science, University of Colorado at Boulder. The Wikipedia article on personal knowledge bases (PKBs) is basically a summary of the technical report. The report defined personal knowledge base systems, described their benefits, reviewed relevant fields of research, and compared systems in terms of several aspects of their data models: structural framework, knowledge elements, schema, and the role of transclusion. This report is the most comprehensive publication I've read that compares PKB systems according to their key features.

Fashion is a non-verbal communication that can represent one’s political and religious beliefs, gender identity, occupation, and essence. Whether intentional or not, the way that you dress can send a message to others about how you view yourself and how you want to be seen.

Diet YAML is a light weight version of YAML that removes much of the complex aspects of the mainline YAML specification.

paranoia has some surprising behaviour (like overriding ActiveRecord's delete and destroy) and is not recommended for new projects. See discard's README for more details. Paranoia will continue to accept bug fixes and support new versions of Rails but isn't accepting new features.

yield is a bit of laguage level magic that only works in the context of a method.

Automated personalization, localization, recommendation, f iltering, classif ication, evaluation, aggregation, synthetization, or ad hoc generation of information are similarly pervasive practices that do not require explicit user input to select, sequence, arrange, or modulate some set of digital items

Search has become a dominant means to access and order the masses of digital and dataf ied bits and pieces that clutter the environments we inhabit.

Current ruby releases generate *.tar.gz, *.tar.bz2, *.tar.xz, and *.zip. But I think we can stop generating *.tar.bz2. I think *.tar.bz2 are less merit. For better size, *.tar.xz exist. For better compatibility, *.tar.gz and *.zip exist.

In other words, i18n allows applications to support and satisfy the needs of multiple locales, thus “enabling” l10n.

The person was transported to Doctor's West in critical condition.

HBCC is the most common form of nonparental child care for infants and toddlers

Moving forward I'd rather see {#await} being removed than adding more {#await}. But that's just from my experience and I'm sure there are use-cases for it.

Persisting across apps Your notifications can persist across multiple apps / page reloads, as long as they use this library. This is useful for a scenario where you show a notification and then redirect the browser to a different application, or trigger a full reload of the page. This is completely automatic and uses session storage.

With firefox 88 it won't work anymore, now navigator.webdriver is always true when maionette is enabled.

The release of Capybara 2.0.0 removed the wait_until method from the API. This seems to have frustrated a few people,

Update API usage of the view helpers by changing javascript_packs_with_chunks_tag and stylesheet_packs_with_chunks_tag to javascript_pack_tag and stylesheet_pack_tag. Ensure that your layouts and views will only have at most one call to javascript_pack_tag or stylesheet_pack_tag. You can now pass multiple bundles to these view helper methods.

The WebSocket Protocol is designed on the principle that there should be minimal framing (the only framing that exists is to make the protocol frame-based instead of stream-based and to support a distinction between Unicode text and binary frames). It is expected that metadata would be layered on top of WebSocket by the application Fette & Melnikov Standards Track [Page 9] RFC 6455 The WebSocket Protocol December 2011 layer, in the same way that metadata is layered on top of TCP by the application layer (e.g., HTTP). Conceptually, WebSocket is really just a layer on top of TCP that does the following: o adds a web origin-based security model for browsers o adds an addressing and protocol naming mechanism to support multiple services on one port and multiple host names on one IP address o layers a framing mechanism on top of TCP to get back to the IP packet mechanism that TCP is built on, but without length limits o includes an additional closing handshake in-band that is designed to work in the presence of proxies and other intermediaries Other than that, WebSocket adds nothing. Basically it is intended to be as close to just exposing raw TCP to script as possible given the constraints of the Web. It's also designed in such a way that its servers can share a port with HTTP servers, by having its handshake be a valid HTTP Upgrade request. One could conceptually use other protocols to establish client-server messaging, but the intent of WebSockets is to provide a relatively simple protocol that can coexist with HTTP and deployed HTTP infrastructure (such as proxies) and that is as close to TCP as is safe for use with such infrastructure given security considerations, with targeted additions to simplify usage and keep simple things simple (such as the addition of message semantics).

Are you becoming a fan of the Clubhouse app or you’re one of them who is planning to build a similar app? In both cases, you must know about the important features of the Clubhouse app.

The emphasis was made on a raw CDP protocol because Chrome allows you to do so many things that are barely supported by WebDriver because it should have consistent design with other browsers.

The main (IMO) feature of MQTT – quality of service – doesn't make sense in our case: if a WebSocket server is down and doesn't receive broadcast messages (through HTTP/Redis/queue), it's likely not to handle client connections too.

While rails does have nice CSRF protection, in my instance it limited me.

if you just need a screenshot of a webpage, that’s built in:

When fetch runs on the server, the resulting response will be serialized and inlined into the rendered HTML. This allows the subsequent client-side load to access identical data immediately without an additional network request.

o help us meet this vision, the frontend should use GraphQL in preference to the REST API for new features.

Local development and testing has huge advantages, but sometimes one needs to test web applications against their real-world domain name. Editing /etc/hosts is a pain however, and error prone. Node Foreman can start up an HTTP forward proxy which your browser can route requests through. The forward proxy will intercept requests based on domain name, and route them to the local application.

Screen and Tmux are used to add a session context to a pseudoterminal, making for a much more robust and versatile solution. For example, each provides terminal persistence, allowing a user to disconnect from one computer and then connect later from another computer.

Apparently when you create a subclass, that subclass's singleton class has # its superclass's singleton class as an ancestor.

Now VS Code's generic debugger UI supports all data breakpoint access types defined in the Debug Adapter Protocol as context menu actions in the VARIABLES view: Break on Value Read: breakpoint will be hit every time a variable gets read. Break on Value Change: breakpoint will be hit every time a variable gets changed (this action was previously available). Break on Value Access: breakpoint will be hit every time a variable is read or changed.

_Underline_

Title: "goal the use case is trying to satisfy"[23]:101 Main Success Scenario: numbered list of steps[23]:101 Step: "a simple statement of the interaction between the actor and a system"[23]:101 Extensions: separately numbered lists, one per Extension[23]:101 Extension: "a condition that results in different interactions from .. the main success scenario". An extension from main step 3 is numbered 3a, etc.

Use the button to get a sharable link to the page with annotations.

and the --enable-gui=<gui> e.g. (--enable-gui=gnome for the Gnome Gui).

How to install VIM with all options/features? - VIM

If you want to compile youself you can pass the --with-features=huge to the configure script. Note, however, this does not enable the different language bindings because those are mostly optional and also the various GUIs need to enabled specifically, because you can have only one gui.

If you call ./configure --enable-gui=auto, the build process will automatically build against whichever GUI libraries are available. A cursory glance suggests that gtk2 will be prioritised over gnome2.

Software that is not currently being used gradually becomes unusable as the remainder of the application changes.

Infrequently used portions of code, such as document filters or interfaces designed to be used by other programs, may contain bugs that go unnoticed. With changes in user requirements and other external factors, this code may be executed later, thereby exposing the bugs and making the software appear less functional.

now that I realize how easy it is to just manually include this in my app: <%= javascript_include_tag 'xray', nonce: true if Rails.env.development? %> I regret even wasting my time getting it to automatically look for and add a nonce to the auto-injected xray.js script

Another solution is using the Safe Navigation Operator &. introduced in Ruby 2.3 which is a bit better because this is a language feature rather than an opinionated runtime environment pollution

ActiveInteraction provides detailed errors for easier introspection and testing of errors. Detailed errors improve on regular errors by adding a symbol that represents the type of error that has occurred.

support round-tripping (assigning the submitted params again)

Folding This is the one function whose name is confusing because many products use the term for what we called “collapsing” above. For this article, collapsing is the process of making whole headers and paragraphs invisible, tucking them up under a “parent.” Folding is a different kind of tucking under; it works on paragraphs and blocks to reduce them to a single line, hiding the rest. A simple case of folding might involve a long paragraph that is reduced to just the first line—plus some indication that it is folded; this shows that a paragraph is there and something about its content without showing the whole thing. Folding is most common in single-pane outline displays, and a common use is to fold everything so that every header and paragraph is reduced to a single line. This can show the overall structure of a huge document, including paragraph leaves in a single view. You can use folding and collapsing independently. At one time, folding was one of the basics of text editors, but it has faded somewhat. Now only about half of the full-featured editors employ folding. One of the most interesting of these is jEdit. It has a very strong implementation of folding, so strong in fact it subsumes outlining. Though intended as a full editor, it can easily be used as an outliner front end to TeX-based systems. jEdit is shown in the example screenshot in both modes. The view on the right shows an outline folded like MORE and NoteBook do it, where the folds correspond to the outline structure. But see on the left we have shifted to “explicit folding” mode where blocks are marked with triple brackets. Then these entire blocks can be folded independent of the outline. Alas, folding is one area where the Mac is weak, but NoteBook has an implementation that is handy. It is like MORE’s was, and is bound to the outline structure, meaning you can only fold headers, not arbitrary blocks. But it has a nice touch: just entering a folded header temporarily expands it.

If a reviver is specified, the value computed by parsing is transformed before being returned.

This decorators proposal deliberately omits these features, in order to keep the meaning of decorators "well-scoped" and intuitive, and to simplify implementations, both in transpilers and native engines.

However, this coalescing was very complicated, both in the specification and implementations, due to the dynamism of computed property names for accessors. Coalescing was a big source of overhead (e.g., in terms of code size) in polyfill implementations of "Stage 2" decorators.

Long ago, the standards deities gifted us <style scoped>, before removing it in favour of the arguably less-useful shadow DOM encapsulation mechanism.

👍 Can it notify user while field is being validated? 👍 Can it stop performing remaining validators if there is a validator that the field does not pass? 👍 Can it perform the validation only when the field value exceed a given number of characters? 👍 Can it postpone the validation for a given number of seconds from the moment user stops fill in the field?

The goal is to bring element creation down to this logic:

There is a killer feature of vDOM that Svelte has nothing to replace with. It is the ability to treat component hierarchy as an object.

It provides several capabilities that are difficult to achieve with React alone, while being compatible with the newest features of React.

A new option --proximate=N groups together lines of output that are within N lines of each other in the file. This is useful when looking for matches that are related to each other.

Also Svelte is so great because developer do not need to worry about class names conflict, except of passing (global) classes to component (sic!).

TBH It is a bit disheartening to see this issue closed when all proposed solutions do not sufficiently solve the issue at hand, I really like svelte but if this is how feature requests are handled I am probably not going to use it in the future.

Update: As best I can tell, <style scoped> has been removed from the specs and even browsers that were supporting it have pulled it. Even as I write this update (August 2017) scoped styles are arguably more popular and desirable than ever before.

Co-editing, commenting +(co-editing only) +

it supports dynamic loading and catalog-driven operations to let users customize its data types, functions, and more.

what makes it different is that you are free to choose the highlight colors you use

Unfortunately, the WordPress.org plugin repository doesn’t provide a way to maintain your plugin with Git.

Some months ago, I wrote about using Git and Github with the wordpress.org plugin repository.

I wish Mozilla would recognize the importance of built-in translation that Google Chrome and Microsoft Edge have.

The “universal” label that has been slapped on to it is superfluous, but it does have its merits. Now that we have a commonly known term to refer to environment agnostic JavaScript code, it allows library authors to list it as a feature and be fashionable doing it. I’m happy with the term “universal” being fashionable because it makes developers think about their dependencies on the runtime environment. In the end this will help the JavaScript ecosystem mature and allow libraries to be used everywhere.

[link](url){:target="_blank"} Works for jekyll or more specifically kramdown, which is a superset of markdown, as part of Jekyll's (default) configuration. But not for plain markdown. ^_^

For ghost markdown use: [Google](https://google.com" target="_blank) Found it here: https://cmatskas.com/open-external-links-in-a-new-window-ghost/

since mobile Chrome still doesn't support extensions (Google plz)

Yes, it’s been deprecated. Why? Because too few people were using it to make it worth the time, money, and energy to maintain. In truth, although I sometimes disagree with the operator changes, I happen to agree with this one. Maintaining ALL of the synonyms takes real time and costs us real money. Supporting this operator also increases the complexity of the code base. By dropping support for it we can free up a bunch of resources that can be used for other, more globally powerful changes.

Alternatively, you can use the Explore function to ask Google Sheets any number of questions about your to do list. It'll give you suggestions like "Most frequent Task" or "What percentage of Tag is [tag name]" and so on. This can give you insight into what you're working on the most and how you're spending your time, which can help you plan your workdays more productively.