The weird port - '443' and SSL certificates

It is not a joke to have a whole community crapping over how their gem does not get downloaded or installed because of a 'https' issue at the server ! :)

 

And it is certainly not funny to have some other weirdos quickly pouncing on how Windows 10 installs flawlessly so that anti-Microsoft sentiments could be provoked, on Facebook (not on LinkedIn or in any professional forum) but singularly amiss in reporting their own issue of a port not being allowed access because they want to make money from websites which also make use of the same server ! Does the word 'hypocrisy' come to your mind?

And it is most certainly not funny, when you find the word 'hypocrite' hitting the news in the social media in a totally different context.

Such is how 'mass moronic' mentality is frequently manipulated to propagate moronity that makes no sense when seen in the 'correct' context but due to the 'symbolic' nutcases (the types that go 'it is like saying...' comparison makers) that create 'smoke' with their ignorant shouting of 'unrelated' issues, which is then taken by the 'inexperienced' nutcases as public opinion, interpolation of context happens and gets blown out of proportions for 'mass misrepresentation and misinterpretation'.

Anyway, to get to the SSL issue when installing rails - all you need to do is provide a fresh new certificate file because Rails it seems has its own mind when it comes to certificate issuing authority (CA) so simply obtain a .pem file and put it into your ruby installation folder that has the path -
~ rubygems\ssl_certs folder. To do this, follow these steps:

1. type 'gem which rubygems' in the command prompt to find the path of 'rubygems.rg'

once you obtain the path to the rg,

2. type 'start ... (... is the path to the rg file location)' and put your newly obtained .pem (certificate file) in the location.

Re-start rails and the SSL connection will be successful for Rails to download any new gems from the ruby server!

Another common error could be in the mySql installation - all these issues are specific to Windows and open source softwares not because of any problem with Windows (which could be hugely contested) but because of how the primary framework on Windows, the .Net framework, consumes third-party or open source software. 

This means that if you already have a .net connector for MySql then using the -d option with 'rails' will cause a problem because the service running MySql somehow 'expects' the old password associated with the connector, even if a new MySql instance has been configured! Best is to uninstall the connector and re-configure MySql before using it with rails.



Another common problem in Windows is that because the 'localhost' is usually configured with the default ip address set to some ASP.Net or Windows Web App Server, 'rails server' may return n ip address for a newly created website.

It becomes useful to know that the --binding option set to the default localhost address will allow the website access.

Ps: On re-check, without running any Windows local web app (which means no app server listening in on any ports), the default localhost IP gets used without the --binding option !

Almost like how Mozilla says "This is embarrassing!" for its own errors as if expecting me to think that I should be embarrassed and Moz is announcing it on my behalf ! :D Seriously !!
 

Dogmas and conventions

Conventions, when misinterpreted or driven by fear, vested interests or agendas as quick fixes, become dogmas celebrated by stereotyp-ism, politico and the disoriented.

Habits, too, get confused with conventions, often. For instance, many in India visit temples out of a habit while the generally stereotyped believe it to be a convention of the religiously inclined devotees.

It is a morning or an evening walk to the temple or a simple activity that conforms to stay in sync with the tradition as believed by the family or friends rather than be on the wrong side.

Next to religion, where dogmas persist as conventions in India, is in jobs.

One such dogma is to persist with the notion that "Quitting a job without a safe offer or Updating it as your status in social media is an act of stupidity that is not professional and it will be used to manipulate" is almost a protocol and is followed as a convention!!

Convention is "Update your status"; taking the updated status as a submission to slavery and therefore, welcoming jackass trading of pay packages is quite simply sheer lack of belief in one's own capabilities of judgement.

Another interesting dogma is an 'article of faith' (to use an expression used in a similar context in LinkedIn) that becomes dormant in practice due to extensive exposure to what is prevalent and popular and a "therefore, must be right" principle that 'attains' the status of a 'belief' due to irrational acceptance of distorted practices, attitudes, techniques and believing them to be conventions.

Conventions are usually that which conforms to universal acceptance, yes, but when followed impractically and based on irrational reliance on others as beacons to propel the self, result in dogmas, with the effect that irrational minds will most likely begin to become the influential agents in future outcomes because dogmas erode common sense.

Guidelines for Better Unit Tests

Guidelines for Better Unit Tests

Be the change that you want the world to be!

"True caller", the app, has a feature that fetches any saved name from the database and displays it for you if you enter a mobile number and somebody has saved the name using the True caller app.

So, before checking others' names in True Caller, check your own name to see how others searching your name may see it.

"Be the change that you want the world to be."

The name returned by true caller on my mobile number is this !!

And my other stolen sim number,