Bitcoin Forum
August 18, 2019, 04:20:16 AM *
News: Latest Bitcoin Core release: 0.18.0 [Torrent] (New!)
 
   Home   Help Search Login Register More  
Pages: « 1 ... 1462 1463 1464 1465 1466 1467 1468 1469 1470 1471 1472 1473 1474 1475 1476 1477 1478 1479 1480 1481 1482 1483 1484 1485 1486 1487 1488 1489 1490 1491 1492 1493 1494 1495 1496 1497 1498 1499 1500 1501 1502 1503 1504 1505 1506 1507 1508 1509 1510 1511 [1512] 1513 1514 1515 1516 1517 1518 1519 1520 1521 1522 1523 1524 1525 1526 1527 1528 1529 1530 1531 1532 1533 1534 1535 1536 1537 1538 1539 1540 1541 1542 1543 1544 1545 1546 1547 1548 1549 1550 1551 1552 1553 1554 1555 1556 1557 1558 1559 1560 1561 1562 ... 2567 »
  Print  
Author Topic: NXT :: descendant of Bitcoin - Updated Information  (Read 2755812 times)
^[GS]^
Member
**
Offline Offline

Activity: 112
Merit: 10


View Profile
February 06, 2014, 06:17:29 AM
 #30221

Fee voting tally google doc spreadsheet.  Please check your vote and PM me if I made a mistake.

https://docs.google.com/spreadsheet/ccc?key=0Akjrt0LTBXgcdFFkSGMwXzd4Q2NPU21yU2NOYWVldlE&usp=sharing

fix me! only 1 to 0.1!

I never said 0.3333 Tongue

0.3333 is only meant to as way to divide your vote by 3.  So, you have 1/3 vote in 0.01, 0.1, and 1 columns.

Analysis based upon your post here:

I vote 0.1 Fee for transactions!
and 0.01 for messages! 1 NXT for alias.


If this is not desired, please specify how this should be tallied.

Sorry for the confusion.
In general fee, 0.1 is fine!

I just wanted to describe various fee in different functions.



Holy java errors batman!

23 public hallmarked VPSs (ery heavy weights) down hard.
Did you copy old web.xml from 0.5.12? They're incompatible.
which is what is new in web.xml from 0.6.0?

PS: API would be very useful to reload web.xml while running. besides being able to read the hallmark of oneself from admin.html.
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1566102016
Hero Member
*
Offline Offline

Posts: 1566102016

View Profile Personal Message (Offline)

Ignore
1566102016
Reply with quote  #2

1566102016
Report to moderator
pandaisftw
Full Member
***
Offline Offline

Activity: 224
Merit: 100


View Profile
February 06, 2014, 06:25:28 AM
 #30222

Hm, that's assuming the merchant keeps those accounts empty right? I think a workaround would be that as long as the merchant plans to use that account for his customers, it should never be empty (he asks the client to keep at least 0.01 NXT in there). If the client empties out his account, then the merchant simply generates a new one for the client to use next time and tells him to not use the old one because the client emptied it out.

I think we should seriously consider forcing this behavior so we can prune public keys of accounts with no balance and no aliases

Speaking of aliases, another way to "preserve" your account would be simply registering an alias. You have to send out a transaction anyways to get your public key, so if you're interested in making some "back-up" empty accounts, you just register an alias as you would have anyways. In the merchant example, the merchant simply just makes up an alias for the customer (maybe an ID #) on that account, and the account won't be erased during pruning.

NXT: 13095091276527367030
^[GS]^
Member
**
Offline Offline

Activity: 112
Merit: 10


View Profile
February 06, 2014, 06:31:34 AM
 #30223

Found in "Get Peers" of https://localhost:7875/admin.html

Quote
"184.75.214.66",
"36.63.156.102",
"adress_ip", <<<
"188.27.102.67",
"108.53.130.113",

Quote
"95.85.46.126",
"84.6.140.192",
"50.30.46.177;209.126.96.136;209.126.96.137;209.126.96.138", <<<
"195.3.205.202",
"109.75.223.181",

Perhaps should better control of peers.
It could even prevent connecting to very old versions.
EmoneyRu
Hero Member
*****
Offline Offline

Activity: 600
Merit: 500

Nxt-kit developer


View Profile
February 06, 2014, 06:32:42 AM
 #30224

23 public hallmarked VPSs (ery heavy weights) down hard.
Upd: 0.6.0 template compatibility

xyzzyx
Sr. Member
****
Offline Offline

Activity: 490
Merit: 250


I don't really come from outer space.


View Profile
February 06, 2014, 06:50:47 AM
Last edit: February 06, 2014, 07:01:02 AM by xyzzyx
 #30225

I don't think a low-memory device like a RaspberryPi would need a full blockchain to forge.  It would only need just over 1440 blocks.  If it needs to consult blocks that it doesn't have because they're too far in the past, it can get them by querring the API of a public node -- or several public nodes.

It can keep a list of SHA256 hashes of the blocks it deletes to check that the ones it gets from a public node are correct.

Or am I missing something?

"An awful lot of code is being written ... in languages that aren't very good by people who don't know what they're doing." -- Barbara Liskov
lucky88888
Sr. Member
****
Offline Offline

Activity: 404
Merit: 250


https://nxtforum.org/


View Profile
February 06, 2014, 07:04:19 AM
 #30226

To a certain extent if the lead developer issues a release and says it's critical we have no choice but to trust him.  But, outside developers can and should perform their own independent audits of new releases to see if something suspicious is done and raise the alarm if need be.

Most Nxt users are not "developers", so while I take your point, I also suggest that most people are being asked to update software without being able to understand OR verify the reason for the update.  It's the software-developer equivalent of "trust me. Just do it."

It's hypocritical to build a decentralized system that is supposed to be trustless, and then ask "untrusted" members of that community to "trust" that they should install new software and not ask questions of the "untrusted" people who issue the order.

You can do your own thing, of course, but I won't give.  I'm not gonna jump off a bridge just because Jean-Luc or CfB says so.  What they've done is bad, and they should feel bad.  When I get an explanation, I'll update my software.

It is unfortunate they had to do it this way, but if they said it was urgent, then it most likely is. The fact that both of them (and I suppose the implicit approval of BCNext) approved it makes it not as bad. C-f-b did say he would disclose what it was, but I'm sure how won't do that until a large majority of nodes have upgraded to 0.6.0.

While its possible for someone to secretly add something inside for his own selfish need BUT in this case, its Jean-Luc and CfB for crying out loud.. im sure they would not try to do anything that is bad for nxt, it would be in their best interest to do what is right. If they don't the whole eco would collapse over night. They are the lead devs, from what i know they are probably the only ones coding nxt for what it is today.
If you won't trust the only core developers, i don't know who else is there to trust in such situation.

I'm pretty damn sure they are pushing this update for one reason, that is to prevent exploitation of the said critical bug.
And to me, it sounds pretty serious when they are not saying the specifics of the actual bug, maybe they are hoping for majority to update and be on the 0.6.0 chain before such bug is exploited thus not providing such details.

To sum up: ITS SAFE TO UPDATE to 0.6.0 so please everyone upgrade as soon as possible before someone finds such exploit mentioned.
CRITICAL MANDATORY UPDATE
http://download.nxtcrypto.org/nxt-client-0.6.0.zip

Fuck Mt.Gox! Fuck Mintpal! Fuck Bter! FUCK kyc! Protect yourself use MGW! SUPERNET!
Recommended ASSET ->InstantDex : Lead Dev Jl777 (decentralized multi currency instant exchange)
Recommended ASSET -> Jinn : Lead Dev Come-from-Beyond (ternary processors!)
https://nxtforum.org/news-and-announcements/(ann)-jinn/
farl4web
Legendary
*
Offline Offline

Activity: 1202
Merit: 1000


aka farl4bit aka farl


View Profile WWW
February 06, 2014, 07:11:35 AM
 #30227

Tonight I was thinking again about the fees. We should not change the fees already, it's not wise.

In this early fase of Nxt I hear nobody complaining about the high fees, mostly because not a lot of payments are done.

But I DO hear a lot of complaining about the joke of forging. In the early fase of a cryptocoin, the miners/investors are the most important people, they make a coins succesfull (look at Dogecoin). To get a lot of attention, we need to attract the miners and investors first!

Later when it gets more populair you can lower the fees!

Follow the latest blockchain news: https://twitter.com/blockchainguide
Come-from-Beyond
Legendary
*
Offline Offline

Activity: 2128
Merit: 1009

Newbie


View Profile
February 06, 2014, 07:18:27 AM
 #30228

Any chance to be able to have function calls to a subset of what is in nxt core?
That way for extra cost, sha256 can be done without bloating script with lots of opcodes

Let's see how it works without SHA256 and then decide.
Come-from-Beyond
Legendary
*
Offline Offline

Activity: 2128
Merit: 1009

Newbie


View Profile
February 06, 2014, 07:19:09 AM
 #30229

Any chance to be able to have function calls to a subset of what is in nxt core?
That way for extra cost, sha256 can be done without bloating script with lots of opcodes
Basic cryptographic functions should be made opcodes. Implementing sha in this really doesn't make much sense. 

Why would someone need SHA256 in a script?
lucky88888
Sr. Member
****
Offline Offline

Activity: 404
Merit: 250


https://nxtforum.org/


View Profile
February 06, 2014, 07:22:10 AM
Last edit: February 06, 2014, 07:33:38 AM by lucky88888
 #30230

Tonight I was thinking again about the fees. We should not change the fees already, it's not wise.

In this early fase of Nxt I hear nobody complaining about the high fees, mostly because not a lot of payments are done.

But I DO hear a lot of complaining about the joke of forging. In the early fase of a cryptocoin, the miners/investors are the most important people, they make a coins succesfull (look at Dogecoin). To get a lot of attention, we need to attract the miners and investors first!

Later when it gets more populair you can lower the fees!

Actually at the moment most blocks mined are with 0 fees inside. So lowering the fee may encourage many new nxters with very low balances to play around and afford to send a friend a nxt without bankrupting their own.

With new lower fees you may actually receive 0.1fees in almost all blocks, this is better than 0 fees received. Which actually is more enticing to forging. Most new nxters are not here to forge for a profit at this early stage of the growing nxt economy, but they are forging because they are hoping they would receive something at all.

As the nxt economy grows, naturally things will come together, but this would encourage a better boost.

EDIT: MOST doge owners are probably in their teens, and the most would probably have 100doges and be very happy about it. Think how much is that worth?? nearly nothing, but that 100doge multiply by a million teens, that is something. Which is one reason doge is not dead yet.

Now think of nxt in the same situation, young people getting their nxt from faucets would be their only source of nxt income, everyone receives 1-2nxt some may have 10nxt! wow! Now if they are able to spend 1 or 2 nxt without bankruptcy i'm sure they would be happy to pass it on to their friends.
This, multiply by 1million and it doesn't seem so stupid for those kids who only have 1 or 2nxt.

EDIT 2: Kids/Teens are what causes viral things on the internet that just explodes over night. Maybe someone should think of marketing somthing towards the younger generations.

Fuck Mt.Gox! Fuck Mintpal! Fuck Bter! FUCK kyc! Protect yourself use MGW! SUPERNET!
Recommended ASSET ->InstantDex : Lead Dev Jl777 (decentralized multi currency instant exchange)
Recommended ASSET -> Jinn : Lead Dev Come-from-Beyond (ternary processors!)
https://nxtforum.org/news-and-announcements/(ann)-jinn/
landomata
Legendary
*
Offline Offline

Activity: 1820
Merit: 1000


View Profile WWW
February 06, 2014, 07:28:45 AM
 #30231

Guys & Gals,

I think it would be great to have a Asset Exchange Explorer type website similar to our blockexplorer http://87.230.14.1/nxt/nxt.cgi?action=1


Development can begin now so that it would be ready when the Asset Exchange officially launches.


CIYAM
Legendary
*
Offline Offline

Activity: 1890
Merit: 1003


Ian Knowles - CIYAM Lead Developer


View Profile WWW
February 06, 2014, 07:28:58 AM
 #30232

Why would someone need SHA256 in a script?

Atomic-cross chain transactions and the like will require a hash function (I would assume SHA256 would be the most likely to include).

If we can't get atomic-cross chain transactions to work then I think the idea of being able to have a trust-less P2P "coin" exchange simply won't work (not that we have to use a "smart contract" to do this of course but it would seem like something reasonable to support as other such "use cases" undoubtedly will arise).

With CIYAM anyone can create 100% generated C++ web applications in literally minutes.

GPG Public Key | 1ciyam3htJit1feGa26p2wQ4aw6KFTejU
Coinonaer
Full Member
***
Offline Offline

Activity: 168
Merit: 100


View Profile
February 06, 2014, 07:31:03 AM
 #30233

this has to be a record amount of time between comments in this thread
I thought it must have been broken!
If it weren't for my blabber, it would have been over 90 minutes between posts.

wonder why its so quiet. it isnt some sort of holiday or something is it.

chinese new year!
Chinese new year is over now.I miss all of you.

welcome Back Sir  Smiley
l8orre
Legendary
*
Offline Offline

Activity: 1065
Merit: 1002


View Profile
February 06, 2014, 07:33:20 AM
 #30234

Guys & Gals,

I think it would be great to have a Asset Exchange Explorer type website similar to our blockexplorer http://87.230.14.1/nxt/nxt.cgi?action=1


Development can begin now so that it would be ready when the Asset Exchange officially launches.



I am making good progress on getting AE into my Client - as let's see what the testing does. Any tentative dates for 'official launch' of AE??
 
Come-from-Beyond
Legendary
*
Offline Offline

Activity: 2128
Merit: 1009

Newbie


View Profile
February 06, 2014, 07:33:33 AM
 #30235

Advanced data compression algos are helped by moores law
Same for switches, routers
Cables are problem, but maybe big breakthrough in wireless bandwidth

shannon says otherwise, and we are much closer to his comm theory limit than we are to running up on moore.  thats a very large maybe in there as well

We could switch to three-valued logic for better compression. Not so effective as 2.72-valued but still better then binary...
l8orre
Legendary
*
Offline Offline

Activity: 1065
Merit: 1002


View Profile
February 06, 2014, 07:34:19 AM
 #30236


Holy java errors batman!

Code:
root@vps1:~/nxt-kit/nxt# java -jar start.jar
WARNING: System properties and/or JVM args set.  Consider using --dry-run or --exec
2014-02-06 05:38:30.341:WARN:root:main: unavailable
javax.servlet.UnavailableException: Servlet class Nxt is not a javax.servlet.Servlet
at org.eclipse.jetty.servlet.ServletHolder.checkServletType(ServletHolder.java:447)
at org.eclipse.jetty.servlet.ServletHolder.doStart(ServletHolder.java:312)
at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:69)
at org.eclipse.jetty.servlet.ServletHandler.initialize(ServletHandler.java:839)
at org.eclipse.jetty.servlet.ServletContextHandler.startContext(ServletContextHandler.java:300)
at org.eclipse.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1347)
at org.eclipse.jetty.server.handler.ContextHandler.doStart(ContextHandler.java:743)
at org.eclipse.jetty.webapp.WebAppContext.doStart(WebAppContext.java:492)
at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:69)
at org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:117)
at org.eclipse.jetty.util.component.ContainerLifeCycle.addBean(ContainerLifeCycle.java:281)
at org.eclipse.jetty.util.component.ContainerLifeCycle.addBean(ContainerLifeCycle.java:213)
at org.eclipse.jetty.util.component.ContainerLifeCycle.updateBeans(ContainerLifeCycle.java:763)
at org.eclipse.jetty.server.handler.HandlerCollection.setHandlers(HandlerCollection.java:89)
at org.eclipse.jetty.server.handler.ContextHandlerCollection.setHandlers(ContextHandlerCollection.java:144)
at org.eclipse.jetty.server.handler.HandlerCollection.addHandler(HandlerCollection.java:155)
at org.eclipse.jetty.deploy.bindings.StandardDeployer.processBinding(StandardDeployer.java:41)
at org.eclipse.jetty.deploy.AppLifeCycle.runBindings(AppLifeCycle.java:186)
at org.eclipse.jetty.deploy.DeploymentManager.requestAppGoal(DeploymentManager.java:498)
at org.eclipse.jetty.deploy.DeploymentManager.addApp(DeploymentManager.java:146)
at org.eclipse.jetty.deploy.providers.ScanningAppProvider.fileAdded(ScanningAppProvider.java:180)
at org.eclipse.jetty.deploy.providers.ScanningAppProvider$1.fileAdded(ScanningAppProvider.java:64)
at org.eclipse.jetty.util.Scanner.reportAddition(Scanner.java:605)
at org.eclipse.jetty.util.Scanner.reportDifferences(Scanner.java:528)
at org.eclipse.jetty.util.Scanner.scan(Scanner.java:391)
at org.eclipse.jetty.util.Scanner.doStart(Scanner.java:313)
at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:69)
at org.eclipse.jetty.deploy.providers.ScanningAppProvider.doStart(ScanningAppProvider.java:150)
at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:69)
at org.eclipse.jetty.deploy.DeploymentManager.startAppProvider(DeploymentManager.java:560)
at org.eclipse.jetty.deploy.DeploymentManager.doStart(DeploymentManager.java:235)
at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:69)
at org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:117)
at org.eclipse.jetty.server.Server.start(Server.java:355)
at org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:99)
at org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:60)
at org.eclipse.jetty.server.Server.doStart(Server.java:324)
at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:69)
at org.eclipse.jetty.xml.XmlConfiguration$1.run(XmlConfiguration.java:1250)
at java.security.AccessController.doPrivileged(Native Method)
at org.eclipse.jetty.xml.XmlConfiguration.main(XmlConfiguration.java:1174)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.eclipse.jetty.start.Main.invokeMain(Main.java:297)
at org.eclipse.jetty.start.Main.start(Main.java:724)
at org.eclipse.jetty.start.Main.main(Main.java:103)
2014-02-06 05:38:30.366:WARN:root:main: unavailable
javax.servlet.UnavailableException: Servlet class Nxt is not a javax.servlet.Servlet
at org.eclipse.jetty.servlet.ServletHolder.checkServletType(ServletHolder.java:447)
at org.eclipse.jetty.servlet.ServletHolder.doStart(ServletHolder.java:312)
at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:69)
at org.eclipse.jetty.servlet.ServletHandler.initialize(ServletHandler.java:857)
at org.eclipse.jetty.servlet.ServletContextHandler.startContext(ServletContextHandler.java:300)
at org.eclipse.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1347)
at org.eclipse.jetty.server.handler.ContextHandler.doStart(ContextHandler.java:743)
at org.eclipse.jetty.webapp.WebAppContext.doStart(WebAppContext.java:492)
at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:69)
at org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:117)
at org.eclipse.jetty.util.component.ContainerLifeCycle.addBean(ContainerLifeCycle.java:281)
at org.eclipse.jetty.util.component.ContainerLifeCycle.addBean(ContainerLifeCycle.java:213)
at org.eclipse.jetty.util.component.ContainerLifeCycle.updateBeans(ContainerLifeCycle.java:763)
at org.eclipse.jetty.server.handler.HandlerCollection.setHandlers(HandlerCollection.java:89)
at org.eclipse.jetty.server.handler.ContextHandlerCollection.setHandlers(ContextHandlerCollection.java:144)
at org.eclipse.jetty.server.handler.HandlerCollection.addHandler(HandlerCollection.java:155)
at org.eclipse.jetty.deploy.bindings.StandardDeployer.processBinding(StandardDeployer.java:41)
at org.eclipse.jetty.deploy.AppLifeCycle.runBindings(AppLifeCycle.java:186)
at org.eclipse.jetty.deploy.DeploymentManager.requestAppGoal(DeploymentManager.java:498)
at org.eclipse.jetty.deploy.DeploymentManager.addApp(DeploymentManager.java:146)
at org.eclipse.jetty.deploy.providers.ScanningAppProvider.fileAdded(ScanningAppProvider.java:180)
at org.eclipse.jetty.deploy.providers.ScanningAppProvider$1.fileAdded(ScanningAppProvider.java:64)
at org.eclipse.jetty.util.Scanner.reportAddition(Scanner.java:605)
at org.eclipse.jetty.util.Scanner.reportDifferences(Scanner.java:528)
at org.eclipse.jetty.util.Scanner.scan(Scanner.java:391)
at org.eclipse.jetty.util.Scanner.doStart(Scanner.java:313)
at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:69)
at org.eclipse.jetty.deploy.providers.ScanningAppProvider.doStart(ScanningAppProvider.java:150)
at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:69)
at org.eclipse.jetty.deploy.DeploymentManager.startAppProvider(DeploymentManager.java:560)
at org.eclipse.jetty.deploy.DeploymentManager.doStart(DeploymentManager.java:235)
at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:69)
at org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:117)
at org.eclipse.jetty.server.Server.start(Server.java:355)
at org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:99)
at org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:60)
at org.eclipse.jetty.server.Server.doStart(Server.java:324)
at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:69)
at org.eclipse.jetty.xml.XmlConfiguration$1.run(XmlConfiguration.java:1250)
at java.security.AccessController.doPrivileged(Native Method)
at org.eclipse.jetty.xml.XmlConfiguration.main(XmlConfiguration.java:1174)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.eclipse.jetty.start.Main.invokeMain(Main.java:297)
at org.eclipse.jetty.start.Main.start(Main.java:724)
at org.eclipse.jetty.start.Main.main(Main.java:103)

23 public hallmarked VPSs (ery heavy weights) down hard.


I experienced this epic java faiul too. rescanning whole blockchain now. interesting to see how long it'll take ..
CrazyEyes
Full Member
***
Offline Offline

Activity: 137
Merit: 100


View Profile
February 06, 2014, 07:37:08 AM
 #30237

Message by Come-from-Beyond
Relevance: 25.2%
Quote from: wesleyh on December 26, 2013, 10:51:24 AM
Here's a question from j0b (who for some reason can't post in here) :

"if a new client joins the network and need to sync the blockchain. if the clients current blockchain id is >= existing blockchain number - 10000 (or something).. send a compressed version of blockchain and extract it locally"

Wouldn't that save a bit on processing, as some clients may not have an up-to-date blockchain. (new users, etc)

Think of it as gzip compression in PHP.

Thoughts?



Looks like premature optimization.

............. Eh? Now all the sudden compression is a good idea. Arrogance is bless (changed that;))) /j0b
Fatih87SK
Hero Member
*****
Offline Offline

Activity: 616
Merit: 500



View Profile
February 06, 2014, 07:39:51 AM
 #30238

Hi CFB,

I think I've got it now. The final result;

http://i.imgur.com/FI2i3Ls.jpg


Aye, very similar to what I wanted. Tomorrow I'll find a better texture of slate, this one looks ugly.

Alright! I'm waiting for it. Will work on it when I get home.

Ps. I received two donations today. Thank you guys! You made me feel good!

Passion_ltc
Hero Member
*****
Offline Offline

Activity: 714
Merit: 500


Crypti Community Manager


View Profile
February 06, 2014, 07:40:18 AM
 #30239

Wasn't the AE integrated into the 0.6.0er update?

lucky88888
Sr. Member
****
Offline Offline

Activity: 404
Merit: 250


https://nxtforum.org/


View Profile
February 06, 2014, 07:43:12 AM
 #30240

Guys & Gals,

I think it would be great to have a Asset Exchange Explorer type website similar to our blockexplorer http://87.230.14.1/nxt/nxt.cgi?action=1


Development can begin now so that it would be ready when the Asset Exchange officially launches.



I am making good progress on getting AE into my Client - as let's see what the testing does. Any tentative dates for 'official launch' of AE??
 

what date do you have in mind?

What about 7th of Feb?

Fuck Mt.Gox! Fuck Mintpal! Fuck Bter! FUCK kyc! Protect yourself use MGW! SUPERNET!
Recommended ASSET ->InstantDex : Lead Dev Jl777 (decentralized multi currency instant exchange)
Recommended ASSET -> Jinn : Lead Dev Come-from-Beyond (ternary processors!)
https://nxtforum.org/news-and-announcements/(ann)-jinn/
Pages: « 1 ... 1462 1463 1464 1465 1466 1467 1468 1469 1470 1471 1472 1473 1474 1475 1476 1477 1478 1479 1480 1481 1482 1483 1484 1485 1486 1487 1488 1489 1490 1491 1492 1493 1494 1495 1496 1497 1498 1499 1500 1501 1502 1503 1504 1505 1506 1507 1508 1509 1510 1511 [1512] 1513 1514 1515 1516 1517 1518 1519 1520 1521 1522 1523 1524 1525 1526 1527 1528 1529 1530 1531 1532 1533 1534 1535 1536 1537 1538 1539 1540 1541 1542 1543 1544 1545 1546 1547 1548 1549 1550 1551 1552 1553 1554 1555 1556 1557 1558 1559 1560 1561 1562 ... 2567 »
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!