I'm working on a way to isolate a data piece behind some kind of secured entrance (requiring a single algorithm out of about forty to be specified in order to access the data lock). Then the user trying to access the data needs to know first hand information about the data such as creation date/time, title of document or type of file (as per user selection) in order to turn the outside but f the lock to let user in behind to access file. Kind of a dual sided data protection security in that even after accessing the files storage location to some degree, the file cannot be made his ble or accessible till you define the file itself to the lock such that the locks acceptance of that data agrees with the data stored behalf be the lock and it opens.

nos.today, smaybe.tommorrow?

open source, music - avail on linux, windows, android and ios? Ya, I don't already see 5 or 6 GREAT reasons to use this, I guess I'll pass...... my mouse over to the download button and start grabbing copies :)

Hi tony... currently working on an information system called HASH-CATS. combining hash-tags with categorical sorting structure like in a newspaper. One one hand, the category or categories are inherent, to meta refine the subject matter. then hash-tags are used to imply keywords or further descriptive data to refine the context of the overall category.

What I'd you did? Do you think it's the kind of thing you're likely to tell me? In the mean time I'll assess your hypothetical conundrum as non definative, determinance that you haven't actually told myself and merely this continue to ignore that plausibility as I already had been.

are you sure they're not actually "real-man-forks" for eating steak like a bear?

what kind of joke is 5x worse than a dad joke and sometimes (often) NOT EVEN FUNNY AT ALL?

- a society joke

what kind of joke is 5x dumber than a dad joke and sometimes ain't even funny at all?

- a society joke

that was one of my favourite twitter hashtags: #iamsatoshi

Is a "one knows" like a zap and when you zap history the future gets dull and stops shocking you?

It occurs toyself that most dual core, core 2 duo, core 2 quad and multicore core i series are probably based on something like pentium pro (with mmx) architecture. This would be fine on a two core and maybe even a four core. By the time eight cores (or more) becomes inherent, the additional instruction sets such as mmx based technology would literally provide hardware bloat in a larger multi core cpu where serial processing is inherent and required. If a 16 core cpu had 16 cores with additional instruction sets that would literally only be required on one of those cores in order to be effective, then an Intel based cpu that had eight or sixteen cores where and if each single core had additional instruction sets for multimedia (especially in consideration of modern GPUs) that this phenomen would be quite explificary as perhaps microhard, the Microsoft of hardware. Bloated system resource hogware.

The important part is the usability. First you can select one or two algos that have to be hash matched to gain access to the lock. Second you can specify various levels of difficulty time, time date, time date year, filename, filename file type, filename time, file name file type time date year, etc.... It can be set as easy as most common Algo with filename only or two algos with time, date, year, filene, fieltype. Since the correct Algo hash let's you access the lock, only then will the correct answer as checksummed against the file yield access to file. Much like a password, you won't learn where you're wrong. Also, attempt allowance could be set at 2 or 4 or 999 and then a duration lockout or even filewipe (depending on security needs)

I was also thinking in addition to timestamp you could also checksum against filename as well as a different and or additional nal security requirement.

Feel free to excuse various obvious typos. I'm not that good a typer without a keyboard.

That is correct. Basically it rides piggy back on the trust-authority of Blockchain verifiability. Further to so said the basic simplicity of the time stamp provides robust deyeination of a requirement of knowledge of said file (or dorectory) itself in order to concede access to 'that' ( particular) file. I am in no way denying the logistically required effort (predominant to complexity of a. Manifesting such a security and b. Making sure you don't accidently, tautologically lock yourself out of your own data. I'm basically working on a VERY slim Blockchain mobile OS predominantly deogned for travel, journalism and other facets requiring not a large particular amount of operation (such as gaming), but a high amount of very precise and virtually unbrechable data access protection.

Yes, this idea would remain a separate function from cryptography overall (i.e. encrypted data). This would probid a. That a user selects an Algo out of maybe 14 or 15. That Algo then becomes a 'key' Algo. That Algo would have to be matched with a chechsum which would likely be a previous hash in a block somewhere upon that chain of a coont or token of that particular Algo. Each file would effectively be access protected and either encrypted or unencrypted (by separate process). In order to access 'that file' (or directory), the access clearance would have to match checksum with a hash of the previously selected Algo which would be formularically requirant inclusive of a timestamp already provided on that 'lock' (so to speak). Using bots or whatnot wouldn't acheive alot of success because not only does the key Algo have to be the correct Algo, but also, the match checksum has to include verification of the correct timestamp (with some element of temporal order ie. Time of day, day of month, month of year and year possibly). User would be able to specify from file lock as per file or directory as well as a specific scrutiny (i.e. how much accuracy specific to provided time stamp is required. The lock would simply exist 'upon' that file in such a way that access to any element of alteration of that file (read, write and/or move) could not become implemented without first providing a correct checksum from a previous hash on the key Algo (as well as matching the time stamp of that file).

I'm thinking something along the lines of performing an Algo hash check prior to being able to even attempt to access data. If that were mixed with a time stamp upon which the data was either created or stored, the knowledge of that time stamp wouldn't be accessible other than by correct hash comparability with the actual time stamp and selected Algo hash checksum relative to the actual time stamp determinant on the (then present) as of yet unaccessible data store(s).

It might be more prudent to refer to that as "a single entity" or "a single account" ( or user token). There might be a conglomeration of many or multiple individuals which act or work together under a single registration. It's not that it couldn't be "one person" but it's not that it would have to be.

I think we should take bobs festivals that are in our way and tern them into britches so that all may cross bobs testicles with our newly built britches of crossing for ease of crossability.

Is there any such that ng as a blockchain mobile OS? Could erc-20/dapps be used to construct a privacy sensitive mobile operating system?