Structural Overhaul for Even More 🌞 and 🌈s

I made some changes that I think help modularize the codebase a little more and can allow for easier testing of the individual parts of the application ( which I haven't added ).

➡️ This is what I did.

I also detail some of the changes further in the commit details, but, I probably should've just broken them up into smaller commits for that branch. Oh well.

Small Confession & Thought

There's also some comments left in there that I will clean up in a little bit after posting this. Probably could even add some more documentation comments in yardoc style or something. Because that way it'll look better when it's published as a gem to rubygems.

Speaking of that...

💎 Let's Gemify Catphish

There's plenty of tutorials online for how to do this.

• If you want to do that: cool.
• If you don't want to: I can do that no problem.

Solving the Dependency Issues

Because some people have had problems with the other gems this application relies on not being on their system -- we should just manage that for them by bundling it up as a pretty gem.

The dependency specifications can be laid out simply in the catphish application gempsec ( which doesn't exist yet ) and that can be taken care of much simpler. And then hopefully that issue doesn't happen for anyone else -- like myself 😺 -- ever again.

🌈 Rainbow Option

I haven't added this yet. But, that'll be super easy to add.

When I give a domain like testme.com.tw the result is only top level main TLDs. Do you have any suggestion about it?

For example,

`./catphish.rb --no-logo -V -D testme.com.tw generate -A
Type Domain Punycode Status

Punycode ťȇsťmẹ.net xn--tstme-c6b.net Available
Homoglyphs testme.com none Available
Mirrorization testmme.net none Available
PrependOrAppend www-testme.net none Available`

I was curious to know which tool you used to create the logo. How did you create it?

Tool informs me that some domains are available even when they're not. See the screenshots.

@ring0lab
Hey, I would like to feature catphish on Null Byte, and hoped you could help clarify a few things.

The -A argument (which seems to be required while using the generate command) isn't mentioned in the --help menu. Are there other options which can be used with generate? If no, why require -A at all?

Punycode is the representation of Unicode in ASCII form, right? I previously thought homograph (or homoglyphs?) were the same as Punycode. It's unclear to me why both Punycode and Homoglyphs are in the "Type" column. So that I don't confuse your usage of the two terms in the article, can you try clarifying the differences?

Also, should the highlighted (in red) "Punycode" column actually be named "Unicode ASCII"?

It would be better if we have a gemfile or list of all the dependencies

Dockerfile fails to build.

Hello, when i'm trying to run the tool i'm getting this error message can you please assist?
10x

/usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in require': cannot load such file -- simpleidn (LoadError) from /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in require'
from catphish.rb:14:in `

I don't mind it all that much. But I think it could be a little more "friendly".

There's also been a little bit of talk on twitter about it; and I think we should take some of that constructive criticism and do something about it.

I opened this issue to document it and have an open discussion about it to help fix up the README all pretty like.

Ideas

I'm hoping current contributors ( and future contributors 😉 ) will add what they'd like to see included or be improved upon.

Some stuff I thought about to get the ball roll'n

• Logo?
• Explain Purpose / Typical Usage
• Improve Clarity of Method Behavior
• Explain Limitations
• Move changes to a changelog file of some sort?