5-million things for bitcoin
An ongoing (and non-exhaustive) list of changes and improvements to Spendabit.
id
column was overflowing.currency parameter, paving
the way for our (long overdue) support for alt-crypto-coins
(e.g., BCH, ETH).<link/> tags referencing images.org.joda.time to java.time.CurrencyConverter objects functional (making for more
robust testing and easier future code changes in this department).BTC payments only).<link/> and <meta/> tags to our site header to
improve our mobile experience (e.g., “Apple touch” icon).POST requests.scala-uri library (which turned out
to require a lot more work than anticipated).maxQueueSize” for our crawler, as stop-gap measure
to prevent some large websites from causing memory-consumption problems.BTC price-lookup hook.og:image”, leading to our logo
showing up much better on the thumbnails used in recent versions of Firefox and
hopefully in various social networks as well.<meta/>-tag page descriptions.<meta/>-tag descriptions for
search-result pages.200.<h1> tags on search-result pages, in hopes of
improving SEO.Content-Length is explicitly specified as 0.<meta name=description />)
for Google and other search-engines to index, for search-result pages.40x response
would be considered “dead” even if the site's homepage yielded
a 40x response (when such a state of affairs indicates a broader, and
not-product-specific, problem).UPDATEs (and some INSERTs) were taking an exceptionally
disproportionate (long) amount of time to execute. (For those interested in the
intimate details of PostgreSQL, we turned off the FASTUPDATE index
setting.)POST requests without proper
parameters (usually intrusion-detection bots or the like).User-Agent string.COUNT database-queries when refreshing the search-cache for
some large result-sets, to avoid needless resource usage.<link rel=next /> and <link rel=prev />
for pagination of search results (which should help search-engines better understand
our site structure and hopefully improve SEO).BTC) for price
display — finally!logcheck utility to keep a closer eye on our log files,
so we can have a better “pulse” on our server/application.404 response for requests for non-existent
merchant profiles.