Thinking about Wikidrive 20220327

from Wikidrive

• Considering the specifications of Wikidrive

  • Each file in the top-level hierarchy of Google Drive will be displayed as a page in Scrapbox.
    • Assuming that all files are placed in the top-level hierarchy.
    • Conversely, even if there are folders, they will be treated as files.
      • With this specification, it is possible to manage hierarchies if desired.
      • The format within the page is similar to Scrapbox’s bullet-point hierarchy.
    • If the name of a file changes or it is deleted, the name of the corresponding Scrapbox page will also change.
  • It is possible to write and link in Scrapbox pages.
    • This becomes a “literary file system”.
  • During search
    • I want to use both the search of the Scrapbox pages and the full-text search of Google Drive.
    • Maybe I can create a search site that integrates them.
    • I’m curious about how /ScrapboxSpace is doing it (blu3mo).
    • It can be done in the same way as the /takker/ScrapboxからGyazoのOCR結果を検索するUserScript and its original version.
      • ↑ This and its original version are smart (blu3mo)(blu3mo).
      • Display the relevant files obtained through full-text search in Google Drive on Scrapbox.

• Concerns

  • I’m afraid of creating a security hole due to my own stupidity.
    • If I introduce it to trusted people, they will eventually find it, right?
  • What if file names overlap?
    • It’s not possible to have duplicates in Drive before Scrapbox, so I guess that’s fine.
    • Well, I can just avoid that normally.

• Impressive features (expected)

  • The ability to link a writing-intensive wiki with a file system.
    • Like a file version of Literary Programming, similar to literary file system.
  • The hybrid nature of hierarchy and non-hierarchy, where if there are folders in the top-level hierarchy, they are treated as a single page.
  • Both of these points are amazing, right? (blu3mo)(blu3mo)(blu3mo)
    • I’m getting excited.
    • The high tension that comes with coming up with ideas.

• What problems does it solve?

  • It eliminates the hassle of file management.

    • When managing hierarchies, files can appear in multiple locations.
      • That can be problematic.
      • It has already been mentioned in /IFPsychology/階層型ファイルシステムの憂鬱.
    • When searching
      • In a hierarchical system, you have to dig through layers to find a file.
        • If you know the “file you want to find,” it is faster to search for it with increased visibility in the wiki.
        • Maybe there are cases where a hierarchical system is better if you want to find something unknown.
          • If There is a Framework, You Can Recognize the Blank Space Enclosed by the Framework
          • But I guess it’s not really necessary.

  • Situations

  • Well, while keeping challenges and such in mind, I want to create a prototype driven by the interesting concept (blu3mo).

• What will the implementation be like?

  • It depends on how well the Google Drive API is developed.
  • What can be done?
    • Drive API
      • Writing operations
    • Drive Activity API

      • The Google Drive Activity API lets your app retrieve information about a user’s Google Drive activity. This provides additional functionality on top the existing Drive API for your app to do things like:

        • Display activity on a user’s files.

        • Track changes to specific files or folders.

        • Oh, this can be used to

        • Alert a user to new comments or changes to files.

  • In short, the flow of information is one-way from GDrive to Scrapbox.
    • Simple and good.