Skip to main content

Renovation and a word about the name

After a ridiculously long hiatus, orsburn.net is back online.  While true it never went offline, the period of time between the last post and now means that it might as well have.  With the new release, it's probably a good opportunity to describe a little behind the combination of the name, what with both “orsburn” and “static content.”

At one point way back when the blog was conceived, the idea was to use the term “static content” as the name.  It was a sort of tongue-in-cheek expression hearkening back to the early days of the Web, when all web pages were updated manually.  Think of it as a sort of antithesis of the way the Web actually works today.  That is, where nearly 100% of the content on the Web is generated “on the fly” and from a host of sources.

So the question then becomes,”why not just staticcontent.com or something like that?”  The answer is two-fold.  Well one really, and this is it.  Domain name squatting.  The domain name staticcontent.com was already taken, as was staticcontent.net, but there was no website at either one.  It's true that there are other top-level domains that could have been used, but it boiled down to the fact that orsburn.net was already owned and wasn't being used for anything else anyway.  This is the pseudo second reason alluded to earlier, but is too cheesy to really count as a decision maker.  It was really just a sort of work-around.  The end result was a blog that is thought of as “Static Content” and is accessed via orsburn.net.  It's not ideal, but so far we're going with it like this.

Comments

Post a Comment

Popular posts from this blog

Remove control of Chrome being managed by organization on personal devices

Chrome may indicate that it's being managed by a user's organization. This warning is provided by the Chrome Policies feature of the browser. To know if an instance of Chrome is managed by an organization, there will be an entry at the bottom of the browser’s hamburger menu (three dot menu), on the right side of the browser window that reads, "Managed by your organization." This is likely due to an entry in the Chrome Policies listing, which can be found by loading this page in the browser: chrome://policy The policies listed in this section are stored in the computer's file system in one of the following locations as JSON files. /usr/share/chromium/policies/managed /usr/share/chromium/policies/recommended Remove the offending JSON files, and click the Reload policies button. The Managed by your organization entry in the browser menu should be gone. A notice like this on instances of Chrome for work, school, library, or other devices that belong to an organizati...
Post a Comment
Read more

Allow Windows authentication using SQL Server driver with DBeaver

DBeaver will allow Microsoft Windows single sign on access when connecting to Microsoft SQL Server using the SQL Server driver (rather than jTDS ).  From the driver properties settings, set the integratedSecurity flag to true . Open the Connection configuration panel and choose the Driver properties section. Set the integratedSecurity flag to true . A subtle, but important step is to not provide username and password credentials to the connection.
7 comments
Read more

Connecting to SQL Server with jTDS using Windows Authentication

UPDATE:   At one point the tip in this article to set the USENTLV2 flag to true was accurate, but it appears it is no longer necessary, at least as far as DBeaver 's use of the driver is concerned.  If it solves an authentication problem, then great.  The expectation is that, an update in one of the packages that make this sort of connection possible has resolved the issue that at one time made this flag necessary. Connecting to Microsoft SQL Server using jTDS with a username and password that's managed by the database manager is pretty straightforward.  It may become a little more problematic however, when trying to use Windows authentication when connecting from a Windows machine. Do not supply a username and password. Set the USENTLMV2 property to true. NOTE:   Step 1 assumes a connection being made from a Windows machine.  If the connection is being made from something else, user credentials may actually be necessary. If the connect...
7 comments
Read more