How to ensure that we will never speak on the phone

I get an awful lot of phone calls. The majority are from people I don’t know. If I know or have a reasonable idea of who is calling, I will answer. Otherwise, it goes to voice mail.

If you truly have no desire to actually speak with me, call on a restricted number. This will firmly ensure that I will NEVER pick up. If you are truly determined to not to speak to me, follow up by not leaving a voicemail.

If you MUST reveal your (supposed) number, be sure it is one I don’t recognize and follow that up by not leaving a message in the (likely) event I don’t answer. I know the current trend is to spoof local numbers, so having three or four different (unrecognized) supposedly local numbers call in quick succession and never leaving a message is solid affirmation that I am on the right track in assuming you are a scammer. Just be aware that any given number suspected of being a scam or other nuisance call only works once. Then it gets blocked. While my block list is now several blocks long, I really don’t care. It has unlimited capacity and I get a warm, fuzzy feeling whenever my phone vibrates for 1/10 of a second, then goes silent.

Please keep those calls coming in. It really brings a smile to my face.

WordPress Critical Notice

I had my WordPress Dashboard popup and warn me I wasn’t using the latest version of Firefox!

OMG!!! That is absolutely correct! I am NOT running the latest version of Firefox. But I’m not running an outdated version, either.

In fact, I don’t even have Firefox installed! LOL! And my Waterfox (!!) reports it is up to date.

I guess it really doesn’t matter as my browser of choice is Chromium on Ubuntu…

 

Sphider 2.0.0 nearing release

Sphider 2.0.0 is under going final testing and will be released probably by mid-October.

Virtually every file has gone at least some alteration. The features of Sphider 2.0.0 are:
– Better page charset handling to ensure that the database receives only UTF-8 input. UTF-8 encodeing of web pages already in UTF-8 format is avoided to eliminate garbled entries.
– Phrase searches have been improved.
– This version is PHP 7.1 ready.
– Integrated indexing of images, with the option to NOT index images. An image search page is also provided.
– RSS content may also be indexed and searched.
– Jquery has been updated to a more recent version.
– While not fully PSR-2 compliant when it comes to PHP coding standards, the code is a LOT closer than it ever has been. This involved the renaming of many functions, the elimination of a few functions which were found to be obsolete (and thus, unused). Coding style had to be changed virtually every module. This is why so much code has been altered, affecting nearly every Sphider PHP code segment.
– The search page is integrated for legacy, RSS, and image searches. Knowing that RSS and images are something not every user will be interested in, an updated (as in 2.0.x compliant) version of the 1.6.x search page is provided. The revised 1.6.x search form, it will work fine with 2.0.x. It will need to be renamed to replace the provided search.php.

Also, finding that porting PDO to databases other than MySQL was messier than anticipated (too many DB specific requirements for each), Sphider 2.0.0 will actually have 4 flavors. The “kits” for PostgreSQL and SQLite were too cumbersome and confusing.
1) The legacy Sphider, using the MySQL database (or MariaDB) and using MySQLi and MySQLnd.
2) PDO Sphider, also using the MySQL database (or MariaDB), but using a PDO implementation (for installations lacking MySQLnd support).
3) PostgreSQL version using a PostgresSQL database and accessed via PDO,
4) SQLite version, using a SQLite database accessed via PDO.

All flavors are testing well and it seems no more coding changes will be needed, after working out some “peculiarities” for each. Now each version must have a final full set of operations performed to ensure everything works. This includes new installation via PHP script, installation using SQL queries, upgrade installation, adding sites, indexing sites, deleting sites, adding, editing, and deleting categories. Also the same is done for RSS indexing. The search functions need to be tested for various situations. We have found a few websites which have, uh…., what you might call “unusual” methods resulting in unusual problems. (Ever seen an image “alt” tag with text running in excess of 1000 characters? We have!)

Dream Chaser now another ISS supply option

The Russian Progress has always been a prime ISS cargo option. Europe for a time provided the ATV (Automated Transfer Vehicle) which flew 5 cargo missions to the ISS, the last being in July 2014.  Japan also has the H-II Transfer Vehicle, but this flies at the most maybe once per year.

Much more recent, and more frequent, are SpaceX’s Dragon and Orbital Science’s Cygnus cargo vehicles, which takes the load off the Progress.

Sierra Nevada, which once was a consideration for manned transport to the ISS with their Dream Chaser, now has a NASA contract for a cargo version of their Dream Chaser. The first two flights will be lofted by ULA in 2020 and 2021.

While Boeing and SpaceX won the nods from NASA for manned transport, Sierra Nevada continued on their own with Dream Chaser. Naturally, Sierra Nevada must now concentrate on the Dream Chaser Cargo System, I, for one,  am hoping the manned Dream Chaser stays alive and becomes a reality at some point in the future.

Face it… Dream Chaser is a beautiful craft, and the concept of gliding in for a landing at an airport near home is an improvement over a splashdown far out in the ocean or thumping down in some remote grassland.

Future considerations for Sphider (but not guarantees)

I’ve been giving thought to just what should come next for Sphider.

Integrating the Sphider Image Indexing functions with the main Sphider, thus making content and image indexing a single operation is a rather obvious improvement.

The ability to index and search RSS feeds would also be a nice addition. I actually have an alpha of this running on both Linux and Windows machines. Since the spidering operations can be done from a command prompt, a simple cron is keeping the feeds updated on the Linux box. The Windows task scheduler is being a bit more stubborn, mainly because of a pesky PHP error I haven’t solved yet. PHP is fine in a browser, but the command prompt is giving trouble. It works, but I keep getting an error that DEMANDS a response! I’ll figure it out.

Since searching for content is different from searching for images, which in turn is different than searching for RSS feeds, three different sets of search and results pages are needed. To a user, the only obvious difference is the search page, as the results portion is integrated. So I am giving thought to a possible “unified” search page with tabs so that the appropriate search form (and corresponding results) can be present to the user. This is not definite yet, just a thought.

These are all ideas for the future. For now, version 1.6 remains the latest. If the need arises, minor release improvements/fixes are not out of the question.

Anything you would like to see in the Spider of the future? Give me your ideas and … well, who knows? It might be a very good, very doable idea!

Sphider 1.6.0 Released

Sphider 1.6.0 and Sphider 1.6.0 PDO version have been released.

Also released is the Sphider Image Indexer, a companion add-on to Sphider allowing the user to index and search images from a website.

And finally, there is also a conversion kit which will allow the PDO version of Sphider to work with SQLite databases in place of MySQL.

Sphider 1.6 Release Status

The regular version of Sphider 1.6.0 and the associated Sphider Image Indexer are completed, tested, and ready to go. Since I want to release the PDO version in tandem, that is the only hold up.

The PDO version and associated Image Indexer are also essentially completed, but undergoing further testing due to some last minute code changes. These changes involve code portability between database types. The release, as usual, targets MySQL (and presumably, MariaDB). There will also be a small set of four replacement modules (install.php, database.php, db_main.php, and db_backup.php)  available targeting SQLite users! It is anticipated that a similar set will soon be introduced for PostgreSQL users. The power of PDO will finally come to be realized.

As soon as everything has been more thoroughly tested, the appropriate zips will be posted in the Downloads section.