0 Members and 1 Guest are viewing this topic.
If it's ok with them, maybe you could PM their contact info to me so I can chat with them about it? Thanx so much @emigalotti
Looks like we're not the only ones working on DDNS: http://what3words.com/examples/
When the populace is overrun by sheep that have been beat down their entire lives, they get excited when they see others persecution and support it wholeheartedly. Sad.
Let's see what action legislation might take .. at least for bitcoin you seemto be rather safe .. in Germany .. it is totally allowed to use here How about do some research first and no spread FUD?
Could Moonstone be blocked via dns?
Or via a specific port that's used by Moonstone? Maybe the type of technology/protocol/algo the wallet calls on?
Or its particular app name? Or where it is downloaded *from*? Or keywords it uses upon execution?
I'm not an ISP, but I can foresee them already thinking this stuff through. Ifthey were ordered to stop the Lime Wallet, Mycelium, Moonstone (or what haveyou), these (above) may be some ways they could give it a shot, no?
if I understand you right then what you fear is technically not possible
If they can't seize your crypto directly, maybe they could even block wallet apps. Related: http://www.coindesk.com/accenture-uk-government-should-regulate-bitcoin-wallets/
Next, banksters/govs will backdoor us by shaking hands with the UN and ISP's.
Question: DDNS is one thing, but is it possible for ISP's (or phone malware they inject) to block which types of apps you can download too?
Yes, I am Mike Ward. One of many, and I hope to get my name registered before others do! I missed mikeward.com by only a few weeks back in the 1990s, and the registrant of the same name has never let it expire I didn't want to make too big a deal out of that point about squatting, except to suggest that whatever you consider it to be (and definitions vary) there are easy ways to mitigate it to some extent. Main point was supposed to be that choosing the anti-squatting mechanism as the feature to distinguish this product from others does not provide incentive to the people registering the names. Again, people have long complained that all the .COMs are taken, then they proceed to register one anyway. Unique features like "instant registration" will make this more competitive IMHO. Better anti-squatting measures, not so much.There are plenty of good ideas about how to mitigate the big land grab that takes place if you offer all-you-can-reg domains for dirt cheap. Registry operators in the existing system are a good model to look at. They typically hold back the best names, and auction them off later, after the value has (hopefully) appreciated. People taking registered service marks like "Apple" is a slightly different issue, and is traditionally dealt with by offering pre-launch sunrise periods, where trademark holders can get first rights to register, as well as a binding arbitration process to challenge "bad faith" registrations. They work somewhat, but not so great, for various reasons.Holding back some names from general registration is an easy way to avoid most issues. Specifically for dealing with bulk registrations (like registering loads of common surnames) diminishing registration prices over an extended launch period help curb excess registrations, higher renewal fees discourage holding large numbers of names over time waiting for high resale pricesrequiring a certain amount of assets to be deposited or kept in an unspendable state for each domain registered might help (?)perhaps only the first "premium" domain name registration per user account is cheap (where premium is defined in some arbitrary way like length of string < 5 characters and it's not on reserved list) For strings beyond that length, no limit, but more premium strings cost more and more.And so on. There are probably as many ways to disincentivize bulk registrations as there are users on the forum. Some are easy to implement and fairly effective.
but I also believe that the emphasis on a complicated auction-style system to deter squatting was ill-advised. Not having a predictable annual cost is a negative for the business community,
Thanks Ken. Maybe that'll include some offering from this group - I hope so. So count me in for whatever, I'll be glad to do what I can. - Mike
I think you should contact EMC Dev (emercoin.com) to cooperate for decentralized DNS.
go for tesla http://cointelegraph.com/news/114149/adopting-the-chain-how-tesla-could-protect-its-website-and-its-cars
spent some time on skype with Oleg today, he is very open to my ddns working group. he is the emercoin dns core developer and "tech lead". he has developed a very nice solution for the squatting issue too. he wrote an open api that our ddns model can work with. emercoin.com/EmerCoin_and_OpenSSH is also a great resource. he has registered about 200 domains so far on their blockchain. opennic is working with emc as well. once i speak a bit more with Bas over at NXT i think ill start putting all this into a spreadsheet in google docs that we can collab on. by working together on ddns, we all win. as usual, ill keep the BitShares community updated. sorry for my grammar here, on tablet while my crappy wallet pc is upgrading to 0.9.0.
Quote from: namjar on April 24, 2015, 07:56:21 amI think you should contact EMC Dev (emercoin.com) to cooperate for decentralized DNS. will do. i'll contact them as well. i am working with Bas over at NXT on this too. this joint deal will be huge for BitShares, watch me.
Quote from: kenCode on April 23, 2015, 05:34:42 pmI've got a Dev connection at namecoin, will contact him now..Are you thinking of making some kind of joint project with Namecoin? If not, then I would like to suggest so and even sharedrop to namecoin holders (i actually don't own any). DNS would get more support, BitShares would get more exposure and create a good relationship with a new community, which I think we are in need since apparently people see us as a community that bashes other projects and that's it, that we're arrogant. That would fit in nice and we would only win with that situation imo
I've got a Dev connection at namecoin, will contact him now..
The UN could issue an order to shut down all crypto related websites or web wallets tomorrow.
Quote from: pc on April 04, 2015, 08:45:00 amBut you are right insofar as there doesn't seem to be any development on that front, and we should get this moving. What has become of Indolering's excellent proposal?At any rate I asked @indolering to comment on this thread to give us an update about launching his delegates.
But you are right insofar as there doesn't seem to be any development on that front, and we should get this moving. What has become of Indolering's excellent proposal?
I'm working to get him and a couple of his friends from namecoin to join us in a Mumble hangout soon. That is going on behind the scenes. They seemed interested, so we it is more likely than not it will happen.
v0.1 beta of the DNS can be something as simple as a taskbar widget that someone clicks, enters in a URL, it does a p2p query for the latest IP address for that site, and then displays an HTML link that the user clicks.This way, you don't have to have any browser extensions.You don't have to bind yourself to the dns resolver or network interfaceThis allows site names to map to ever changing IP addresses, from a p2p database. It's a very "lite" client, that doesn't need a huge download.Microsoft never shipped with utorrent or ICQ, but look how popular those were. A little taskbar widget for Windows could really work.v1 could be a browser pluginv2 could be something that binds to the network interface almost like hotspot shield does..By the way, if you expect the client to have to process regular BTS blocks, with all the other non-DNS traffic, I highly recommend against that. You need this to be as lean and mean as possible, as a separate dedicated sidechain.If you're worried about getting BTS to gain benefit from this, all you have to do is make registering names happen via BTS only.But clients need to do minimal processing in order to resolve a name. Right now, you type in a name and in milliseconds you get your answer from the root servers with only a less than 1 kb of traffic in either direction.That's going to be the hard part. Designing a dedicated blockchain that hardly ever hard forks that is simple and quick, and stores very little resources on the client so it can work on phones and other small devices.
IMO the DNS stuff should be done properly, and that takes time. If we rush out a half-baked solution we'll regret it later.But you are right insofar as there doesn't seem to be any development on that front, and we should get this moving. What has become of Indolering's excellent proposal?
Quote from: pc on April 04, 2015, 08:45:00 amIMO the DNS stuff should be done properly, and that takes time. If we rush out a half-baked solution we'll regret it later.But you are right insofar as there doesn't seem to be any development on that front, and we should get this moving. What has become of Indolering's excellent proposal?Talked to devs about this, and you are pretty much spot on. I think the intent is lay down some foundational work to leverage such as turing complete scripting to build DNS functionality correctly. Thom's point is also correct; figuring out a methodology that will be attractive- i.e. predictable, is the key to DNS. The auction system doesn't fulfill this as he pointed out.At any rate I asked @indolering to comment on this thread to give us an update about launching his delegates.
... the solution is a mater of vetting proposals and building consensus to implement the one chosen...
Those of you who know me, know how passionate I am about saving the Internet. Some warnings: Wikileaks Loses DNS Service, Supporters Spread Mirrors as 'Infowar' Continues http://techpresident.com/blog-entry/updated-wikileaks-loses-dns-service-supporters-spread-mirrors-infowar-continues What do UK and Iran have in common? Both want to outlaw encrypted apps http://www.theregister.co.uk/2015/01/12/iranuk_in_accord_as_pm_promises_to_block_encrypted_comms_after_election David Cameron wants to ban encrypted apps like iMessage and Whatsapp https://nakedsecurity.sophos.com/2015/01/14/david-cameron-wants-to-ban-encrypted-apps-like-imessage-and-whatsapp Russia (and Bangladesh, Vietnam, Iceland....) on blocking crypto-related websites: http://cointelegraph.com/news/113857/russias-bitcoin-ban-expected-in-august-expert-recommends-businesses-get-out NameCoin slips further, down to #15 on CMC today: http://coinmarketcap.com Our wallets (wallet.bitshares.org, moonstone, bitsharesblocks, metaexchange, etc) are at stake now, not just the web itself. Let's save ourselves first, then begin work on integrations with icann/iana/ietf, etc. My ideas: 1. Make a chrome browser extension (for now) that uses the proven BitShares Login (see below). 2. If the extension sees an address/url of "bts:web.kencode" it will check the routable location to that "child" (website). 2b. You could even have the website owner maintain their own json file w/routing keys/vals, ie: http://kencode.de/id/kenCode.json 3. If the extension sees "bts:kencode/approve" it will load up the local client, or the web wallet as a backup for votes. 4. If the extension sees "bts:web.kencode/approve" you could vote for a website's popularity, great for search algos. 5. If the extension sees "bts:chat.kencode" it would load up the user's chosen voip Dapp (like icq, firechat, tweets, skype). 6. If the extension sees "bts:mail.kencode/subject?'Here's my subject line'" it would load up the user's chosen email client. Once the extension has these basic abilities, then we could connect it to volunteer bridging nodes to ip4/ip6 tables. I will happily host the first few myself by purchasing a dedicated ip from my isp. I'll host my kencode website on a beaglebone black, or one of my raspi's. This way, you guys can verify routing and mapping to the "web" child account as seen in #2 and #4 above. Here's a list of people that I have seen in discussions regarding BitShares DNS, may be qualified: A. @indolering B. @toast C. @gamey (https://bitsharestalk.org/index.php?topic=12119.0;all) D. @testz (https://bitsharestalk.org/index.php?topic=12540.0;all) E. @bytemaster (http://bytemaster.bitshares.org/article/2014/12/22/BitShares-Login/) F. Am I missing anyone?? If this Poll is successful, I see no reason why we can't get the first extension up and running ASAP. The technology already exists. Think of how newsworthy this will be when released with 1.0. First Moonstone, then BitShares DNS! (the Darknet subreddit has become VERY active the last 6 months, and for good reason!)