Re: [OT] unhosing .rev and .livecode files

2016-12-03 Thread Jerry Jensen
Just one additional level of warning - if you keep Dropbox or Google Drive online, malware can get there too. Usually the baddies just trash your directory, but if they encrypt everything you have accessible online, Dropbox and Google Drive won’t help you. Offline backup is essential, offsite is

Re: live code seems to gratuitously unlock write permission for directories

2016-12-03 Thread Stephen Barncard
This has been standard practice for shared hosting at Dreamhost for years. I made an index.irev file that looked at the contents of the directory and displayed a list, subject to filtering. Parameters set with simple txt file. Very easy. sqb -- Stephen Barncard - Sebastopol Ca. USA - mixstream.or

Re: [OT] unhosing .rev and .livecode files

2016-12-03 Thread Kay C Lan
Hi Richmond, Glad to hear that you've been able to rescue most of your files. The Data Rescue programme I use is imaginatively called 'Data Rescue' by Prosoft. I don't think it would help in your case as I don't think the Mac version can recover non-Mac HDs. The reason I mention it is that it has

Re: Non-Public API Usage

2016-12-03 Thread pink
I have not used those names, so I submitted it: http://quality.livecode.com/show_bug.cgi?id=18958 -- View this message in context: http://runtime-revolution.278305.n4.nabble.com/Non-Public-API-Usage-tp4710840p4710842.html Sent from the Revolution - User mailing list archive at Nabble.com. ___

Re: Non-Public API Usage

2016-12-03 Thread Mark Schonewille
Hi Pink, If you are using the names _getcontext, _makecontext and _setcontext for your handlers in your scripts, just change the names and make sure they are nowhere mentioned in your app. If you didn't use these handler names, report it as a bug to the QCC. Kind regards, Mark Schonewille h

Non-Public API Usage

2016-12-03 Thread pink
I compiled and submitted an app using iTunes Connect. I received the following rejection message. I compiled using Livecode 8.1.2 rc2, I have Xcode 8.1 installed. I tried recompiling a few times and got the same results each time. How do I fix this? Dear developer, We have discovered one or mor

Re: live code seems to gratuitously unlock write permission for directories

2016-12-03 Thread Mike Bonner
Most likely directory browsing is turned off. You could change the setting, or you could put in an irev that gets "the files" and builds a link list dynamically, minus itself of course. On Sat, Dec 3, 2016 at 3:54 PM, Alex Tweedly wrote: > You're right - and I confess I don't know why the downl

Re: live code seems to gratuitously unlock write permission for directories

2016-12-03 Thread Alex Tweedly
You're right - and I confess I don't know why the downloads folder is inaccessible. Permission is set to 755, and there's no .htaccess file or anything else I know of to prevent it. Anyway - if you wanted the taskrunner files, they are : - taskrunner.rev - taskClientLib.rev - test-task-runne

Re: live code seems to gratuitously unlock write permission for directories

2016-12-03 Thread Alex Tweedly
Very strange - the correct URL is http://tweedly.org/downloads/checkpermissionsetting.livecode i.e. without the last 's' Did you know that, in Chrome, if you modify the URL, and it turns out to be a downloadable file - then Chrome downloads it, and then changes the visible URL in the address

live code seems to gratuitously unlock write permission for directories

2016-12-03 Thread Alejandro Tejada
Hi Alex, Downloads folder in your server is not accessible. It's not possible to download this stack either: http://tweedly.org/showpage.lc?page=taskRunner Al ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscri

Re: live code seems to gratuitously unlock write permission for directories

2016-12-03 Thread Dr. Hawkins
On Sat, Dec 3, 2016 at 9:47 AM, Alex Tweedly wrote: > It's at http://tweedly.org/downloads/checkpermissionsettings.livecode > Not Found The requested URL /downloads/checkpermissionsettings.livecode was not found on this server. Additionally, a 404 Not Found error was encountered while trying

Re: [OT] unhosing .rev and .livecode files

2016-12-03 Thread Richmond Mathewson
That sounds great, but I wonder exactly how I should look for the file headers. Richmond. On 12/3/16 7:42 pm, Stephen Barncard wrote: On Sat, Dec 3, 2016 at 7:58 AM, Richmond Mathewson < richmondmathew...@gmail.com> wrote: files, and NOT .rev and .livecode files I wonder if anyone has any br

Re: live code seems to gratuitously unlock write permission for directories

2016-12-03 Thread Alex Tweedly
OK, I got slightly lost in this thread - we've gone off to solve a work-around to your problem, and I'd like to go back to the problem itself. If I understood it properly, what you;re seeing is that setting the permission of a directory to disallow write *should* prevent you from saving a sta

Re: [OT] unhosing .rev and .livecode files

2016-12-03 Thread Stephen Barncard
On Sat, Dec 3, 2016 at 9:42 AM, Stephen Barncard wrote: > Look for the file header text at the beginning of every stack: > > like > REVO7000 > REVO5500 > There should also be a file termination character(s) -- Stephen Barncard - Sebastopol Ca. USA - mixstream.org ___

Re: [OT] unhosing .rev and .livecode files

2016-12-03 Thread Stephen Barncard
On Sat, Dec 3, 2016 at 7:58 AM, Richmond Mathewson < richmondmathew...@gmail.com> wrote: > files, and NOT .rev and .livecode files I wonder if anyone has any bright > suggestions how one might > go about looking for them. > Look for the file header text at the beginning of every stack: like REVO

[OT] unhosing .rev and .livecode files

2016-12-03 Thread Richmond Mathewson
Aa all forensic software for digging in blanked hard drives seems to find the most obvious files, and NOT .rev and .livecode files I wonder if anyone has any bright suggestions how one might go about looking for them. Richmond. ___ use-livecode maili