I recommend you read Fees are LOW/HIGH, use this opportunity to Consolidate your small inputs!, it explains how to handle fees and how to make low-fee transactions at the right moment. One option would be to make your customers pay for the fee needed to consolidate the payments. That's what Bitpay does: they charge their own "network fee" to cover their transaction fee (on top of the network fee you pay when you make the transaction). |
|
|
|
Please make an opportunity to create an account and register on the site Please don't do that, but instead provide a hash that can be saved and used to restore the account (or clone the same account to a different browser/device). One of the great things about Lightning Network is instant deposits and withdrawals without accounts  |
|
|
|
You might be underestimating false positives - it's a killer when you're dealing with 50 million posts. 1% false positive rate would require you to review 500 thousand posts manually, unfeasible. So you probably want to tune the parameters to the point where you have very few false positives even if it comes at a cost of letting some (or many) plagiarists slip through so that you could still catch many others without wading through almost identical bounty reports and other crap. I might give it a shot if I have the time some day What you are describing would only detect entire posts that are copied. If someone added a single word, the post would not be flagged as a duplicate. I have also noticed that some plagiarists like to copy parts of posts/content, sometimes from different sources. Also sorting as you describe is just another way of checking every post against every other post. This is how you would put everything in the correct order.
You could index parts of the text (for example the first word or the first letter of the first word) to reduce runtime, but the cost to check each post against every other post is still expensive.
Example: What you are describing would > 4081ffba8ba8e9aa702ba47c868c86ab you are describing would only > a4476131d8f6a76d09daabe2c0e12ff5 are describing would only detect > f805a9b6e8756ec0e7e8d9d9b9f6085e would only detect entire posts that > 3190387c55974545cf2d2045197ee70b After generating the checksums, only the checksums have to be sorted and searched for duplicates. I've used that before to find matching Bitcoin addresses in very long lists, and it only takes seconds to search through gigabytes of data. The benefit of this method is being able to use very efficient existing sorting algorithms. |
|
|
|
@Theymos and Admin; please do something soon. Mods don't always act quickly on posts in this topics. I assume the posts in question have been reported too, and I also assume this is now being discussed on the Moderators' board. |
|
|
|
Can you teach me or somehow publish a thread on how to do scrapping? Scraping is nothing more than just automating downloading data. You can use countless different methods, and my method won't likely fit many other people. So just find what works for you, and use that. |
|
|
|
Everything depends on if the server is trusted or not. Every roll is independent of the previous and your chance to hit a roll is always the same. I suggest to discuss only provably fair games here(preferably dice). If the game itself can't be trusted, the question about server seed change is meaningless. It depends who changes the server seed: if the host decides to change it, they might have had a reason to do so. If the user decides to change it, the server could still give a seed that's bad for the way you're playing. However, they also risk you changing your strategy after using a new seed, so that's a risky thing to do. This explains better what I mean: Ryan, when Bustabit v1 is taken down, could you reveal the 10,000,000th game's hash (the first generated hash)? For legitness. Why would you care about the hashes of any of the games which were never played? It might make sense to look at future games, to check if that's the motivation for the new hash chain (or the timing of the release of it). Oh yes, that's a good point. It could be that the players were due for a good green streak, and so you've decided to switch to a new random sequence. |
|
|
|
To demonstrate the cost of checking for plagiarism:
If you check every group of 5 consecutive words in each post in a user's post history against every group of 5 consecutive words in every other post that exists:
Assuming the userbase has made 50 million posts, 40 million of which (80%) has at least 5 words, and the average post length is 15 words.
Each post you check for plagiarism would cause you to make 11 queries, and each query would check against 440 million rows in your database. So each post you check would need to be compared against 4.84 billion rows. It's madness to check everything against everything. If I'd be chasing this (which I'm not), I'd create a checksum for each string of text, sort all checksums, search for duplicates, and use those to check back the original posts. This way you don't have to iterate through all posts, but catch them all at once in a very fast process. Of course there'll be many false positives and the slightest change in a word would be missed, but this cause would have been caught. |
|
|
|
vod gave me neg feedback for i gave merit to OG "Vod 2020-05-21 Reference Helping a scammer conceal a 2,600BTC scam." hey Loycev, suchmoon ! why you not distrust Vod ?
this is not trust abuse? If the feedback is only for Meriting a post (and it looks like that from the Reference link), I think it is. And so does theymos: If a DT member tags you for something stupid involving merit (ie. probably anything less than selling merit), then they're not going to be a DT member for much longer. Vod: Meriting a post is not necessarily an endorsement. And although it probably is in this case, I sometimes Merit posts because they're worth reading because they say a lot about the person posting it ( example). Let me put it this way: if OgNasty's post would have been about me, I probably would have Merited it myself. In peloso's case, I don't think the negative feedback is justified. I've said it before but I'll say it again: OgNasty should ignore Vod, and Vod should ignore OgNasty! You two don't like each other, we get it. That's okay. Let it be, and move on. |
|
|
|
Whoohoo, nice work Rikafip, hopefully this contest will drag more people to the server.
I'll join  I've never used Discord before, but I'll join and I've outsourced the pizza making to my wife. Lockdown for the win  The deal is: if she wins, she sets up her own Bitcoin wallet. Until now, she's always rejected that. |
|
|
|
Update (based on last Saturday's Trust data dump): This has grown to 4.6 GB of data. On my Trust list, I include 19 users on Depth 0, 159 on Depth 1 and 443 on Depth 2. There are even more on Depth 3 and 4, but I don't use see those with default (Trust depth 2) settings. On Depth 1 already, I don't recognize all usernames. My exclusions on Depth 1 include many users who's judgement I don't necessarily distrust. On Depth 2, I don't recognize the majority of the 2003 excluded users.
Use this to improve your own Trust list. If anyone wants an update later, feel free to ask. |
|
|
|
Loyce, could you save the seclog data in .txt format as same as what you usually do with merit and btc blockchain data? Sure, all it took was one long line of code: See seclog.txt (or seclog.txt.gz): UnixTime UserID String
1590075009 2490711 woke up
1590074446 2491035 woke up
1590074179 1706830 woke up
1590073677 83586 woke up
1590073568 1115137 woke up
1590073086 2612874 password reset via email
1590072435 1817851 woke up
1590072232 1715288 woke up
1590071571 459378 woke up
1590071559 1304409 woke up
1590071550 459378 password reset via email
1590070728 998158 woke up
1590070330 366549 woke up
1590070316 949002 woke up
1590070280 1161921 woke up
1590069550 2612498 woke up
1590069117 2433138 woke up
1590068811 1064700 woke up
1590068499 1073616 woke up
1590068456 2603243 password reset via email
1590068448 1073616 password reset via email
1590067842 1421454 woke up
1590067829 1421454 password reset via email
1590067306 1748392 woke up
1590066644 1229436 woke up
1590066629 1229436 password reset via email
1590066209 842426 password changed
1590066182 842426 woke up
1590066059 1049269 password changed
1590066029 1748388 woke up
1590066025 1049269 woke up
1590065265 2272659 woke up
1590065031 331517 woke up
1590065013 290762 woke up
1590064921 322576 woke up
1590064854 2579450 woke up
1590064771 862915 woke up
1590064752 1380772 woke up
1590064532 2715207 woke up
1590064129 2809340 password reset via email
1590063915 2187418 password reset via email
1590063455 1111537 woke up
1590063406 2651918 woke up
1590063359 1194657 woke up
1590063197 2457299 woke up
1590062684 49320 woke up
1590062406 1797438 woke up
1590062156 1420329 woke up
1590062080 1099430 woke up
1590061969 1866874 password reset via email
1590061568 2710692 woke up
1590061371 2685759 woke up
1590061145 2579651 woke up
1590060861 1740285 woke up
1590060757 2653941 woke up
1590059965 2703192 woke up
1590059598 20145 woke up
1590059482 1831063 woke up
1590059466 1733619 woke up
1590058854 2573487 woke up
1590058343 2111196 woke up
1590058308 979231 woke up
1590058300 2324268 woke up
1590058262 1232629 password reset via email
1590058223 104892 woke up
1590057824 2517791 woke up
1590057718 23696 manual recovery, ownership change queued
1590057578 2567195 woke up
1590057238 77542 manual recovery, ownership change queued
1590056801 1720837 woke up
1590056358 1158590 password changed
1590056182 336754 woke up
1590056178 950934 woke up It gets daily updates. |
|
|
|
My 2020 offer is simple, and similar. First person who posts here, saying they want to and are able to:
1. Send me 3 pizzas tomorrow at around 4pm UTC (that's server time). I'll share an address; and
2. Pay in Bitcoin (I'll show you a provider that accepts);
will receive back from me the full amount paid + 0.005 BTC. (Your estimated costs will be around 0.0025 BTC, 0.003 BTC max) I'm surprised there are no takers yet. I can do this |
|
|
|
I think you may have to set up a separate set of funds for each time-frame as I have a feeling that wallets are swept clean when this process is done. You can use the same wallet, as long as it has multiple inputs and you use only one at a time. You can't create a Locktime transaction for funds that haven't arrived in a change address yet. |
|
|
|
Now, the https://posts.ninjastic.space has all* of Loyce's 2,5 million archive posts saved (*with the rare exception of a very few ones). Most of them have no title, but you can still search by topic id, content, author and date. Expect some graphic bugs since I wasn't planning on having that many data that early. And please be gentle with the database (text content takes some time and it's heavy work). I'm not sure if it's still loading or stuck, just searching for username "LoyceV" or Topic ID "1813624" keeps loading indefinitely. To raise the stakes a bit, I have much more posts, although it'll take a few more months to complete scraping. I expect to be done around August, so if you can handle a lot more data to search by then, you can have it all It's currently 11 GB using bzip2 compression.I didn't keep the original post dates for this though, but you can always get a raw estimate by scraping one in every 1000 posts. |
|
|
|
A user can have only airdropped merits but as long as they send out atleast one merit, they will appear in the list. Correct. |
|
|
|
Should be trivial if you have a working time machine like you claim... There's nothing trivial about getting 1.21 GW  I'm testing my new time machine |
|
|
|
My number: 50 My addy: bc1qpnj63tywx8qdxk3m4xng3v3llptxlvx0h8ghgv (this is a custodial Lightning Network wallet) SHA256 hash of predetermined number and salt is ABEF0055F85A7EE20D711E8C0E9455CBCEFE21C70125D15E285299C9C0C68A96 Quoting |
|
|
|
|
Show Posts
