Here are some that I've collected from various forums that are not on your list.
pvuif6nonbhj3o3r.onion
c5qvugpewwyyy5oz.onion
xqzfakpeuvrobvpj.onion
Maybe add to http://www.bitcoin.org/wiki/doku.php?id=74638_nodes or combine that wiki page with teh additions in forming a new wiki page with a more appropriate name? |
|
|
|
|
original post edited to include link to patch.
|
|
|
|
|
bitcoin2cash: "You could have easily parsed the block chain yourself and found an address that has a suitable balance."
Additionally, your very first post has offered a similar deal and you haven't established much of a reputation as a legitimate business as far as I see. Also, google results for the Bitcoin address do link to a Russian site and Russians... stereotypically scammalicious, imo.
There are some people that pursue an established sense of trust or naivety and "try" deals like these only to later learn their mistakes.
Additionally, there are some people that pursue an established sense of distrust or awareness and proclaim illegitimacy.
If you truly are legitimate entity then you will accept both negative and positive feedback and only reply on those that merit a response. To try to squander or deter negative feedback or review (even as a noncustomer) seems rather implicative of your intentions. A more friendly perspective would definitely help to establish a positive reputation.
Consider restaurant industry for example. Waiters and waitresses may have horrendously difficult, obnoxious, greedy, rude, etc customers, however they are still treated nicely as any other customer.
e.g. I may be horrendously difficult, obnoxious, etc, buuut, I may still potentially be a customer that will help yuor business to succeed. If you are legitimate, you will probably focus on efforts to encourage such business.
|
|
|
|
My wife rolls her eyes when I mention bitcoin..... Your wife is kyuuute:  |
|
|
|
He's offering a good deal in order to establish a good reputation at which point he can charge a premium. Also he can keep stocked on the cheap if anyone wants/needs to get cash in the mail for their bitcoins. 200BTC/1$ does seem extreme though. I'd be interested to know if you get any takers on that. As does Sell: For every 200 bitcoins sent to 1CRZpkKKAt7G5uiK4JPBjBJGnozgiatFAs you will receive $1.00 USD in cash by mail. considering: $0.0639 each for BTC200 ($12.78) at bcm:pp. Total amount for BTC200 is $12.78 Where are you located. I'll buy them.
However, I suspect you're trying to move the market with zero coins. This is a possibility. Perhaps they are trying to shape the market with this service, however, I am certain that since it requires mailing monies, that it will not succeed as well as mtgox or bitcoin market which use Internet-based monies and do not require any snail mailing. |
|
|
|
Just curious, why not use mtgox? You can sell 25k on there right now for more than .04
It is unlikely bitcoin2cash will establish a positive reputation from their efforts in this manner. Cash by mail could possibly become "lost" and therefore create profit for bitcoin2cash. Only a percentage of the incoming funds need to be "lost" in order to generate profit. e.g. the first us $1.00 sent to them will supposedly trigger bitcoin2cash to send 25btc. However, current market indicates: $0.06195 each for BTC25 ($1.54875) at mtg. Total cost for BTC25 is $1.54875 Therefore, in order for bitcoin2cash to afford sending 25btc, they will require at least $2.00 which will then produce an estimated $0.45 worth of profit. Therefore, one of the two "$1.00" payments received will be claimed as lost. I would claim it as lost if I were pursuing same scheme. |
|
|
|
|
I suggest that if you are concerned about what you say being associated with your identity than you should put forth the effort to conceal or make difficult/impossible to determine your identity and not require or expect others to do the work for you. Besides, if you already have said something that would affect you in some way, then regardless of the public logs, other privately established logs can be used and you will have no recourse.
It can be argued that a public log makes information finding easier, and yes, that's the point. Information wants to be free.
Previously I have quoted insightful commentary from others that had sparked further discussion amongst the forum community and possibly the rest of the world. The ideas/discussions that have been initially limited to the IRC community due to lack of replication throughout other communication models could be expanded to the web to provider others to express their insights, etc as well.
|
|
|
|
|
unu, fher, naq gura fbzrbar nccyl n fpevcg (ternfrzbaxrl?) gb ebg13 ntnva ^_^
|
|
|
|
|
I am uncertain what is necessary to protect against as I am still new to SELinux. However, if there is a kind of extra layer of protection that can be established, I would like to learn more about it and possibly help to establish it.
|
|
|
|
|
I will be moving over next few days and nullvoid.org and bitbot may be unavailable during this period. I will try to prepare availability as much as possible.
|
|
|
|
we [ought to] pay [for] relatively large pieces at once. But whom to pay then and how much? And when?
[...]
The only solution I see is to encrypt all chunks from each client with some key that only uploader knows.
When you seed on Bit Torrent today, you get no guarantee that the person you're sharing with will share with anyone else--yet the system works just fine. I think we can extend this hopeful principle to a payment system. Abby begins seeding a file to a swarm of two other people, Ben and Crissy. Abby's uses a BitCoin-enhanced Bit Torrent client which, when it makes the initial connection with a leech, sends a fresh Bit Coin address.[1] Ben doesn't use BitCoin, so his client ignores the extraneous BitCoin address and downloads like a regular leach. Crissy, on the other hand, also uses a BitCoin-enhanced client and she sets up her client to send 0.01 BTC for every MiB received. Her client notices Abby's BitCoin address and sends payments there in the ratio Crissy specified. After uploading her first MiB to Crissi, Abby's client notices the incoming payments and correctly attributes them to Crissy--and from then forward prioritizes uploads to Crissy. Now lets say another user enters the swarm--Daniel. Daniel uses a BitCoin-enhanced client too and he's in a big hurry to download the file, so he sets his client to pay 1 BTC for every MiB. Abby's client will soon notice Daniel's greater payments and will prioritize uploads to Daniel first and Crissy second; Crissy's client will also prioritize uploads to Daniel over Ben. In summary, BitCoin-enhanced Bit Torrent clients upload like normal Bit Torrent clients until they receive BTC; then they prioritize uploads to whichever client pays the best. How do they know who pays the best? They simply divide the total number of bytes uploaded to that person by the total number of BTC received from that person. (Later implementations may want to use a moving average to react quicker to changing conditions.) -Dave [1] The fresh BitCoin address is so the client can correctly attribute all incoming payments to their originator's Bit Torrent client. This is good idea. I suggest, however, writing plugins for existing Bittorrent clients rather than writing a new client or forking an existing client. |
|
|
|
|
or (c) public anonymous logging with Tor and nothing can stop it, so tough ^_^
Of course, if anyone does establish such a service on Tor I will probably be first to blame. I don't mind.
|
|
|
|
|
Like many open source developers who maintain their projects even ones as small as individual Drupal modules or similar, it appears that perhaps the open source version of their Bitcoin client will be unmaintained. Someone can pick up the slack, however, and if necessary create a fork.
Just as there was little effort previously, there is little effort now. It is up to the community's open source developers to pick up the slack, and if none of us are capable or willing, then other noncommunity members shall appear and join the community and perhaps they can contribute. Maybe even promoting or requesting assistance with this from the worldwide open source commuinity may be helpful?
|
|
|
|
I do not object to logging of #bitcoin-dev. In fact, sometimes I wish a real-time log was available when I get disconnected during a conversation. And sometimes it's nice to go back and read a prior conversation.
But I understand that some are uncomfortable with a log being kept, despite it being a public channel that anyone can secretly log anytime. So redacting those member's lines is a good compromise, as long as it's made obvious each line that was redacted. Don't show who's line it was; just indicate that someone unknown said something unknown, so there won't appear to be confusing one-sided conversations. It is fairly simple to have raw uncut logs and to present them with a script that handles censoring nicknames as desired. However, additionally, anyone else can anonymously host uncensored logs using tor and never reveal their identity. However, for a community-based effort as a kind of service simply to prepare previous discussions to be available, it should be fairly acceptable to censor a nickname, or possibly even to by default randomize all nicknames for the sake of anonymity for everyone. |
|
|
|
|
Show Posts
