Quote from: 82ndabnmedic on September 09, 2018, 02:50:21 PM

Quote from: dbkeys on September 09, 2018, 02:20:43 PM

Quote from: maser82 on September 09, 2018, 11:50:24 AM

Quote from: 82ndabnmedic on September 09, 2018, 03:23:11 AM

Quote from: dbkeys on September 08, 2018, 04:57:31 PM

Quote from: maser82 on September 08, 2018, 04:12:29 PM

Quote from: dbkeys on September 08, 2018, 12:05:24 PM

Quote from: cubonho2k on September 08, 2018, 04:09:17 AM

Is this a new project? What are your key features compared to other wallets that may appeal to users? Your wallet is a new version so I think it needs to be improved, and you already have the person in charge of this part yet? You should improve the wallet so that users can use the best way

The Bitmark project was started in July of 2014.

The key feature of our Blockchain is our focus on Marking.

Marking is a broad term that encompasses many different uses and applications, most involving anchoring data sets on the blockchain via hashes embedded in transactions. It's a deep, fascinating topic that we can expand on to many useful areas.

We welcome your suggestions on how to improve our wallet and any others you may have too.

Having the marking feature in the wallet would be nice. Like offering the option to select a file to be marked before you do a transaction and then, when it do the transaction, it hashes the file and stores the file hash into the blockchain.

If there were an option to set file name, file description and an optional storage of the file in the bitmark servers, allowing to publicty query the file, that would be very useful to many companies and entities.

I like your suggestion !

That would be a great and simple way to enable users to mark anything they had on file.

The optional storage part is interesting too because it would in essence be the storing of the file which originated in the user's machine to the Bitmark servers, or "Bitmark Storage Cloud" which could be a federation of machines which are willing to commit storage space for a length of time in exchange for MARKS.

Agreed, that would be a good way to implement Marking and leverage our "Bitmark Storage" solutions. Thanks for the recommendation! We will see if this is a feature the community would like/support, and if it is we can add it to our short term milestones list (after the completion of the code base upgrades).

May be it could be a new tab intended explusively for marking, showing the available fields to fill, and when the user commits the action then it automatically do the transaction, marks the file and upload it to the bitmark storage.

A webpage having a "marked files explorer" that allows anyone to search and to check the marked files, additional data, timestamp and hashes would be very useful.

The main problem I can think on this is what happens when someone marks illegal content and it is stored on the bitmark servers or bitmark storage. There should be a way to report illegal content and a way to delete it.

The question of legality is always tied to jurisdiction. It's an interesting question, because what is legal in one place might not be legal in another. There should be a way to report questionable content, and for contributors to the storage federation to decide whether they want to keep it or not.

Those are good points.

We could look into the Firewall offerings (through the web server/services provider)

It is easy to block certain types of traffic, however files (with illegal content) gets a bit trickier.

https://www.paloaltonetworks.com/documentation/71/pan-os/pan-os/policy/create-best-practice-security-profiles

https://live.paloaltonetworks.com/t5/Management-Articles/Complete-List-of-PAN-DB-URL-Filtering-Categories/ta-p/129799

Not sure if google offers an API for this. That said it would be prudent to take a similar approach as services like reddit. Relying on the community is much more feasible, since we don't have the resources/assets for this at the moment.

The distributed storage idea and to get paid in Bitmarks for hosting the marked content is pretty attractive. It is a groundbreaking idea, like what Dash did with the masternodes, but it is pretty risky too. With no content control, Bitmark could become a network to share child pornography or something scary as that. Allowing the content to be controlled by a public community could not always avoid legal problems: In an hipotetical case where someone marks a leaked hollywood movie or some content DMCA protected, publishing it without authoritzation, then maybe the users in the comunity would like to keep accessing to the content because they like it but that would be illegal in the USA where many lawyers would take action.

From my point of view, the best way would be to keep it simple: Store the content in one server, in one legislation and managed by one entity. In one hand it would imply resources in terms of hardware and support but in the other hand that would make all the marking storage easy to acomplish with laws. The fees for marking could be higher than a normal transaction and destined to pay the server storage and support. By support I mean what could be review the content complaints and content removals.

A Bitmark association or fundation backing all the process would be nice and would provide confidence to the users.