86 Matching Annotations
  1. Last 7 days
    1. 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
  2. Aug 2022
    1. 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];'
  3. Jul 2022
    1. 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.

      It's not rational, but I'd like to note how angy I am with myself in retrospect for not looking this up before. I have literally given up on old project files because I assumed the video was unretrievable and then... I just did this on my iPad in a matter of seconds lol.

  4. Jun 2022
    1. 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

      The studies quoted here are in the mid 80s and early 90s before the rise of better and easier UI methods or more powerful search. I'd have to call this conclusion into question.

      There's also a big difference in what people know, what people prefer, and what knowledgeable people can do most quickly.

      Cross reference this with Dan Russell's research at Google that indicates that very few people know how to use ctrl-f to find or search for things in documents. - https://hyp.is/7a532uxjEeyYfTOctQHvTw/www.youtube.com/channel/UCh6KFtW4a4Ozr81GI1cxaBQ

      Relate it to the idea of associative (memory) trails (Memex), songlines, and method of loci in remembering where things are -- our brains are designed to navigate using memory

  5. Apr 2022
    1. 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++; } }

      Although the generated code is very useful...

      This is wrong. It treats the ZIP format as if (à la PNG) it's a concatenated series of records/chunks marked by ZIP's characteristic, "PK" off-set, 4-byte magic numbers. It isn't. The only way to read a ZIP bytestream is to start from the end, look for the signature that denotes the possibility of the presence at the current byte offset the record containing the central directory metadata, proceeding to validate* the file based on that, and then operating on it appropriately. (* If validation fails, you can continue scanning backwards from the offset that was thought to be the signature.)

      The first passed validation attempt carried out in this manner (from back to front) "wins"—there may be more than one validation passes beginning at various offsets that succeed, but only the one that appears nearest to the end of the bytestream is authoritative. If one or more validation attempts fail resulting in no successes, the file may be corrupt, and the implementation may attempt to "repair" it (not necessarily by making on-disk modifications, but merely by being generous with its interpretation of the bytestream—perhaps presenting several different options to the user), or, alternatively, it may be the case that the file is simply not a ZIP archive.

      This is because a ZIP file is permitted to have its records be little embedded "data islands" (in a sea of unrelated bytes). This is what allows spanned/multi-disk archives and for the ZIP to be modified by updating the bytestream in an append-only way (or selectively rubbing out parts of the existing central directory and updating the pointers/offsets in-place). It's also what allows self-extracting archives to be self-extracting: foremost, they conform to the binary executable format and include code for being able to open the very same executable, process the records embedded within it, and write them to disk.



    1. 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.

      Almost every time I've used FedEx's "Print and Go" for a PDF I've created by "printing" e.g. HTML (and that I've verified looks good when previewing it on-screen), it comes out mangled when actually printed to paper.

  6. Mar 2022
    1. ● 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

      compile 之后的 object files 有哪几种类型?

  7. Dec 2021
  8. datatracker.ietf.org datatracker.ietf.org
    1. 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.
  9. Nov 2021
    1. 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.
    1. 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.
    1. 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).
  10. Oct 2021
    1. Postmodernist Theory. This theory was focus on associated with relativism on ideology in the maintenance of economic and political power. It also generally explain which is claim to be valid for all groups, cultures, traditions, or races.


  11. Sep 2021
    1. Fundamentos pedagógicos. En el PEI de la institución pudimos identificar las tendencias pedagógicas del colegio universitario de socorro como lo son: el aprendizaje significativo- humanista y constructivista, al igual orientan contenidos al estudio del medio ambiente.

  12. Jul 2021
    1. The original document file (I think - I can't test it)

      Referenced in an HN thread:


      In the thread, William Woodruff mentions that LibreOffice is capable of displaying this file.

  13. Jun 2021
  14. Apr 2021
    1. Ideally, GitHub would understand rich formats

      I've advocated for a different approach.

      Most of these "rich formats" are, let's just be honest, Microsoft Office file formats that people aren't willing to give up. But these aren't binary formats through-and-through; the OOXML formats are ZIP archives (following Microsoft's "Open Packaging Conventions") that when extracted are still almost entirely simple "files containing lines of text".

      So rather than committing your "final-draft.docx", "for-print.oxps" and what-have-you to the repo, run them through a ZIP extractor then commit that to the repo. Then, just like any other source code repo, include a "build script" for these—which just zips them back up and gives them the appropriate file extension.

      (I have found through experimentation that some of these packages do include some binary files (which I can't recall offhand), but they tend to be small, and you can always come up with a text-based serialization for them, and then rework your build script so it's able to go from that serialization format to the correct binary before zipping everything up.)

  15. Feb 2021
    1. 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.
    1. 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.
    2. 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.
  16. Jan 2021
  17. Dec 2020
    1. 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.

      Structuring Information

      Ted Goranson holds that there are only a couple of ways to structure information.

      In — Possibly the most primitive of relationships. Things can be in other things and things can be superior to other things.

      Links —Links are what we know from the web, but these types of links or only one implementation. There are others, like bi-directional linking.

      Relationships — This is what we typically use databases for and is most easily conceived as "is-a" statements.

      Attributes — Adjectives or tags that help characterize or locate things.

      Metaphors — A technique for inheriting structure from something familiar.

  18. Nov 2020
  19. Oct 2020
  20. Sep 2020
    1. I think your error is because you don't have .mjs in your webpack's resolve.extensions. The file singled out by the error message ./internal is actually a .mjs file, but you only have .svelte extensions...
    1. It’s become increasingly common to divide code into components, rather than by file type. React, for example, allows for the collocation of a components markup and JavaScript. In Svelte, this is taken one logical step further: the Javascript, markup and styling for a component can all exist together in a single `.svelte`​ file
  21. May 2020
  22. Apr 2020
    1. They are proof that our openness about our data formats means that you do not have to fear data lock-in.
    2. So while we can’t endorse those systems, and indeed we have to advise you against using them; their existence is still a Good Thing
    3. It’s this third way that we avoid lock-in that is relevant to today’s topic. Our data format design is specified well enough so that people with no connection to AgileBits can write software to be able to handle it.
    4. The second way we avoid locking you into 1Password is through the ability to export data to a more neutral format. Not all versions are yet where we want them to be with respect to export, and we’re working on that. But there is usually some path, if not always a simple click away, to export your 1Password data.
    1. Although we don’t anticipate publishing source code for manipulating 1Password keychains, others, unaffiliated with AgileBits, have done so.

      May not technically be an open file format, but meets some of the criteria for one:

      • [?] The format is based on an underlying open standard
      • [⍻] The format is developed through a publicly visible, community driven process
      • [⍻] The format is affirmed and maintained by a vendor-independent standards organization
      • [✓] The format is fully documented and publicly available
    1. OPVault is an almost perfectly documented format. This makes it highly improbable to come across a file that will fail to be imported. If it ever happens, a bug in the plugin is probably to be blamed.
    1. 1Password wasn’t built in a vacuum. It was developed on top of open standards that anyone with the right skills can investigate, implement, and improve. Open tools are trusted, proven, and constantly getting better. Here’s how 1Password respects the principles behind the open tools on which it relies:

      I found it ironic that this proprietary software that I have avoided using because it is proprietary software is touting the importance of open tools.

  23. Mar 2020
  24. Jan 2020
  25. Dec 2019
    1. You're not going to find many checkboxes, drop-downs, reminders, or date pickers here.

      Thankfully, some clients like https://github.com/QTodoTxt/QTodoTxt2 do have nice features like autocomplete, and date pickers.

    2. Countless productivity apps and sites store your tasks in their own proprietary database and file format. But you can work with your todo.txt file in every text editor ever made, regardless of operating system or vendor.
  26. burnsoftware.wordpress.com burnsoftware.wordpress.com
    1. Future proofs your journal entries by saving them as plain text and organizing them as you go. This means you can read or create entries when you don’t have DayJournal.
    1. Plain text is software and operating system agnostic. It's searchable, portable, lightweight, and easily manipulated. It's unstructured. It works when someone else's web server is down or your Outlook .PST file is corrupt. There's no exporting and importing, no databases or tags or flags or stars or prioritizing or insert company name here-induced rules on what you can and can't do with it.
  27. Nov 2019
    1. File-relative configuration Babel loads .babelrc (and .babelrc.js / .babelrc.cjs / package.json#babel) files by searching up the directory structure starting from the "filename" being compiled (limited by the caveats below). This can be powerful because it allows you to create independent configurations for subsections of a package. File-relative configurations are also merged over top of project-wide config values, making them potentially useful for specific overrides, though that can also be accomplished through "overrides".
  28. Oct 2019
  29. Jun 2019
  30. May 2019
    1. "list" (0x6C696E74)

      The hex spells lint not list, also in a real WAV file it appears to be capitalized LIST = 0x4C495354

  31. Apr 2019
  32. Mar 2019
    1. error BadZipfile: File is not a zip file

      在安装albacore的时候,使用pip install命令安装.whl文件的时候,总是会出现“ BadZipfile:File is not a zip file”的错误,通过使用参数--no-cache-dir可以解决这个问题。

  33. Mar 2018
    1. It would be fair to characterize Beaker as “a novel application of Bittorrent’s concepts to the Web platform.” If Beaker had been started in 2006, it would be using Bittorrent as its primary protocol. However, as of 2016, new variants have appeared with better properties.
  34. Nov 2017
  35. Oct 2017
    1. What is this again? What Google Drive should be. What Dropbox should be. What file systems can be. The way we unify our data access across companies, services, programs, and people. The way I want to live and work.

      I think that this is interesting, but idealistic. The code repo on GitHub is quite active, but how does a technology like this gain traction?

  36. Jun 2017
  37. Dec 2015
  38. Aug 2015
    1. “The cat is out of the bag. The content people have no clue. I mean, no clue.” - Bram Cohen