taravancil/paste-dat

A tool for sharing files with Dat in the Beaker browser

paste-dat's Issues

Remove archive.commit() depreciated method?

There is a console warning:
The DatArchive commit() API has been deprecated. as indeed it is listed as depreciated method here dat://beakerbrowser.com/docs/apis/dat#commit
Although it is not clear to me what this method did. When I removed this line:

paste-dat/index.js

Line 43 in 49ca096

await archive.commit()

All seemed to work fine.

Preserve whitespace!

Use feature detection instead of user agent sniffing.

Right now paste-dat checks if it should support saving by looking for the string "BeakerBrowser" in the user agent string. I propose instead checking if "DatArchive" exists in the window context. I know that right now the DatArchive API is only supported by Beaker Browser, but I believe it is better not to user user agents to infer anything, ever.

An example which is forked from the original page can be found here: https://parsedat-peacememories.hashbase.io/
Only the check is changed, not the resulting message, and it's done in the "binary" js.

Display warnings when not in Beaker - won't work in traditional browsers

Double check tabindex for file forms

Markdown rendering in the preview page

Open questions:

• Should the user be able to toggle between formatted and rendered? Beaker already does this for markdown files, so maybe not?

Only render preview if user hasn't added an index.html

Should we even write files?

PasteDat doesn't really function like pastebin/gist if when, for example, you add a .html file, every time you visit that file, it's actually rendered as HTML. How do you ever get the raw file? We should probably just write one file in the archive (the preview page), which renders all of the file contents.

Show share prompt on preview page if user is the archive owner

.hidden class is not taken off of the markdown preview

This makes the preview unscrollable

Use same monospace font for code in markdown formatted code as rest of page

Should consider doing this for the default markdown formatting in Beaker as well.

Create a preview page for the archive

Handle errors for filenames like `../test.txt` and `dir/test.txt`

Only import markdown renderer if it's actually going to be used

Show list of previous versions on preview page