So, I got paid today. Nothing special, happens every two weeks. But Today I decided to give cloud mining a try. See, since 2008 we’ve seen a new type of currency propagating across the internet. Digital Currencies that are decentralized, and not bound by the good faith and credit of any one government. The first of these was Bitcoin, which is still the most popular and recently had a hard fork with Bitcoin Cash due to a debate on scalability.
Bitcoin is not the only digital currency though, you have others like LiteCoin and Etherium, both of which are supported on the bitcoin exchange wallet service Coinbase.com.
Now, I found a cloud based mining company that takes its maintenance out in bitcoins you mine off their hardware. Not so bad when you consider how much it takes to get started. I gave then $30USD/0.01 BTC and started up. Now, I won’t know exactly how effective this is until the first payout, so I can’t go into it now, but if it’s not all I lost is $30USD.
But let’s assume that I make back that $30USD. Then proceed to let the mining go on to make a bit more. From what I can tell for tax purposes these are all covered under the same regulations as any currency trading. So, I’m going to have to put back about 50% of anything I make for Capital Gains Taxes next year.
Still, 50% of something is better than all of nothing.
I’m thinking of reinvesting into the process as I make more BTC. I will take the first 0.01BTC after my tax savings are considered and get started on Ethereum mining on the same services. Cost about $29.99USD for 2 years. I can improve on that over time hopefully as I add power to the mix.
But what does this all mean in the long term? I’m assuming for tax purposes that all of this is covered under US Tax law, and that saving back 50% of it should be sufficient. To my knowledge no one pays more than 50% taxes on IRS. Any better information would be appreciated. But even then, all my digital currency at the end of the year will need to be dealt with in taxes as US Dollars. Not a bad thing, or a good thing, just the currency of the country I’m a citizen of.
I’m all for anyone who has knowledge into this world I’m stepping into.
I’m a member of the Reddit group r/hfy and lately we’ve been a bit concerned for how things have been going. So one of the group mods is creating a separate website. I’ve used Drupal a lot so I’m consulting with him on it, going to see what I can do to help the process. Of course that leads me to ponder the general truth of how we share what we know. Our experiences and our skills we haven’t been trained in, that we just pick up as we go along.
It’s interesting to note that he was starting things in a similar way as I was, but I already have hit several pitfalls that I can hopefully prevent him from falling into. Future proofing the layout and site structure for the upcoming Drupal 8, keeping the number of modules down while delivering the best experience possible, things of that nature.
Now, I’ve had a few things setup here over time that I’ve tried sharing out before. Its lead me to certain opinions of things. First you should always try and pick the right tool for the right jobs. A big community and content display system defiantly qualifies for a Drupal Build. I use WordPress for this page as it’s just me and no one else, but I wouldn’t trust it for Fanbards. And if anyone ever asks me I’ll tell them that exactly.
We all learn things over time. We gain skills, abilities, and even tricks that help us out for procedures we try and create. We also, can and always have, share these tricks with others when needed. Its how things have been passed down for Centuries, from Master to Apprentice. We document them as SOP’s, Rules of Thumb, Tips and Tricks, all of those things. You find it all over forums and help pages. It’s almost as if it’s a need for us all. If you have a problem, you ask for help. When you figure out a problem you share your solution for those who might benefit. It doesn’t always work that way, and there may in fact be folks who don’t share their knowledge, but it’s very few people these days.
I’ve started using word processors to create all my articles instead of just writing in the cms I’m in. I get the benefits of Spell check and all of the other things that come with using a full on word proc. I didn’t before, but I do now. I got some help from the guys in the Drupal group on LinkedIn on how I should lay out a how-to article with all of my information. That was interesting to say the least.
The point is, we try and help where we can, and share our knowledge to help those around us. I think it’s basically something we just do. We only horde knowledge when it’s to protect ourselves, our groups, and to have some advantage over adversaries intending us harm. Within our communities we are free and clear to give everything we know away.
I’ve been thinking about site building for a while now. Site building isn’t like development to me, in that development you are really just working with PHP code, creating modules, sites, scripts, and things of that nature. You are going from the ground up in code to a finished product. Then you have building, which to me at least implies you are mostly if not exclusively finding modules and using scripts someone else maintains. This isn’t about the benefits or drawbacks of either, just defining our terms for this discussion.
When the internet first started becoming a thing for the general public we had sites like geocities. You could go and build a simple html website there for free, and not really have any issues. It was ok. I had a simple page there with gifs and the like. I used Mozilla Composer to build it first. Then I started learning some simple html code. Things have sort of spiraled out of control since and now I have to basically use a project to do anything. That is frankly not too big an issue as an open project allows for updating to code to be handled more easily if others are doing the backend work for you. I get to focus on the content and presentation.
But that’s really interesting in a way. We’ve seen it become much easier over time to create your own space on the internet. You can do something simple like just use a Facebook profile as your personal page, or create a group, send out short tweets with links to Youtube videos. You can even just get easy to setup blogs from wordpress.org. Structurally at least creating a personal presence on the web has become extremely simple.
So while I could probably save cash I still do things with an eye towards this idea. I like not focusing on the code and focusing more on the layout and the content. It’s what I do mostly so the question becomes what is best for what you are trying to do?
For an archive like Fanbards.net you can either just do a straight archive using something like eFiction.org’s archive software. You can use Drupal as well to construct things the way you want. I’m hopefully done with structure for a while until Drupal 8 comes out. Or you can create a WordPress Blog, generate pages and things of that nature to build things up slowly. It works, and works greate for a personal setup.
But that’s structure, in the end it’s what you put out there that defines your precense. I run five web addresses. Four of which are all part of the same website. It’s basically a separation of interests. I’m not sure if I will eventually be able to make anything of all these interests but I try. And that is something a lot of people do. Try to provide an interesting precense on the web. We have Video Blogs, and Kindle Books, and all sort of things that make it easier for the common person to do what needed an entire company of people to do only twenty years ago. And it’s only going to get easier.
I think over time we will see more of a simplification and consolidation of things. Maybe having more interlinks between profiles on different sites, posting things we post on fictionpress.net to our Facebook Pages, things of that nature.
So I caved after years of hearing how I should be using Entity References over Book module for all my stories and such in the Fanbards.net archive. Book module provided built in navigation and organization of structured content and was easily handled for display, but was a pain to make easy for folk to add to.
In order to make things look good you had to add children to books. What you see above is what a Top-Level page in a book looks like. I personally have my Top-Level pages as a completely separate content type in Drupal. That’s my opinion at least that something like that should be unique, and contain all your book meta-data depending on what your books and groupings are based upon. Now, in Drupal by default if you are going to add a child-page to a Book outline you have to select said outline on the add node page you are saving at that time.
Notice the default setting for Weight. That is always 0, and by default the Drupal Book module orders all your child pages alphabetically. That can lead to ordering issues if you don’t plan for it. So you have to go to the Outline tab for that book and reorder all your chapters there.
Now, if it was just me working all of this that would be fine. Find what I need, add it to the story, order it properly. Simple, easy, ok. But it’s not just me. It’s me and anyone else who wants to post to the page. So I had to work with that, find a module that would give me access to certain information in Views, and build certain structures. After a bunch of Views and Rules I managed to create something for the average user that worked. Not the best way but it worked.
This is a view of story pages from Fanbards.net. It shows all story pages that share the same author, and that author is the person that is currently logged in and requesting the view.
That was how I got a listing of stories of all users. Editing however had to be done with links that took a person away from the page for everything, even just viewing the chapters in a story. When I tried to fix that issue with things like Views Megarows all I’d get were error 200’s, rules wasn’t letting me redirect easily at all, and a ton of other issues that major modules had to book module. And never bothered to fix.
I also had to create a drop down menu showing all the chapters in a story like every other archive site has so a user could just jump chapters if they wanted. That required me to install a completely new module to pull that information into Views. It provided a drop down menu, and I was happy with it. Even wrote up an article on here for it.
That being said everything I did before had to go out the window due to switching over to using Entity References instead. First a note on what an Entity is and why you would want to reference it. As it relates to Drupal at least, an Entity is any piece of information, taxonomy, content nodes, files, things of that nature. You would reference such things when creating something like a Group or an image gallery. Organic Groups and Node Gallery both are dependent on Entity References. It’s how they associate Group Content with the Group you are posting in, or the Gallery you are adding an Image to.
So I set up my regular content types and this time added an Entity Reference field on the Chapter Type that references Story Pages. I also added a field that was specificly meant to be an integer for Chapter Number as it relates to ordering. It defaults to an autocomplete field that allows you to add to every story page in the site. While that is not any different from a book outline tab in a book module outline, the difference is I can switch that to reference a specific View display that will ONLY show stories created by the person who is creating the chapter.
It’s not active at the moment as we go through and edit all the chapter nodes to connect to story nodes, but it is there. And After finding a documented how to article on Drupal.org that showed me how I was able to recreate the basic chapter listing block that books had. So there was that.
Recreating navigation in a story however was a big pain. I managed to recreate the Chapter Jump Menu easily enough once I figured out how to get it to display all the chapters and links, but I had a bit of a harder time getting it to do paging through chapters as a navigational link. I found a module called FreePager and after fighting it for a week was able to, with help, recreate next previous paging in a story. So there is that.
I also was able to finally create a Megarow View table for User Content Management for Stories. So when you click edit chapters it drops down a display that shows every chapter in the book. You can’t do dragable sorting anymore, but that seems less important. The real important thing is that now you can do some editing of your chapters without having to go through three different pages.
That pretty much sums it all up. Everything can be accomplished with Entity References, Views, and an extra module or two. What worked for me may not in fact work for you. You may in fact find better ways to accomplish this. If this helps you figure out things then let me know. This is in no way a how to, just a description of what I’ve done.
I started working my twitter displays for the site, trying to get everything to work properly and display the feeds for all the sites. Then as I’m created content panes for the Fanbards/Darkscribes/Evaficsnet/Lemontastica twitter accounts I had a thought. Why the heck should I be displaying those? I need the linked up to the Twitter Module, but I don’t really need to display the stuff I’m tweeting from there. I’m just doing things that would normally show up as an update. So I thought on it and decided something else might be a good idea.
So I setup a block to show all the twitter accounts I have setup to follow on the page. That way every time a cron run goes the site would pull in that information. The timeline gets updated and it keeps with the Twitter display requirements while keeping with the sites primary display style. I also had the idea that every time the cron is run that a story article or forum topic would be randomly tweeted to the four twitter accounts I have. That way more information could be gotten out while keeping things simple.
It’s an idea I’ll be looking into more readily as I go.
I’ve been rebuild Fanbards.net/Darkscribes.org and have gotten to the point where I needed to work on presentation. Drupal guys and others recommend using radix, which is a fancy shiny theme. It is however difficult for me to get my head around. I already have to add css in in order to properly integrate the dashboard.
I have been using Footheme on the page for my theming before now. It’s simple, easy to setup a usable Adaptive Theme subtheme based on Corolla or Pixture Reloaded, and looks good enough.
Bootstrap, Twitter’s contribution to the internet, looks really fancy and can be used by anything. But it’s still difficult to get things working at times. So I’m going to stick with the easy way for now. It gets the job done, and I’m not paid so I don’t have to make everything all glossy.
So I’m developing the sites again, trying to figure out what broke the story creation process on the original site, and I get to thinking. As I’m basically rebuilding from scratch trying to find the problem here I was wondering what I can do to make things better. This goes through from content viewing to content creation. It’s difficult though as I can’t do much as I wanted. I’m just trying to get through it all.
I’ve been trying for instance to do from scratch what I used modules for in some cases before. Trying to limit the number of modules needed SOUNDS like a GREAT idea. Use some panels and views and you SHOULD be able to pull it off. What’s not to improve on with that sort of thing. But the thing is that I’m not a coder, and I’m not sure how to go about recreating functionality that a module already makes use of.
There are some that will always say that you need to minimize the number of modules used. The more you use the slower things get. And there is a good logic behind this. Fewer modules means fewer resources. But at the end of the day you are really trying to prototype, deploy and maintain as easily as possible. For a lot of us, myself included, that means you have to look at things from the perspective of what you can do.
Taking that into account and looking at it fact is that the basic site needs really only need a few modules to run in general. The rest of the modules are just integration of other items and the like. Things like CKEditor, Fivestar voting, Disqus comments, and Twitter/Facebook integration are all just modules that really you don’t do anything but set and forget hopefully. They can’t be modifier and frankly it’s best to just use an available module for them.
Everything else really comes down to a couple of modules, views and panels. Everything else is for all intents and purposes an extension of these modules. When you figure that, it becomes less about finding more modules and more about creating more views. That way things turn out better.
ruSo I have been rebuilding all of my sites since I got hit by an exploit in Drupal. I’m still rebuilding the DS sites in whole at the moment due to this,. Unfortunately had to finally accept that my preferred method of keeping stories together was just going to fail forever so I have stopped using the core Book module. I’m having to use Entity References in order to pull off what I was doing with ease using Book Module, but will hopefully get other things I couldn’t do done much easier.
Hopefully, I’m still trying to reach feature parity with Book module and the old DS user content management features.
This also requires work towards fixing certain issues with the site over time I hope. An associate has agreed to help on Editing and fixing connections, and I could use some help from anyone willing to take on the mark of Editor.
This allows me some time to work on the structures as well as the content as I go along. I just don’t know what to do.
I’ve decided to try and keep this page running on WordPress while I’ll keep Fanbards/Darkscribes on Drupal. The two different specs will make it a bit easier to keep up with differences, and keep me focused. I hope at least.
This also means that I’m working towards trying and separating my Regular identity from my fandom one slightly. I’ve always tried to keep this separate, but there is still a bit of similarity in there. This should make things a bit more unique.
That being said, I have to wonder if there is a cause to NOT have a separate identity for fandom related activities as opposed to maintaining them. Facebook doesn’t allow you to have a secret identity, and as much as someone may like to think otherwise, having separate accounts is meaningless if you have your images posted all over the place.
I’ll be adding more real content to this page here soon. And I’ll be working towards improving current displays. More work.
One of the things I enjoy about the Drupal Book module is that it is a built in way to generate hierarchical content for a site. This can be anything from a work of fiction with multiple chapters to a handbook how-to. The built in navigation features are extremely simple to use for the visiting user and frankly make it easier to get them where they need to be. However there are some ways that are easier then others to navigate. One is to have a full listing of the chapters in a sidebar of the page. Personally I don’t quite like that approach in some cases.
On pretty much every fanfiction site I go to there is always a drop down menu to allow the user to go to the chapter of their choice. This allows the user to quickly select what chapter they want to go to without having to back track to a chapter listing. Now, whether this is more efficient then just having your table of contents along the side of the screen or not I could tell you. However it is expected in this day and age that it be there. So I had to figure out how to do this with Drupal. Fortunately after a bit I figured it out.
First off you more then likely already have views installed. It’s such a necessary module it’s been included as a core module in Drupal 8. IT allows you to create pages and listing of content easily and handles many of the use cases your average website will need. It also integrates rather seamlessly into Panels, allowing you to add views pages or create view panes. So first off you want to create a brand new view. It’s going to be a content view of the content type you use as pages in a book. I personally have two separate content types as part of my books. One type for the meta-data: title, summary, genre, series, rating. The second content type is the chapter or the real content of the book. I call the second type chapter so that is how I will refer to things from here on. You don’t need a full page so don’t create a page, you can choose a block or leave the basic two empty then once in editing create a content pane.
Now there is a module you will need to install called menu node API. This module provides you with an API, a module for setting access permissions, and the important part for this a node integrating it all with views. We will need this as for all intents and purposes a book module is just a menu of content and that menu is important for this block. Also, you should have pathauto installed so you can set your custom URL paths for your child page content type.
Having these modules installed first go to admin/config/search/path/patterns and find the entry for our chapter page. Now pathauto uses tokens for a good portion of things. My pathauto entries for my Story page, the front page for all my books is stories/[node:book:mlid] so that the mlid of this page is the same even when looking at the parent in your URL. My chapter page path is stories/[node:book:root:mlid]/[node:nid]. This provides some URL consistency so that the parent id is always the same no matter where in the book you are. Where I put [node:nid] you can chose what you want there instead. However, the [node:book:root:mlid] is essential to what we are discussing. Delete and Bulk Update your content URLs using the new patterns.
Now you have your basic content pane and your URL alias default. The first thing you need is to add a contextual filter. You should find the Menu: Parent Menu Link ID entry in the contextual filters and select that. When in settings, and this is how I did it if you know a better way then please share, under “When filter is not available” select provide default value and set that to Raw Value from URL. You will then need to set the path component to read for this filter. That would be where in your alias the menu link id of the book is located. In my URL, stories/[node:book:root:mlid]/[node:nid], that would put the value you want as the second part of the path. Always remember that it’s position in the URL is relative to the end of your domain address, so which value in between / it is. For us that sets the value at 2. Then click the check box for use alias as the system path will NOT have this in there. Under the entries for when a default value r the filter is available I set it for a basic validation and to hide the view if it doesn’t.
Now go to your format and set it for jump menu. And then make sure your show entry is set for fields. You will need four fields here. The first field is the title of the chapter. That is going to be your drop menus human readable entry. The second field is the parent menu link id. Set it to be excluded from display as you do NOT need it visible to the user. You will also need to add the node nid. This also should be set to exclude from display. Your forth field is the actual link that will be constructed. Add the Content:Link field, and once again click the exclude from display box. Go to Rewrite Results and select rewrite output of this field. Your entry should be similar to stories/[plid]/[nid] where the [plid] and [nid] fields are the values provided by the second and third fields.
Now go to your settings for the Jump Menu format. You need to set the link field as being Content:Link so that it will consider that as the internal link to send your user to. I personally hide the go button and set my choose text to -Chapter- however you can leave Go visible and modify the text of it to your preference.
Go to your preview area and enter the parent menu link id of one of your books to test. What you should see is a basic drop down menu of all chapters that are a part of that book. Save this and then just place the view pane in a panel page modifying your chapter content type. There you go, and easy to use chapter jump menu for the users on your site. There may be a more efficient and easier way to do this. This is just what worked for me. If you have better ideas or improvements please, leave a comment and let me know what you think would be better. I’m always open to more improvement.