Of Google, Bing, Yahoo, and DuckDuckGo, Google’s the only one not displaying my disqussearch.com on the first page on querying “disqus comment search” or “disqus search.”
On this, I commented
I thought that Google’s search results are supposed to “far exceed the rest”
Somebody else responded
I don’t think they do anymore. Search is a commodity and they have brand recognition, which is all they need.
But not in China, where they are banned, which means to use any of their services, I have to use a VPN. Just goes to show how more often than not, political power trumps everything.
Using https://wordpress.org/plugins/lj-xp/ I was able to do so not only for some individual entries (it auto cross posted categories too) but also for a bulk of my earliest entries (from back in 2017). However, the 2018 ones and 2019 ones didn’t get cross-posted. I got a timeout with Nginx 500. This was when I clicked on some Update options and cross post all older entries in the settings.
Great tool/plugin. Much appreciation to Stephanie Leary, and the other names involved in the project for their time and effort!
I had noticed before that LiveJournal was more “Russian” than usual. Only today did I find out that it’s actually owned by a Russian company, hosted in Russia.
How did I find out? Well, it occurred to me that I might want to back up this blog more. Fault tolerance, high availability, single point of failure (SPOF), blah blah blah all those distributed systems buzzwords. I’m just one person. I could suddenly end up gone. WordPress could also potentially forcibly shut down this site.
So I asked somebody to possibly replicate some of the stuff on here on Sina. I did make another WordPress under the suggestion that me and a few others create a joint blog, but nothing’s come out of that. So yes, another WordPress helps too, but that’s not as diverse. Ideally, make a github.io (I already have one, and have hardly anything on there) with version control and pull requests. I didn’t have the time/energy and plus there is value in concentrating and accumulating more into one place, as far as media goes.
Continue reading “What!? LiveJournal is actually owned by Russian company now? (and has been for a while)”
Thanks to Jesse Zhang (who I learned is a 2x MOSPer + Harvard CS 18 + interned at Google and Citadel) for making this very straightforward for me by writing and publishing the following document, which I easily found: https://hackernoon.com/how-to-set-up-https-for-your-domain-on-aws-8f771686603d.
I saw that he founded camelot.ai, a YC backed startup, which he advertised in that. Michael O Church hates YC and Paul Graham for classism, ageism, sexism, promoting founder-engineer divide, etc. I won’t really comment on that, have too little experience with them, but I guess I would naturally be suspicious of them.
Continue reading “Enabled HTTPS for disqussearch.com”
For those of you who don’t want to read this, I have my Disqus comment search deployed now, at disqussearch.com.
From now on, I’ll give an outline of my experience deploying my Disqus comment search web app.
I had deployed the Disqus comment search web service I developed on Heroku, with the endpoint being https://pacific-waters-11622.herokuapp.com. What I didn’t expect was to end up blocked on account verification (now I’m pretty sure it’s almost certainly not my problem, since a similar procedure has worked on others), especially given that Heroku is pretty large and established, now a Salesforce company.
So that led me to try AWS. I made an account (it’s kind of a shame that I never cared enough about software engineering to have already made one long ago) and with some looking up info online plus trial and error I got it deployed on Amazon Elastic Beanstalk. As for details, I developed this in Scala using Scalatra and when testing locally, it was powered by Jetty web server, which I ran in sbt. For Heroku all I had to do, after incorporating a
Continue reading “I finally used Docker and Amazon Elastic Beanstalk (to deploy Disqus comment search service)”
I used my Disqus comment search to get all of Ron Maimon’s comments on there. His username is “ronmaimon” as you can verify through https://disqus.com/by/ronmaimon/. For those of you who see this, make sure to be exact on username. So, if you search “ron maimon” (with a space) you will get back something like “No Disqus user with username ron maimon.” I will soon make it such that you can disregard capitalization, which means the system will detect for instance that RonMaimon matches to username ronmaimon.
This week I released a Disqus comment search now deployed at https://pacific-waters-11622.herokuapp.com/. It allows you to search comments of a specific user filtering by search terms. I thought that if I have the time and motivation, maybe you could commission me to create something similar for Unz Review. I know you have a search on there, but it neither works terribly well nor is it very visible. There is no easy way to get all comments of a user with say, 3000+ comments, and with my web service, I’ve downloaded all comments of Steve Hsu, Bob Sykes, and Godfree Roberts. Bob Sykes has 4000+ and Godfree has 3000+ iirc. They’re now on my site, much more visible than before.
Continue reading “Letter to Ron Unz (on his site and on Jews as a group)”
THIS HAS BEEN UPDATED. SEE https://gmachine1729.com/2019/04/28/disqus-comment-search-now-returns-results-in-real-time/.
https://pacific-waters-11622.herokuapp.com/ is the service endpoint.
I made this because I wanted to be able to search a user’s Disqus comments. On the Disqus site itself, for a user with a ton of comments, you have to keep scrolling down manually which is painful and takes too long. On the other hand, using this service I downloaded 4000+ comments of BobSykes in under 3 minutes (with a retry). By default, this search tool limits to searching 100 latest comments, which is basically guaranteed to take under 5 sec.
The released version is very minimal, much because I wanted to get this out ASAP, even if means not having a separate (more descriptive) domain name for it, which will come later (assuming I’m not too lazy).
Please forgive if this initial version has a few bugs. There is one in that if you’re trying to download a ton of comments (like 4000+) of a user, it might timeout on the first request. It did for me. But, the second time (after a refresh) it took under 20 seconds to download 4000+ comments. For those of you who are more technical, I plan to make this ajax-y to download asynchronously in batches of say around 100, sometime in the future (again assuming I don’t get too lazy).
You guys are welcome to provide me feedback via the following:
And feel free to share this, including openly on the internet!
Also, shouldn’t happen, but for now no guarantee that there won’t be an outage.