have not been meaningfully improved by your co.

Sure, so long as you conveniently ignore the entire software category here.

"s.nsa" was a collaborative work of fiction perpetrated at MP's insistence while it pleased him.

Good to know, previously I'd described the situation in terms of a failure of S.NSA. Now I take it that the discontinuance of FUCKGOATS was a deliberate decision by Stanislav Datskovskiy.

Speaking of bugs, do you suppose that JFW's "wallet" proggy is bug-free? (spoiler: it very much isn't.) To whom should these be addressed?

There's no "should" here. Supposing you actually have something, you'll do whatever you'll do with it, and we'll act accordingly.

portray me as an incompetent

You're incompetent in dealing with people, not technical matters per se. You've known for a while that I learned about computers from reading you. It's not that you made a mistake, it's how you handled it (and are handling it).

rebadged copies of my inventions (V, FUCKGOATS)

We're linking, not rebadging. And those aren't your inventions, you'd have not made them without Mr. Popescu and S.NSA, which is what you used to say (the instance I recall was to kako post-s.bb schism), until he fired you. And now S.MG is writing the V for production use because you.. sat around rationalizing why you work for the enemy to turn around and pay rent in her swamp and meanwhile spat on every extended hand offered to help extract you.

Where were you and JFW while I was cutting 0.5.3 into TRB in '14?

I was working for Coinapult and JFW was sharpening his skills while moving abroad to Panama. You showed up to TMSR well before us, congrats and thank you I suppose though it's unclear how many potential people you drove away.

you believe (and would have your customers believe) that I defused all of the bombs therein? Where is the logic in this?

Instead of hallucinating what you write, I actually read and reflect -- at least most of the time. Never have I said the Bitcoin code --or underlying math for that matter-- is perfect. TRB was always described as a turd that's being polished / cleanest shirt in the dirty laundry. The contradiction is only in your conveniently contrived false narrative, not in what I've written or said.

help you to permanently obscure the origin of these products

I don't need or want help doing that because I'm not doing it nor do I want to.

which despite more than a year, have not been meaningfully improved by your co. or marketed with any degree of success -- I won't bother to argue the point any longer, will let your slowly dwindling cash reserves argue it instead.

You know, you're not any better an armchair management consultant than you are an armchair general. Our business started out focused on services, one of which being the consulting on which products to buy. We've not produced a TRNG to date, no, because the foundations we thought we were standing on meanwhile collapsed. I say this not to pass blame to anyone outside ourselves, but to provide context to any new readers. In the meanwhile, we've continued with the training and hardware sales (from the RESERVE WE BOUGHT outbidding you on the salvage of the Pizarro you shipwrecked) and have also been implementing another product/service in a pivot and the fact is... our cash reserves are UP.

The logs (which are readable by your prospective customers, and not only those sections you prefer to link to) show who it was who made it so that you have what to put new coats of paint on and sell to begin with.

I don't know if anyone has wasted more time than you with anti-signal nonsense. Don't insult our readers or customers who, if they have any merit, underfuckingstand the whole fucking log is there on Trilema and in case they've not read it before, the minimal required reading to sort out who's who and what's what is 6 months.

I invented and wrote V

You made a proof of concept script of a concept that was discussed for quite a while in the forum. Maybe you brought it up first, I'm not going to look cause anyone who wants to can and you've wasted enough of my time by giving me puke to clean up.

dragged people kicking and screaming to use it

Everyone was excited and very proud and congratulatory from the logs and blogs that I've read since 2014, 'V for Victory' anyone ? Buehler ?. I started reading in earnest in January 2015, but that included a lot of going back to years prior out of curiosity, searching and link following. Grow the fuck up already and quit pretending you were the single parent there washing ~and~ drying dishes.

and dug TRB out of the mud

On Mr. Popescu's orders.

FG was designed and built by yours truly, as you also know, "s.nsa" was a collaborative work of fiction perpetrated at MP's insistence while it pleased him.

I'm sure you did a lot of the work on FG, maybe even like 80%, but the reason it says NSA on the torn open asshole on the underside and not "Stanislav Datskovskiy" is because it wouldn't have existed without Mr. Popescu and MPEx. S.NSA was a company constituted by a contract you signed on to and financed by MPEx investors, not mighty mouse manalone.

Speaking of bugs, do you suppose that JFW's "wallet" proggy is bug-free? (spoiler: it very much isn't.) To whom should these be addressed?

The author of this blog. If he made a mistake, I trust he's competent enough to own it.

Where were you and JFW while I was cutting 0.5.3 into TRB in '14? Why not lifted a finger to help? And for that matter, realize that there's ~400kB of mostly untouched heathen code in there. I am, supposing, in your cosmography, a moron; but at the same time you believe (and would have your customers believe) that I defused all of the bombs therein? Where is the logic in this?

All the snake-tonguing in the world will not help you to permanently obscure the origin of these products (which despite more than a year, have not been meaningfully improved by your co. or marketed with any degree of success -- I won't bother to argue the point any longer, will let your slowly dwindling cash reserves argue it instead) as your would-be clientele *will* eventually discover the facts one way or another.

The logs (which are readable by your prospective customers, and not only those sections you prefer to link to) show who it was who made it so that you have what to put new coats of paint on and sell to begin with.

I invented and wrote V, dragged people kicking and screaming to use it; excavated Ada from oblivion, after many dead ends, and -- ditto; and dug TRB out of the mud (incidentally, you can easily do without all ~40 of the LOC I added to it, most of the effort consisted in cutting & instrumentation, as you well know). FG was designed and built by yours truly, as you also know, "s.nsa" was a collaborative work of fiction perpetrated at MP's insistence while it pleased him.

Speaking of bugs, do you suppose that JFW's "wallet" proggy is bug-free? (spoiler: it very much isn't.) To whom should these be addressed?

If the install base of your commercial offering were something other than zero, you would have discovered this bug long ago, via the same path as whaack did.

Well, whaack is our customer and he found the bug that crawled outta you and into the Bitcoin source. So I suppose you're wrong again. To underscore how wrong you are on this point, GBW-node is designed to trust TRB and only watch the addresses it's told about. This bug was discovered because whaack extended gbw-node to index all addresses and transactions. The underlying point you're attempting to make seems self-defeating, which I'll leave as an exercise for the alert reader.

So far I'm not seeing any signs that anyone at JWRD co. has put in serious effort to understand how the old cruft works;

Keep your projections to yourself. You're the one that signed off on the bug and you're the one with your pants down. Pull them up and tighten your belt rather than continuing to dump shit every which way you turn. Jacob tried using your thing and wrote an article expressing his troubles, which you hand waved away at the time and then later pretended no one used it to deflect responsibility. He also implemented Gales Linux (which allows us to cut out your cribbed buildroot) and cut out the wallet (which no one had publicly done). What you call trb returned incorrect data 2k blocks deep.

This doesn't even get into fixing bugs in v.pl no one else saw or making it keccak w/o gnat, but we don't need to list all the feathers in his cap.

Pro tip: *all* software that you didn't write *yourself* is a "poisoned offering".

Here you misrepresent "manalone" as "pro". Professionals understand trust enters into human relations and work to understand the extent to which they can trust the people they're working with and relying on. To profess is to claim or affirm and in practice this is either proven to stand or fall down.

If you ever take a moment to step out of reaction mode and reflect, it might occur to you that I referenced my betters to acknowledge they knew better and in the meantime I didn't do the work they advised. The top node there wasn't about "you", but that the trust model I have been acting out is broken and my betters knew.

Especially if you get carried away in lifting my work, sawing off serial numbers, and pretending it to be authorship

Get over yourself and your hallucinations already. Pics or it didn't happen, where have we done such ? For the record (not for "you", the record), with the FUCKGOATS we bought, we detail what they are in the contract and resell them in the manufacturer sealed packaging, as well as link to No Such lAbs in the latest article (this is called scholarship). We absolutely would have ordered more from you (as proven by outbidding YOU and paying a steep mark up on the originals) if that supply didn't collapse and you didn't get s.nsa wound up through your nonsense. We just found out the hard way we can't rely on your sigs on Bitcoin code.

Seems that you don't have the sendbuffer patch in your TRB either, which means that all nodes belonging to you and your customers -- should there one day be any -- are trivially remotely crashable.

It is correct we don't have this patch in our tree. For one thing, it's not directly usable because it doesn't build on our tree and is not signed by anyone active in our WoT. In order to use it, we'd have to review it ourselves and we've deemed this a low priority item because a) you yourself said it wasn't a full fix and we've not encountered this problem in practice (because we're not deploying publicly listening nodes for the time being), b) the problems we've observed in trb, e.g. the need to restart regularly, are unrelated to this issue and c) you've expressly stated you're operating in a reactive mode and not proactively understanding the code.

P.S.: MP won't "come back"; and if he were to come back, will not shower you with dough for having role-played SS Werwolf.

You have enough trouble speaking for yourself, I'm certainly not interested in hearing you speak for others.

asciilifeform: in other lulz, preening scammer duo pretending that trb fix 'unhappened'.

In closing, we're not pretending you didn't emit text that allegedly fixes your fuckup (wasn't dumpblock corrected once ?!), whaack's link to it in the log above will remain. The point is the patch does not solve the problem for us, i.e. the problem we've got ourselves into by trusting you. This is the root of what we have to fix and it doesn't involve you whatsoever.

If the install base of your commercial offering were something other than zero, you would have discovered this bug long ago, via the same path as whaack did.

So far I'm not seeing any signs that anyone at JWRD co. has put in serious effort to understand how the old cruft works; you thereby endanger both yourselves and your misfortunate customers, should they ever happen materialize. But this is between you and Beelzebub.

Pro tip: *all* software that you didn't write *yourself* is a "poisoned offering".

Especially if you get carried away in lifting my work, sawing off serial numbers, and pretending it to be authorship while demonstratively sneering; and consequently neglect to go back and crib fixes. (Seems that you don't have the sendbuffer patch in your TRB either, which means that all nodes belonging to you and your customers -- should there one day be any -- are trivially remotely crashable.)

P.S.: MP won't "come back"; and if he were to come back, will not shower you with dough for having role-played SS Werwolf.