-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Please consider this #1
Comments
Certainly seems like a quick fix. Whats the process for submitting an amendment? Little over my head but I'm sure I can help with the proposal? 4chan thread is blowing up with maxis already talking about a mass upload / shorting group.. These people have serious issues.. Looks like a PR is already in, that's fantastic |
its seems a quick fix. I think this is VERY important to do so. |
Technical discussion: XRPLF/rippled#3007 |
Great work, donated |
Let's start with a big thanks & hats off to you, as we can't have enough development in this ecosystem. Great to see you jumped in 😎
On a different note: I'm worried. I operate a full history node on the XRP ledger. I am very very much afraid of what will happen when your service will get some actual use. It'll be a matter of time before illegal content will be uploaded. Especially with the hate against the XRP community from maxi's. When someone uploads pirated content, or worse: child abuse images, no one would be able to remove that from their full history servers.
That would mean it would become a legal nightmare to run full history nodes, not only for me, but for all XRPL enthusiasts and businesses.
I would kindly ask (beg) you to take down the project.
P.S. In the long term I would suggest an amendment for the XRPL to exponentially increase the minimum transaction fee when large memo's are being sent. That would render this 'use case' non viable. Again: I really appreciate your efforts to develop for the XRP ledger, and please keep on doing so! But if you want to store files, consider using tech. meant to store files.
The text was updated successfully, but these errors were encountered: