the real problem is what we're layering the web on we shouldn't be doing the web over this kind of just simple file distribution system that works over TCP and you have to work really hard to put over anything else we should be putting the web over a distribution system that can deal with the distributed case that is offline first and uh this is are kind of like stats showing the usage of mobile apps versus uh the web and so on so this is a very real real thing

Utopia is a content-centric web application platform. It leverages the file-system to provide a mapping between logical resources and files on disk.

while true; do waitforsave assignment.ly; lily assignment.ly; say "done"; done

file transfers

OK, remember how, in several of my past issues, I've kept at you to create a "swipe file" of good ads, sales letters and so on? Not to mention all those headline cards? You do remember? Good!

From an organizational standpoint, the beauty of sermons is that each revolves around a specific theme. Accordingly, King could devote a single folder to each topic. He accumulated 166 folders, each with a title like “Loving your Enemies” (folder 1), “Why the Christian must Oppose Segregation” (folder 87), “Mental Slavery” (folder 113), and “The Misuse of Prayer” (folder 166). These folders contain King’s outlines; source material, like clippings from books; and drafts.

То, что мы будем называть Черным лебедем (с большой буквы), — это событие, обладающее следующими тремя характеристиками.

the modern textual archive format

Causal Deep Learning Authors:Jeroen Berrevoets, Krzysztof Kacprzyk, Zhaozhi Qian, Mihaela van der Schaar

Comedian Phyllis Diller had “gag file,” which is now housed at The Smithsonian: Phyllis Diller’s groundbreaking career as a stand-up comic spanned almost 50 years. Throughout her career she used a gag file to organize her material. Diller’s gag file consists of a steel cabinet with 48 drawers (along with a 3 drawer expansion) containing over 52,000 3-by-5 inch index cards, each holding a typewritten joke or gag.

Hanna BredenbeckCorp is a project assistant in the Division of Culture and the Arts.

In the end, I numbered and scanned 52,569 individual note cards from the Phyllis Diller gag file.

This joke card has a comic clipped from a newspaper glued to it. During the digitization process, the index card was put in a clear Mylar sleeve to prevent the comic, with its brittle glue, from being damaged or separated from the card.

While most of the joke cards are simply index cards with a joke typed on, others are more complicated. Some cards have strips of paper glued to them with longer jokes on those papers. Some cards have entire letter-size sheets of paper containing long jokes stapled to the cards. Some cards have comic strips, cut from the newspaper, glued to the cards. Other cards are not even cards but are just pieces of printer paper with jokes scribbled on them. These irregular cards were not stable enough to be sent through the feed scanner and had to be scanned one-by-one using a flatbed scanner, which slowed my progress.

I started my project by writing a small number, in pencil, on the back of each card. The numbers are used to keep track of the original drawer in which the card was located, as well as the card's position within that drawer. For example, the card numbered 15-0837 would be the 837th card in Drawer 15.

Oliar, Dotan; Sprigman, Christopher (2008). "There's No Free Laugh (Anymore): The Emergence of Intellectual Property Norms and the Transformation of Stand-Up Comedy". Virginia Law Review. 94 (8): 1848. JSTOR 25470605. Retrieved September 16, 2020. There is also evidence in the [Diller archive…at the Smithsonian in Washington, D.C.] file suggesting that Diller appropriated from other sources [apart from self-creation or using her writing team], including newspaper comic strips and comedy books. For example, a number of Diller's jokes about her dysfunctional marriage to her fictional husband 'Fang' appear to have been inspired by a comic strip, 'The Lockhorns,' that Diller followed obsessively over the course of nearly a decade. The Diller joke files contain hundreds of 'Lockhorns' panels cut out of newspapers and mounted on index cards.

"The [joke] file is like a tree," says Diller. "Leaves drop off, and new leaves are added—the new stuff pushes out the old." Along with this cache—Diller refers to it as "my life in one-liners"

Even the alphabetized categories evoke a laugh: "Science, Seasons, Secretary, Senile, Sex, Sex Symbols, Sex Harassment, Shoes, Shopping..." "Food Gripes, Foreign (incidents & personalities), Foundations (bra & underwear), Fractured Speech, Freeways, Friends, Frugality, Frustrations, Funerals, Funny Names..."

a steel filing cabinet of safe-like dimensions

“The file is like a tree,” Diller told the magazine’s Owen Edwards in 2007. “Leaves drop off, and new leaves are added—the new stuff pushes out the old.”

each typed on an index card and filed under such prophetic taglines as “Science, Seasons, Secretary, Senile, Sex, Sex Symbols, Sex Harassment, Shoes, Shopping…” and “Food Gripes, Foreign (incidents & personalities), Foundations (bra & underwear), Fractured Speech, Freeways, Friends, Frugality, Frustrations, Funerals, Funny Names…”

This beige metal cabinet is Phyllis Diller’s gag file, a categorized archive of the jokes Diller used in her stand-up comedy routines throughout her half-century long career. A small three drawer expansion of the gag file is also in NMAH’s collection (Catalog Number 2003.0289.01.02). The 48 drawers of the gag file, along with the 3 drawer expansion, contain a total of 52,569 3-by-5 inch index cards, each holding a typewritten joke or gag.

Phyllis Diller Gag File - Drawer No. 49, Part 1

Numbers on Cards The curatorial and collections teams are trying to learn more about the appearance of "No. #" on cards. Please transcribe this number on a separate line underneath the Date line, above the Joke line.

The digitization of Phyllis Diller’s index card collection was generously supported by Mike Wilkins and Sheila Duignan.

48 drawers (along with a 3 drawer expansion)

Photo: Hugh Talman, Smithsonian's National Museum of American History

Photo: Hugh Talman, Smithsonian's National Museum of American History.

on Aug. 12, the National Museum of American History is giving the artifact pristine treatment.WpGet the full experience.Choose your planArrowRight"Have You Heard the One . . . ? The Phyllis Diller Gag File" is an exhibition of the beige cabinet in the quiet Albert H. Small Documents Gallery.

Diller typed her jokes on index cards and filled 48 file drawers.

Most of the gags, written from the 1960s to the 1980s, are just like that—one per card. But a few that are more involved sometimes take a few cards to tell.

Most of the gags, written from the 1960s to the 1980s

But when Diller’s jokes came up for transcription last week, “they are going like gangbusters,” says Meghan Ferriter, project coordinator. “I think we actually gained about 115 new volunteers in one day.”

They were typed and meticulously filed into 48 drawers of a large, beige Steelmaster cabinet on wheels that she donated, along with a few of her wilder getups and wigs to the Smithsonian in 2003—less than a decade before her death in 2012 at 95.

SIMON: That's Heidi Rotbart, Phyllis Diller's longtime friend and producer. That gag file, as Phyllis Diller called it, is a piece of history, a hefty taupe filing cabinet filled with 53,000 alphabetized jokes.

HEIDI ROTBART: She would write a joke on a piece of paper, and her assistants would type them up on 3-by-5 cards and then place them in the joke file.

Three weeks and 52,569 jokes later, the job was completed.

Three weeks and 52,569 jokes later, the job was completed.

The joke file is a snapshot of American history.”

“I admire her ability for organization too. My jokes are still mostly in my head. She got hers on paper in alphabetical order.

Another important 20th-century thinker to rely on index cards was pioneering media theo-rist Harold Innis.18 The executors of his estate published a tome called The Idea File (1980),composed of 18 inches of index cards, plus five inches of reference cards. Innis had a selection ofhand-written index cards typed up and numbered, 1 through 339. It is unclear if these rumina-tions on television and art, communication and trade, secrecy and money, literature and the oraltradition, archives and history were intended to constitute a book project; the decision to publishthe cards balances the putative will to posterity of an author, and the potential embarrassmentof incomplete work. Clearly Innis intended to work synchronically rather than diachronically,to focus less on logical connections than on analogies, to practice pattern recognition—andthe associative links of a card index lend themselves perfectly to this kind of project.

he Automatic File & Index Co.

debían estarprotagonizados por extranjeros y tratar de cosas con las que no podía identificarme. Puesbien, la situación cambió cuando descubrí los libros africanos.No había muchos disponibles, y no eran tan fáciles de encontrar como los extranjeros.Pero gracias a escritores como Chinua Achebe y Camara Laye, mi percepción de laliteratura cambió. Comprendí que en la literatura también podía existir gente como yo,chicas con la piel de color chocolate cuyo pelo rizado no caía en colas de caballo.Empecé a escribir sobre asuntos que reconocía.5

The ID suffix was added because I use external tools to add notes to my vault so I needed a means to ensure there would never be a collision. For example, Alfred. If I accidentally typed the name of a note that already exists into it I didn’t want it to accidentally overwrite an existing note,

Use the Get-ChildItem cmdlet with the -Recurse switch: Get-ChildItem -Path V:\Myfolder -Filter CopyForbuild.bat -Recurse -ErrorAction SilentlyContinue -Force

Template: <%* const id = tp.file.creation_date("YYYYMMDDHHmmss"); await tp.file.rename(`${id} ${tp.file.title}`); %>

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.

There are also some advantages to a multi-file YAML format OpenAPI definition: Reuse schema objects to keep things DRY (don't repeat yourself) Smaller diffs compared to JSON (especially for markdown descriptions) Easier to navigate Easier to edit with confidence

Process the log file to determine the spread of data: cat /tmp/sslparams.log | cut -d ' ' -f 2,2 | sort | uniq -c | sort -rn | perl -ane 'printf "%30s %s\n", $F[1], "="x$F[0];'

doesn't know if .env is a hidden file with no extension or a *.env without a filename.

If you do not have an iOS device or a machine running OS X to open your IMOVIEMOBILE file, you can still access its contents. First, copy the IMOVIEMOBILE file, rename the file extension to "zip", decompress the file, and the project content will be in a folder called "Assets." You can then open the original content in a video editing program.

As powerful as search can be, studies5 have found that in manysituations people strongly prefer to navigate their file systemsmanually, scanning for the information they’re looking for. Manualnavigation gives people control over how they navigate, with foldersand file names providing small contextual clues about where to looknext.6

function Zip(_io, _parent, _root) { this._io = _io; this._parent = _parent; this._root = _root || this; this._read(); } Zip.prototype._read = function() { this.sections = []; var i = 0; while (!this._io.isEof()) { this.sections.push(new PkSection(this._io, this, this._root)); i++; } }

What I like best about pdf files is that I can just give them to someone and be almost certain that any questions will be about the content rather than the format of the file.

There are project layouts that put implementation files and test files together.

● Relocatable object file (.o file)○ Code and data that can be combined with other relocatable object files to form executable object file■ Each .o file is produced from exactly one source (.c) file● Executable object file (a.out file)○ Code and data that can be copied directly into memory and then executed● Shared object file (.so file)○ Special type of relocatable object file that can be loaded into memory and linked dynamically, at either load time or run-time

The NFS version 3 protocol is designed to allow servers to be as simple and general as possible. Sometimes the simplicity of the server can be a problem, if the client implements complicated file system semantics. For example, some operating systems allow removal of open files. A process can open a file and, while it is open, remove it from the directory. The file can be read and Callaghan, el al Informational [Page 96] RFC 1813 NFS Version 3 Protocol June 1995 written as long as the process keeps it open, even though the file has no name in the file system. It is impossible for a stateless server to implement these semantics. The client can do some tricks such as renaming the file on remove (to a hidden name), and only physically deleting it on close. The NFS version 3 protocol provides sufficient functionality to implement most file system semantics on a client.

Inside each first-level directory of a MAFF archive, the second-level directory named ^metadata^ (case-sensitive) is reserved and should not contain actual content. A file or folder named ^metadata^ (case-insensitive) should not exist inside any first-level directory.

MAFF files are standard ZIP files containing one or more web pages, images, or other downloadable content. Additional metadata, like the original page address, is saved along with the content.

Modern browsers that support the File System Access API (Edge and Chrome today) allow web pages to access the local file system (with your permission).

The original document file (I think - I can't test it)

mmv1,2 is also a very nice tool for such a task, applied to the current job, it would be mmv '*.md' 'test - #1.md'

Ideally, GitHub would understand rich formats

Source maps eliminate the need to serve these separate files. Instead, a special source map file can be read by the browser to help it understand how to unpack your assets. It "maps" the current, modified asset to its "source" so you can view the source when debugging. This way you can serve assets in development in the exact same way as in production.

When Sprockets was introduced, one of the opinions that it held strongly, is that assets such as CSS and JS should be bundled together and served in one file.

The alternative was to have multiple scripts or stylesheet links on one page, which would trigger multiple HTTP requests. Multiple requests mean multiple connection handshakes for each link “hey, I want some data”, “okay, I have the data”, “alright I heard that you have the data, give it to me” (SYN, ACK, SYNACK). Even once the connection is created there is a feature of TCP called TCP slow start that will throttle the speed of the data being sent at the beginning of a request to a slower speed than the end of the request. All of this means transferring one large request is faster than transferring the same data split up into several smaller requests.

Trailblazer offers you a new, more intuitive file layout in applications.

Instead of grouping by technology, classes and views are structured by concept, and then by technology. A concept can relate to a model, or can be a completely abstract concern such as invoicing.

Yes. That is a drop-in file. I think a leftover from the CentOS docker package. I just removed the file and it started working.

The advantage of the first method is that one easily overrides the complete unit, the default Container Linux unit is not parsed at all anymore.

After command, then we need to first reset the command withAfter= and then add our commands.

Types of Structure Outliners take advantage of what may be the most primitive of relationships, probably the first one you learned as an infant: in. Things can be in or contained by other things; alternatively, things can be superior to other things in a pecking order. Whatever the cognitive mechanics, trees/hierarchies are a preferred way of structuring things. But it is not the only way. Computer users also encounter: links, relationships, attributes, spatial/tabular arrangements, and metaphoric content. Links are what we know from the Web, but they can be so much more. The simplest ones are a sort of ad hoc spaghetti connecting pieces of text to text containers (like Web pages), but we will see many interesting kinds that have names, programs attached, and even work two-way. Relationships are what databases do, most easily imagined as “is-a” statements which are simple types of rules: Ted is a supervisor, supervisors are employees, all employees have employee numbers. Attributes are adjectives or tags that help characterize or locate things. Finder labels and playlists are good examples of these. Spatial/tabular arrangements are obvious: the very existence of the personal computer sprang from the power of the spreadsheet. Metaphors are a complex and powerful technique of inheriting structure from something familiar. The Mac desktop is a good example. Photoshop is another, where all the common tools had a darkroom tool or technique as their predecessor.