Topic: Re: [ANN][GLYPH] GlyphCoin - | Cryptsy BTC/LTC | Bittrex | Glyphbox Release - page 19. (Read 64058 times)

Thank you for the support

All I did want to say was ad rem. Explained why the tag was reasonable also after the # in the line 421 in my opinion.
Someone tried to abuse it for his illegitimate claims.
I hope you didn't take my words wrong.
Don't know who's doing the trolling but this is apparently an attack, not a fair discussion.
The new accounts without any history, created just to be used here. Possibly someone jealous for success of this coin.
I am sorry my for my post being used to launch this. It was no my intention or my fault.

I do appreciate your fixes and the timely manner fixes were done!

Lol, so now you start making unfounded accusations at my address?

I stopped, but I am willing to pick the glove up again if you start spreading falsehoods.

You are confusing accounts, you might want to read the username ... I did not personally attack anyone who did not call me a liar or dickhead first nor did I post that picture ... BTCmods will be able to confirm that. So good luck reporting me, I did nothing wrong, I only exposed your non-existent coding skills, and that, my friend, is most likely welcomed by most of the community, not looked down upon..

And you are apparently assuming C is the only language worth learning, let me wake you from that dream, there is a plethora of them.

However, I have to agree with you that the person who posted that picture went much too far, I also noticed the Github profile but chose not to disclose that information because it was nasty, I could've but I did not, you now pointing at me is not such a smart move if you want me to leave you muck on.

P.S.
And don't tell lies about Github doing something wrong, that account was used to push, don't make me explain how the record and history keeping of git works and why actual devs love it so much, there is however no proof whatsoever that person was involved with anything else then the initial push.

Not sure for the reasons for the attempted personal attack, or why this attacker says he has 31 years of coding experience but is just now learning C.

That picture is not the dev or anyone associated with the project. The github is being pushed with the account "glyphcoin" but for some reason, github makes Imagnai the listed author.

Bugs happen. We fix ours quickly.

Please, stop the harassment. BTCTalk mods have been notified about your attempts to personally attack others and expose identities.

These settings were optional but also wouldn't work anywhere else.
The reason for using # is sometimes because you want to leave enabling something easy but switch it off but default.

@Glyph devs - good job.

this guy seems to be gentleman?

lol,just like vootcoin dev dispear cause an accident. shabby fud have so many commons,get out quick after you earn enough profits, you better not to know what is hiding behind those copiers

Hey fuckhead,

I am not making up lies, you are being retarded, learn to read a fucking git commit history, you dumbass!

https://github.com/glyphcoin/glyphcoin/commit/96c59b570590066174a8c41b23fa0d1725405bb1

Line 421/422

Incredible how stupid this lot is ... retards of the week!
Not only do you nubs not know how to code, but you don't understand git either... so sad..

It's a good thing being stupid does not hurt, huh, else you would be in constant agony.

hey dickhead... Ive been watching this and stayed impartial. Now yr just making up lies - the code you're referring to is here:

https://github.com/glyphcoin/glyphcoin/blob/master/glyphcoin-qt.pro#L19




theres no comment on that line and they already replied to you about that exact part of the code, at the same time they pushed the last commit.


go outside and get some fresh air, please.

[sarcasm]Oh wow, you did such a good job! [/sarcasm]

Again showing off your non-existant skills I see!
You made me go LOL!

Changing:
for
does nothing

You just showed again you don't really understand what you are doing, since apparently you don't even know that lines starting with '# ' (note the whitespace after the #) are comments and not executed ><

But I am really gonna stop now ... otherwise you might manage to make your skills look legit due to my pointers

Have fun!
Buhbye!

I checked all code and replaced most by hand.

A coin is not a scam if the intentions are pure. The price has obviously risen, now more than 10x, and then stayed there. There is no "dump" - we have far bigger plans for the project.



Now please, stop trolling us! I need to get some sleep!! 

Lol .. doing more replaces to mask the fuckups of the first set of replaces is not a fix, a fix would require actual code to be written ;P
This still does not make you a dev ... show us some code you wrote which is unique to your implementation, then you are a dev.

I'll give you one thing though, you are good at this scamming thing, great responses, I could use someone like you on my team
With all these Fry's it must be like taking candy from a baby!

http://i1.kym-cdn.com/photos/images/original/000/264/241/9e9.gif

Very nice dev timely update 


I am very confident in your abilities to bring us many new features!

Thank you Marada, we pushed all fixes and updates within an hour or two tops.

We will be here with support and more features!!

More members have been added to dev team since launch.

Again, thanks for the heads up and free code audit, even if you felt the need to bring it with hate and FUD.

We updated within a couple hours of you pointing this out.


The original 'dev' claims he missed it because the code still worked properly. However, the pszTimestamp and nonce and other information was properly modified.

If you see anything else sloppy please let us know!


Github is properly updated with all fixes.

https://github.com/glyphcoin/glyphcoin



Also we have compiled a new windows wallet:

https://mega.co.nz/#!VElQGaQZ!Bk97CXTHOw91dHt2bulBBx0kAZVD7Hq9Kf9tJcKBs9I



We will be adding custom theme and features soon, and more announcements are coming.

Here is the problem, apparently cloning a git (5 sec) and running a search and replace (also 5 sec and this one was even poorly executed, case senstive would have been better) qualifies someone to be called a dev? I can tell you this is incredibly offensive to actual devs, who painstakingly work days and days to implement a new feature .. (I happen to be one, I have been coding for 31 years).

How can you trust someone who has shown no skill (rather a lack thereof) to deliver on promises of new features?

And yes, there are many more coins who deserve a good torching. But if were to expose all it would become a day job, and I already have one of those, being developer and all. Also we would be left with like 10 coins tbh

Either way .... I have done my part ... what you do with the information I provided is up to you lot ..

I am out .. back to actual developing.

This really wansn't the worst coin and dev I have to do with.
Yes, there were some minor bugs, but I have to notice unlike many other clones:
1) sources were released and possible to compile from the launch time,
2) DEV responds and does the fixes, seems to be interested.

These two things need to be appreciated.

@ ScamExposer:
Look around, there are many really worse coins. Why are you present only here?
Whenever you see the issue - post it, but give at least few hours so devs could react.
If only you are honest.

I've updated those lines to:

# Windows specific compilation parameters.    Thanks to Marada for the tip.
windows:BOOST_LIB_SUFFIX=-mgw48-mt-s-1_55
windows:BOOST_INCLUDE_PATH=C:/deps/boost_1_55_0
windows:BOOST_LIB_PATH=C:/deps/boost_1_55_0/stage/lib
windows:BDB_INCLUDE_PATH=C:/deps/db-4.8.30.NC/build_unix
windows:BDB_LIB_PATH=C:/deps/db-4.8.30.NC/build_unix
windows:OPENSSL_INCLUDE_PATH=C:/deps/openssl-1.0.1g/include
windows:OPENSSL_LIB_PATH=C:/deps/openssl-1.0.1g
windows:MINIUPNPC_INCLUDE_PATH=C:/deps
windows:LIBPNG_INCLUDE_PATH=C:/deps/libpng-1.6.9
windows:LIBPNG_LIB_PATH=C:/deps/libpng-1.6.9/.libs
windows:MINIUPNPC_LIB_PATH=C:/deps/miniupnpc
windows:QRENCODE_INCLUDE_PATH=C:/deps/qrencode-3.4.3
windows:QRENCODE_LIB_PATH=C:/deps/qrencode-3.4.3/.libs

I will push the changes soon.

Thanks all!

Drop dead you knucklehead, you are obviously affiliated with these scammers by defending a 5 minute search and replace job .... I will torch this scam as much as I want ... truth hurts huh!

We will see who is right in a few hours when this suposed update is coming from people who don't even know how to read C, let alone write it.

We will see who has the last laugh!