Tag Archives: tech

Can’tact me:

Posted by David Emeron on

Of late, I find myself contemplating leaving the comment section of this blog “wide open,” i.e. deigning not to require logins or even unique UIDs. Would anyone like to weigh in on this matter?

In addition, I have recently added a contact page; although wordpress is still the best way to get in touch with me. I check my email approximately once a month unless I am specifically expecting an email from someone, or for some reason. I have therefore listed such contact information in descending order of effectiveness. I have never, for example, even run a skype client under my publicly known name; and wordpress does not allow active skype URIs in any event. However, in the event that someone is feeling very, very lucky and happens to catch me in an especially amiable mood, I offer up my skype ID in the event that said individual should wish to dial me over and over until his fingers bleed.”

On an unrelated note, I believe the next pay service I may buy on wordpress by way of celebration of some goal achieved will be the “No Ad” service. Even though such ads are only presented on individual posts and only to logged-out users; still, unpredictable content rankles my aesthetic sense–such as it is.

A slight improvement to sequence displays:

Posted by David Emeron on

As I have been reviewing the site, I have been renaming my sequence tags to the actual names for the sequences in question.  I shall be moving the sequence links from a menu widget to a links widget.  Which shall give me a different set of options regarding the positioning i.e. the order of such links.

In addition, while I have not yet found a way to reverse the order of sequence posts so that they may read from the top down, I have discovered that inserting links of the form:

https://davidemeron.com/tag/the-rain/#post-3643

will start the reader at the bottom, and therefore at the first entry in the sequence.  This, at least, will allow the reader to scroll upward through the posts in date order–which, after all is the “normal” blogging order:  oldest at the bottom, newest at the top.  And perhaps, this is good enough.

Eureka!

Posted by David Emeron on

I think I finally managed to ferret out the form for postID as a REAL permalink  that will continue to work no matter what happens to the post or where it may be moved.

upon further examination…

It appears that

http://<domain>?p=PostIdNum

will in fact work. I must have been typing something incorrectly in my experiments. It took me a bit of redundant mucking about to discover this fact. The default behaviour of an independent wordpress site is a bit different, and I admit that when compared to my dearest one I am notoriously poor at doing research; unless it is the real kind wherein one actually does ones own discovery and experiments–which is what, in fact, I resorted to in this as well.

One can even add

&preview=true

to the end and use the same link before it is posted (and which will do no harm once the entry is live) making it

http://<domain>?p=<PostIdNum>&preview=true

In addition, one can add a bookmark in the form

#comment-<CommentIdNum>

with the dash instead of the equal sign followed by the PostId number, or any other bookmark

#<BookMarkId>

which exists or is allowed in the post, making it

http://<domain>?p=PostIdNum&preview=true#comment-CommentIdNum

This will… may… save me some effort although it is not all that difficult to create the unique tags I have been using. it tends though to bog down the whole process though. I wish the links would stick around after the draft is saved.

I am now investigating links of the same kind to pages. although this is not so important… and I have just now discovered that indeed this very same form works for pages. And in the case of wordpress blogs integrated with domain names, the method works as well. One can use both ones registered domain and the original wordpress blog name. Both will work. Hmm. Well, give me good old fashioned scientific method any old day.

The fact is that once one clicks “save” (verses the auto-save that happens automatically in the beginning) one must then construct the link oneself (from, for example, by editing the “Get Shortlink” link, or by copying the “Preview” link before one makes the post live.)  Evidently once one changes or alter the status of the publishing date wherein it no longer reads “Publish immediately” this link will no longer be listed and will instead be replaced by the default “permalink” which contains a directory structure involving the date of publication.

This post, for example can be accessed by using the following:

Try them for yourself!  I have tested them both logged in and logged out and they seem to function properly on the handful of machines I have surrounding me.

The downside of all this is that there appears to be no way for a non blog member to discern the PostIdNum.  It can only be seen in the dashboard area before one saves for the first time.  After that it can be unmangled from the “edit” links, but only if one is able to access these, therefore if one wants people to use these links, they must be provided in some way.  Which means that I should probably create some templates for this.

Related articles

The Viking Situation:

Posted by David Emeron on

Herein I attempt to link all the relevant posts wherever they may be:

  1. First: the location of the original exchange:  February 7th, 2013 at 4:03 am
  2. Next, the whole enchilada:  My first…
  3. Next, the introduction which you (kanzensakura) stumbled upon:  Where is Waldo?
  4. And the sonnet I wrote inspired by the whole exchange:  Sonnet:
  5. Finally, a note about the piece–titled referent to my research on the subject:   FYI

Now, after and, I think during the hole affair, there were even some very peculiar emails exchanged.  They seemed to appear in great heaps.  Those, however, I did not save, and had I saved them, I would not publish them here for ethical reasons–even if I chose to redact the identity of the author of these.

Related articles (only the first two are actually related, heh)

The Big Merge…

Posted by David Emeron on

…seemed to go off without a hitch.  My final step this evening has been to remove all the post from “reflections.”  I did have to modify a few elements.  Some menu items were duplicated, as were all three blogs made to look similar.  It appears that I could very well merge all three into one.  The same effect as before could well be accomplished with one blog and three distinct categories.  I believe I more fully understand the issue of “tags” vs. “categories” and would now have little trouble using both to accomplish this.
Continue reading →

Blessed Silence…

Posted by David Emeron on

If one finds one cannot endure the lure of the “little orange thingy” which informs one of new “likes/comments/follows,” &c, then the following solution should be undertaken:

  1. Log out of your account
  2. Create another user i.e. “davidemeronII”
  3. Set its primary blog to Private
  4. change the user’s display name to something like “REMOVE THIS NOW”
  5. Log out of this account and log back into your “real” account
  6. From each blog you use, invite your user (i.e. “davidemeronII”) to be an EDITOR.
  7. Log out and log back into your new account
  8. Check the email for the new account and accept all invitations you sent.
  9. Now, you can edit drafts already posted and nothing will change
  10. It is best to put the Author widget toward the top of the “Add New Post” page.
  11. Because it will default to user “REMOVE THIS NOW”
  12. Never post as this user
  13. Never comment as this user
  14. If you do, edit the comments or posts to reflect your normal username i.e.  “David Emeron”
  15. You will never receive any notifications while logged in this way.
  16. You can answer comments on this account, without affecting this
  17. IF you always remember to change the user when you are posting.
  18. SO IT IS BEST NOT TO DO THIS.
  19. When you are ready for the cacauphany of comments, likes, follows, &c, just:
  20. LOG OUT, and log back into your regular user account, and do whatever you wish.

(This post was published in this manner, my “little grey thingy” never changed into a “little orange thingy.”)

This is much better, and is far less nerdy, than using script blocking techniques.  I would much prefer that wordpress allow you to turn all notification OFF, but, until they do, this works perfectly.