edgeofinnerspace
commented
8 months ago i guess not ... ... ... ... ... ... ... ... ...
I'm quoting to reply to vs editing what I said to make the point that I meant no disrespect to anyone who created this. I could never get close to it. What I said should be understood without context - as simply as it is stated. The universe is an impersonal place after all.
But it should be known that it is, objectively, a depressing irony that something that could be useful and extremely helpful to so many - not just beginners - doesn't appear to be cared about. The only one who does seem to care about it wouldn't be able to use it but is trying to help update it.
I imagine someone with any kind of reason is patenting this right about now and integrating it with AI as I ramble on. Just remember that I tried when you write your last will!
i guess not because i've been needing help with a dependency issue for a while now. or for someone to help me update to replay protected transactions. I've tried on my own to fix both but i cannot code. my main issue is the fact that i have updated the transactions locally for it (tx block, sendTX, account module, etc) but i do not know how to override react stuff from devtools and i am only trying that because i cannot - as much as i have tried to and looked hi and lo for answers to the problems that turn up in the process - seem to get these dependencies working and i have gotten damned close.
i guess i have a final issue but not with the code itself: what was the point of building this especially if it was to help someone learn if you aren't atleast going to pass its caretaking on to an interested party? in abandoning this project, people like me who have truly sought to learn because they can understand it best through this method have given up too much of their time trying to fix a mess left behind and seemingly ignored. yea, i have learned a lot trying to fix the issues it seems like everyone else is having for the most part... but it probably wasnt the best choice for how to spend that time.
i've even tried build the other versions of this and all have similar problems. so i know its not just me. eth-rebuild, ethbuild-with-lit, the fork of this by 'theycallmeloki', and even the most recent updated fork which fixed the exact issue causing many of the problems... but lo and behold, now i cannot fix an issue with the characters in yarn.lock caused by the file encoding itself. i have even tried replacing with the original yarn.lock (knowing i would get the original dependency issue) then going and replacing the few things needed by hand (each keystroke - to avoid bringing in possible encoding problems from other yarn.lock) but apparently its not the encoding in that file but the dependency replacing the first one that caused issues.
i am at a complete loss as to how no one who actually knows about these kinds of things wanted to address this. after how long? thats why i said above.... ignored. not forgotten. i understand people are busy. i could be busier, i could be more responsible. if i werent kept busy with things that are not my responsibility to begin with.
but i digress. update if you find something working and i will do the same. already uploaded some things i thought would work on my fork as well as updated transaction nodes.