#IndieWeb Updates For December 6th

as a citizen, I want to inform everyone of a couple of things that are happening based on recent happenings here in the community, so a huge thank you to everyone for putting up with this. In short, here we go

Change In Domain from .net to .org

In light of the recent change with PIR, and after watching several members of our community, I have decided to follow a couple of examples. The external domain will now have a .org TLD. .net will be my internal active Directory domain, which I will elaborate on in another post for another day.

With A New server Comes More Service Opportunities

I just recently bought a R620 (I have a nice picture of her in a previous post that a friend of mine took during the system building phase), and she has made many things that I have wanted to pursue for a very long time actually become possible. Very shortly, probably this coming weekend, I will be migrating all of my content off of my existing shared Windows hosting plan (hats off to Joe Davis from I7Media, and onto a server running on my beautiful Dell (for those who didn’t remember it, her name’s Dianda.) But that certainly isn’t all. My second goal with this new environment is to also assist some of the IndieWeb developers who have instances running of software, and so far there’s is the only instance. I will be running a Monocle and an Aperture instance, in hopes that the new social web will have greater chances to flourish. In addition, a public Friendica instance will also be available for Indiewebbers, technologists, and just great people in general for those who need a break from the annoyances of the Algorithm. I will decide on other public instances of things providing resources allow, so more updates to come on that. All for now.

Until next time.

IndieWeb Part 4: Cleaning Up

During the past few days, I have noticed some things that need to be looked into up here in terms of IndieWeb functionality. Not sure if anyone else has noticed, and not sure whether this issue is with WordPress itself or with the third-party IndieAuth enabled services I have connected, but either way, I am going to attempt to assist the IndieWeb community by finding out and potentially fixing what I can. I will be honest and admit my very limited knowledge of PHP, however, it is a seemingly simple language to pick up (if others disagree, please discuss in comments because I want to hear!) so providing I can keep my focus in one place (though I won’t be the first to state that is oftentimes more difficult for me than not), I might be able to fix a plugin or two by the end of 2019 or the beginning of 2020 at the latest.

Current Situation With This Site

at the moment, I seem to be encountering an issue with my micropub endpoint where it is displaying a 500 error if posting content from third party applications. I have not touched anything in the configuration settings for the plugin, so if anyone has any ideas as to what to look for while troubleshooting, that would be appreciated. Noticed this yesterday or the day before that while attempting to compose a reply via Quill, which failed. The odd thing? My text-enabled check ins seem to be working just fine when posting from Swarm, so not sure what the difference is. Both services, at least to my knowledge, are running on the same infrastructure. I will provide updates for you if I find out anything interesting. I am sure I will at this point.

Updates on where I’ve Been

The past few months have been … interesting to put it lightly . While the circumstances are more than I want to go into on this blog, I will certainly tell you that it has not been a walk in the park.
In Light Of Recent Events

During this recent period, I have been considering a couple of ideas regarding this domain. In the not too distant future, there will be several services running off of this domain; a known site, for the purposes of experimentation and development while attempting to learn the PHP and C# languages. I need something valid that I can practice concepts.
I will also have both a Friendica and a nextCloud instance, both as proofs of concept as well as functionality. RSS and other social feed functions will be handled by a self hosted Aperture instance. We need more of them out there, considering right now, as far as I can tell, only one that exists is the developer’s own. In order for the IndieWeb to thrive, everyone needs to do their part. I will do mine.
Dianda Comes
What I did not yet mention in the previous paragraphs is the fact that all of this will be hosted on a new personal server; getting a Dell PowerEdge R620 from the secondhand market. For those of you who kno me, her name’s Dianda. I will keep everyone posted as new developments appear.

IndieWeb Journey Part 3: Fooling With Themes

This will be a new experience for me; looks like in order to get everything to work as beautifully as I would like, I’m going to have to dabble with CSS, which should be fun. I’ve switched things up just a little bit, swapping Autonomie for IW26, both of which are respectable IndieWeb compatible themes, so thanks David Shanske for the inspiration.

Colors are still a work in progress, so keep that in mind if you see the webscape changing a bit more than normal over the course of the next few days. My goal is to find a means of getting all of the colors to match up to what is in my head, (sort of hard to do when color schemes are visible in one’s mind, but the eyes are often not on par, you know, side effect of being blind?) but look for red/blue variants, considering those are my two favourites. I’ll keep everybody updated as the times go on, so, stay tuned

My Indieweb Journey Part 2: Working On Finalizing Webmentions And Responses

I’ll say. this journey has been interesting, to say the least. For the most part, my site has been active consistently for several months, so that’s good. What still doesn’t feel verry consistent is the responses coming from outside. I still find that mentions from Twitterr are flaky, while check-ins from Swarm do show up, though the awarded coins do not. Like other webmentions, I have not been able to detect the discrepancy. I’ll be keeping you updated though once new information or developments come in. It’s been a learning experience so far.

Server and Workstation Updates: Part 1

This week started with a day off for Memorial Day (I don’t normally get that day off in light of the fact my service desk position is technically a 24-hour position, and lately, I’ve been slotted to work for most of the Monday holidays that have so far occurred this year), so that was definitely a treat for a change. Arrived back from NH to MA fairly early in the morning, which was also nice, since it gave me a chance to be more productive than I’ve been at home for the past few weeks, it seems. Read on to find out why …


Networking Upgrades and More


I decided a while ago that I would upgrade my technological environment at home, beginning with a desktop computer (more posts about it to come) and after doing some reading, I finally concluded that the best option for me at the moment in the server department would be to replace the motherboard on my existing PowerEdge T110. For those who don’t know, you can actually replace T110 components with those belonging to the next generation, which is the T110 II, which gives a definite improvement in performance, and of course, more memory. I plan to upgrade mine eventually to its full 32 gigabytes of RAM.

The plan is in the long run to have two servers, one acting as the core of the production network, and then the other, acting as a lab unit (though both of them will be on at all times). Not sure what the second unit will be, but ideally, possibly a R620 or R630. Follow more on that to come, as well. That’s it for now, but keep reading for upcoming posts discussing both my OptiPlex 7040 desktop workstation, as well as the adventures with the T110.

Bridging IndieWeb and Steem Blockchain

Evening everyone. This is my first post where I combine both the power of the Indieweb and that of the Steem blockchain in one location, that of my own personal web site, rather than posting on Steem first. After reading mixed reviews of the Steempress plugin, I’ve taken the leap of faith; hopefully I’ll be able to drive more community engagement this way from both sides of the web.


The Current Problem


One of the most prominent issues that are facing us today are the number of technologies that are all built to accomplish the same thing, that of community engagement. Particularly the concepts behind the Fediverse, The IndieWeb, and social media blockchains. It’s very difficult to tell which, if any will win out in the end, but for now, I’m with everyone at once, trying to gain as much engagement as I possibly can, while considering the rewards secondary to the experience on Steem. Of course, they are part of it, for it would not be a proof-of-brain cryptocurrency otherwise, but let’s just see what happens with this. Will it succeed, or will it fail?

My IndieWeb Journey Part 1: Web Server and CMS Choices

I have to begin this post by first saying how I’m glad I found the Independent web and the fantastic community which surrounds it. There are too many people to name at the moment, so I’ll just mention those who I can think of off the top of my head. Thanks go indisputably to Greg McVerry who has replied to a lot of seemingly odd questions with detailed answers, providing just the right amounts of both technical detail and the reasoning behind concepts. I also appreciate those who have been providing hands with noticing weird oddities on my site, as well as providing feedback on how I might be able to fix random issues that crop up here and there.


Initial Research


I first started looking around the web for something other than the mainstream content that continues to propagate,  around eight months to a year ago, when I discovered my first Mastodon Instance. the link above points technically to my second one, or at least the second one I grabbed an account for, with the first being the flagship instance run by the developer of the software itself. I spent several months on his instance, and eventually left, finding it too busy, and with too many folks following me from instances I was not interested in. I’ve kept to my current one ever since. Then I found the IndieWeb through various articles, though if I could remember them, I would link.

I saw the similarity between the fediverse and the IndieWeb immediately, and it got even more interesting when I discovered their ability to be linked together. That’s when I began looking around for sites that showed off the concepts. The internet will be a much better place when every single site unquestionably supports responses from everywhere, not just from siloed walled gardens, as is the case seemingly today. I’m a member of this movement, and I intend to remain. Keep reading and walk with me on this adventure.


Creating my Site (May 2019)


After finally coming to the decision to join the movement, the issue of how to create my site came to the forefront. I’ll be the first to admit that my web design capabilities just are not there, so I needed something that could be used in light of that very situation, which could be scaled up to something better and more advanced as my programming knowledge grows.


Between WordPress And Known


My options in light of the amount of support given for IndieWeb concepts, to make up for the lack of design and development knowledge, fell between two; either WordPress or Known. As you can see here, I went with WordPress, but that’s mostly because I’m more familiar with it from other projects. I will probably try Known, as well, though, for the experience if nothing else, and I could end up switching it to my primary site in future. You never know.For a web server, I went with IIS, seeing the fact that I’m more familiar with it, and plus, I am sick of conforming to industry standards when they aren’t required. I shouldn’t have to on my personal site.