11–20 of 37 posts
"We're sorry but web doesn't work properly without JavaScript enabled. Please enable it to continue." This appears to be a static content site after I enabled JS. Why can't the site display static content without JS?
> App added an icon to my menu bar and has no clickable menu to close it.
> The app opens up asking for a Blockstack login... no mention of this on the website. I have one but are typically people supposed to sign up for something seemingly unrelated?
> The 'x' button on the app minimizes it instead of closes it.
> The only way I figured out how to actually close it was by killing the process from the command line.
Why blockchain? Because there's one FAQ that you're obviously missing: "How do I delete a compromised/accidentally-uploaded file?" and I suspect it's because the answer is "You can't." This would be the last place I'd upload anything important. Once that URL/password get out, whatever "secure" file I've uploaded is exposed forever.
You can have your own private web-based file transfer server in maybe around 100 lines of PHP where you have total control over file expiry and no need to trust any third parties except perhaps your VPS provider. If you need more secure than that, courier an encrypted thumb drive or something.
I can't tell if this is a reference to the infamous Dropbox reply or not.
What blockchain does it run on? How is it free? Who's paying the blockchain transaction fees?
"We're sorry but web doesn't work properly without JavaScript enabled. Please enable it to continue." This appears to be a static content site after I enabled JS. Why can't the site display static content without JS?
Because it's done in a JS framework without server side rendering.
Earlier quoted context omitted.
I can't tell if this is a reference to the infamous Dropbox reply or not.
What is the infamous Dropbox reply? Are you talking about the Steve Jobs thing?
Why blockchain? Because there's one FAQ that you're obviously missing: "How do I delete a compromised/accidentally-uploaded file?" and I suspect it's because the answer is "You can't." This would be the last place I'd upload anything important. Once that URL/password get out, whatever "secure" file I've uploaded is exposed forever.
I'd say the primary use case is data which you want to keep public forever. Such as your legacy before you pass away (it is pay once, host forever, right?). Such as an encrypted insurance file for Mr. Assange. I can also imagine this would be interesting for copyright infringement (eventually with spliced files; e.g. with RAR .rar .r01 r02 etc), or for an activism, or whistle-blower. I suppose though that once that '…
Earlier quoted context omitted.
"server side rendering", cool, I was doing that in 1995
What is a better alternative to server side rendering?