elective-stereophonic
elective-stereophonic
NRS v1.7.3e
Please login or register.

Login with username, password and session length
Advanced search  

News:

Latest Stable Nxt Client: Nxt 1.12.2

Pages: 1 2 [3]  All

Author Topic: NRS v1.7.3e  (Read 24861 times)

coretechs

  • Sr. Member
  • ****
  • Karma: +161/-1
  • Offline Offline
  • Posts: 436
    • View Profile
Re: NRS v1.7.3e
« Reply #40 on: December 25, 2015, 05:29:29 am »

Yeah, but drugs can be tolerated by many. What possibly won't be tolerated is, uhm, so called sexual content involving infants. Images are posted directly to the blockchain and then distributed among all participants so every NXT user would store such content in a completely plain unencrypted form. I'm curious how these things will be settled legally.

What you describe has unfortunately already occurred in the Bitcoin blockchain.  There is a huge thread on bitcointalk somewhere but I'm not about to go searching for those terms.  Other types of information appear too, some controversial, some not - http://www.righto.com/2014/02/ascii-bernanke-wikileaks-photographs.html

That is the nature of public blockchains and censorship resistant technology.  It shifts the burden of filtering content to the client, which is arguably no different than the internet itself.
Logged
https://ardorportal.org - Ardor blockchain explorer | https://nxtportal.org - Nxt blockchain explorer | http://bitcoindoc.com - The Rise and Rise of Bitcoin
ARDOR-T43P-R2K9-8W79-9W2AL | NXT-WY9K-ZMTT-QQTT-3NBL7

rkfg

  • Jr. Member
  • **
  • Karma: +1/-0
  • Offline Offline
  • Posts: 33
    • View Profile
Re: NRS v1.7.3e
« Reply #41 on: December 25, 2015, 07:38:27 am »

That's true, I'm aware of that incident. The difference is in the ease of use. Do you know how to extract that data from the Bitcoin blockchain? I can't do it right off the bat, heck, I don't even know whether it's possible using the RPC API or if it requires some database hacking. On the opposite, NXT provides the uploaded images in two clicks. You don't have to know anything, you just open the Data Cloud tab and see that there. You don't even need to search explicitly, you have all the files available immediately and can download and view them with little to no effort. That's what I'm talking about.
Logged

crimi

  • Hero Member
  • *****
  • Karma: +122/-11
  • Offline Offline
  • Posts: 863
    • View Profile
Re: NRS v1.7.3e
« Reply #42 on: December 25, 2015, 02:28:30 pm »

API getState gives false info for example.

Quote
"services": [
        "HALLMARK",
        "PRUNABLE",
        "API",
        "API_SSL"
]

Both enabled API and API_SSL doesnt seem right. Server has no service API_SSL active.
Logged

Brangdon

  • Hero Member
  • *****
  • Karma: +229/-25
  • Offline Offline
  • Posts: 1389
  • Quality is addictive.
    • View Profile
Re: NRS v1.7.3e
« Reply #43 on: December 27, 2015, 11:59:24 am »

That's true, I'm aware of that incident. The difference is in the ease of use. Do you know how to extract that data from the Bitcoin blockchain? I can't do it right off the bat, heck, I don't even know whether it's possible using the RPC API or if it requires some database hacking. On the opposite, NXT provides the uploaded images in two clicks. You don't have to know anything, you just open the Data Cloud tab and see that there. You don't even need to search explicitly, you have all the files available immediately and can download and view them with little to no effort. That's what I'm talking about.
I share your concern. Any suggestions what to do about it?

We could do what we did for the market place and add a warning and an extra click to enable it. Having a line in nxt.properties that could disable decoding images and videos entirely, so it can't be re-enabled from the UI, might be good too.

That said, I'm not convinced that ease of use will carry much weight in court. Simply running an archival node would probably count as distributing child porn. I'm based in the UK, where possession is an absolute offence that carries a jail sentence. If/when it happens I'll probably just shut down my node for a few weeks and then make it non-archival when it starts up again. If it happens too often I'll stop running a node entirely.
Logged

Sebastien256

  • Hero Member
  • *****
  • Karma: +169/-24
  • Offline Offline
  • Posts: 2823
  • ^LOOK UP^ = Nxt community!
    • View Profile
Re: NRS v1.7.3e
« Reply #44 on: December 27, 2015, 05:26:32 pm »

That's true, I'm aware of that incident. The difference is in the ease of use. Do you know how to extract that data from the Bitcoin blockchain? I can't do it right off the bat, heck, I don't even know whether it's possible using the RPC API or if it requires some database hacking. On the opposite, NXT provides the uploaded images in two clicks. You don't have to know anything, you just open the Data Cloud tab and see that there. You don't even need to search explicitly, you have all the files available immediately and can download and view them with little to no effort. That's what I'm talking about.
I share your concern. Any suggestions what to do about it?

We could do what we did for the market place and add a warning and an extra click to en able it. Having a line in nxt.properties that could disable decoding images and videos entirely, so it can't be re-enabled from the UI, might be good too.

That said, I'm not convinced that ease of use will carry much weight in court. Simply running an archival node would probably count as distributing child porn. I'm based in the UK, where possession is an absolute offence that carries a jail sentence. If/when it happens I'll probably just shut down my node for a few weeks and then make it non-archival when it starts up again. If it happens too often I'll stop running a node entirely.

Archival node of not, it does not make a real difference because normal node will still hold the "sensitive" data for a certain time period (90 days by default).

I agree that a few agreement click as for the marketplace would be good.
Logged
Please drop your ideas concerning Nxt and/or NRS in this topic -> List of feature request for Nxt and/or NRS (with the full list in OP).

blackyblack1

  • Hero Member
  • *****
  • Karma: +165/-82
  • Offline Offline
  • Posts: 1764
    • View Profile
Re: NRS v1.7.3e
« Reply #45 on: December 27, 2015, 07:45:10 pm »

Bug report: OPEN API service not running when using IPv6 bind address.

Example:

Code: [Select]
nxt.allowedBotHosts=*
nxt.apiServerHost=0.0.0.0
nxt.apiServerCORS=true

API service is active.

Code: [Select]
nxt.allowedBotHosts=*
nxt.apiServerHost=[::]
nxt.apiServerCORS=true

API service is not active.

Code: [Select]
nxt.allowedBotHosts=*
nxt.apiServerHost=[::1]
nxt.apiServerCORS=true

API service is not active.
Logged

Jean-Luc

  • Core Dev
  • Hero Member
  • *****
  • Karma: +816/-81
  • Offline Offline
  • Posts: 1610
    • View Profile
Re: NRS v1.7.3e
« Reply #46 on: December 27, 2015, 09:09:46 pm »

If you set nxt.apiServerHost=0.0.0.0 it will listen on all interfaces, including IPv6. Is there a reason not to use 0.0.0.0? The jetty documentation for setHost, which is where this parameter is used, says if it is 0.0.0.0 or null, it binds to all interfaces, doesn't mention how [::] is treated.
http://download.eclipse.org/jetty/9.3.6.v20151106/apidocs/org/eclipse/jetty/server/AbstractNetworkConnector.html#setHost-java.lang.String-
Logged
GPG key fingerprint: 263A 9EB0 29CF C77A 3D06  FD13 811D 6940 E1E4 240C
NXT-X4LF-9A4G-WN9Z-2R322

blackyblack1

  • Hero Member
  • *****
  • Karma: +165/-82
  • Offline Offline
  • Posts: 1764
    • View Profile
Re: NRS v1.7.3e
« Reply #47 on: December 27, 2015, 09:28:57 pm »

If you set nxt.apiServerHost=0.0.0.0 it will listen on all interfaces, including IPv6. Is there a reason not to use 0.0.0.0? The jetty documentation for setHost, which is where this parameter is used, says if it is 0.0.0.0 or null, it binds to all interfaces, doesn't mention how [::] is treated.
http://download.eclipse.org/jetty/9.3.6.v20151106/apidocs/org/eclipse/jetty/server/AbstractNetworkConnector.html#setHost-java.lang.String-
The author of original bug report told me he is trying to setup a node for Hyperboria. Maybe there is a reason to bind on [::] address.
Logged

qq2536007339

  • Hero Member
  • *****
  • Karma: +42/-9
  • Offline Offline
  • Posts: 514
    • View Profile
Re: NRS v1.7.3e
« Reply #48 on: December 28, 2015, 03:47:26 am »

What's the meaning of HK,PE,AI,AL in Services column at Peers page? Can someone explain to me? Thanks in advance.
Logged
你送我阿朵,我是要的。ARDOR-DJ68-PG7W-4JEU-2LU5T

blackyblack1

  • Hero Member
  • *****
  • Karma: +165/-82
  • Offline Offline
  • Posts: 1764
    • View Profile
Re: NRS v1.7.3e
« Reply #49 on: December 28, 2015, 06:00:01 am »

If you set nxt.apiServerHost=0.0.0.0 it will listen on all interfaces, including IPv6. Is there a reason not to use 0.0.0.0? The jetty documentation for setHost, which is where this parameter is used, says if it is 0.0.0.0 or null, it binds to all interfaces, doesn't mention how [::] is treated.
http://download.eclipse.org/jetty/9.3.6.v20151106/apidocs/org/eclipse/jetty/server/AbstractNetworkConnector.html#setHost-java.lang.String-
Looks like 0.0.0.0 option works for him. Is it possible to include some additional info (that IPv6 networks are supported) in the parameter description ?
Logged

blackyblack1

  • Hero Member
  • *****
  • Karma: +165/-82
  • Offline Offline
  • Posts: 1764
    • View Profile
Re: NRS v1.7.3e
« Reply #50 on: December 28, 2015, 06:00:41 am »

What's the meaning of HK,PE,AI,AL in Services column at Peers page? Can someone explain to me? Thanks in advance.
Let me guess. HK = HALLMARK, PE = PRUNABLE, AI = API, AL = API_SSL.
Logged

qq2536007339

  • Hero Member
  • *****
  • Karma: +42/-9
  • Offline Offline
  • Posts: 514
    • View Profile
Re: NRS v1.7.3e
« Reply #51 on: December 28, 2015, 07:45:22 am »

Let me guess. HK = HALLMARK, PE = PRUNABLE, AI = API, AL = API_SSL.

That was a very good guess,thank you and one applaud for you.
Logged
你送我阿朵,我是要的。ARDOR-DJ68-PG7W-4JEU-2LU5T

Brangdon

  • Hero Member
  • *****
  • Karma: +229/-25
  • Offline Offline
  • Posts: 1389
  • Quality is addictive.
    • View Profile
Re: NRS v1.7.3e
« Reply #52 on: December 28, 2015, 11:55:25 am »

Archival node of not, it does not make a real difference because normal node will still hold the "sensitive" data for a certain time period (90 days by default).
That's why I'd need to take the node offline (and delete the database) until it expires. It can be set to expire after a couple of weeks.
Logged

Sebastien256

  • Hero Member
  • *****
  • Karma: +169/-24
  • Offline Offline
  • Posts: 2823
  • ^LOOK UP^ = Nxt community!
    • View Profile
Re: NRS v1.7.3e
« Reply #53 on: December 28, 2015, 12:19:26 pm »

Data cloud feature is cool. Good idea to have make a gui for that directly into the core wallet.  :)
Logged
Please drop your ideas concerning Nxt and/or NRS in this topic -> List of feature request for Nxt and/or NRS (with the full list in OP).

Sebastien256

  • Hero Member
  • *****
  • Karma: +169/-24
  • Offline Offline
  • Posts: 2823
  • ^LOOK UP^ = Nxt community!
    • View Profile
Re: NRS v1.7.3e
« Reply #54 on: December 28, 2015, 12:33:19 pm »

When a file is renew multiple time by multiple user, do the extend time period before the data is pruned is cummulative? I hope so.
Logged
Please drop your ideas concerning Nxt and/or NRS in this topic -> List of feature request for Nxt and/or NRS (with the full list in OP).

blackyblack1

  • Hero Member
  • *****
  • Karma: +165/-82
  • Offline Offline
  • Posts: 1764
    • View Profile
Re: NRS v1.7.3e
« Reply #55 on: December 28, 2015, 07:10:07 pm »

If you set nxt.apiServerHost=0.0.0.0 it will listen on all interfaces, including IPv6. Is there a reason not to use 0.0.0.0? The jetty documentation for setHost, which is where this parameter is used, says if it is 0.0.0.0 or null, it binds to all interfaces, doesn't mention how [::] is treated.
http://download.eclipse.org/jetty/9.3.6.v20151106/apidocs/org/eclipse/jetty/server/AbstractNetworkConnector.html#setHost-java.lang.String-
Looks like 0.0.0.0 option works for him. Is it possible to include some additional info (that IPv6 networks are supported) in the parameter description ?
Here is a description for peerServerHost parameter:

Code: [Select]
# Host interface on which to listen for peer networking requests, default all.
# Use 0.0.0.0 to listen on all IPv4 interfaces or :: to listen on all IPv4 and
# IPv6 interfaces
nxt.peerServerHost=0.0.0.0

I think it is wrong based on our previous discussion.
Logged
Pages: 1 2 [3]  All
 

elective-stereophonic
elective-stereophonic
assembly
assembly