Scott, I don't think I'd replied to you for some reason, but I think I'm generally in the same boat as you. While I prefer to have one Swiss Army knife-like tool that can do everything, I know that it just isn't going to happen, or at least it certainly isn't quite there yet. I use Twitter and Facebook for different things (primarily audience based), so I suppose I shouldn't expect to have my own site do exactly everything I want it to.
Part of the problem is that I don't have the skills, the time, or maybe even the patience to make my own site do everything I'd like it to (and if I did maintenance can be a bear), so sometimes picking up pieces of things here and there from other developers or even on other platforms seems to be the result. In some sense that's why I'm using both Known and WordPress simultaneously (along with a few other side projects which don't fit into either of those). WordPress does a lot of what I'd like, but the speed, simplicity, and ease-of-use that Known provides just couldn't be overlooked to give me more of what I wanted. Over time, I do find myself moving more and more under the WordPress banner, but I always hear the siren song of other tools calling, so it may never be under one umbrella.
I also find that using other tools lets me test drive UX, UI, and general functionality to see if it's something worth building, maintaining, or having myself. And even then, I like to do "manual until it hurts" to raise the bar a bit further.
Scott, I agree with you that it could do a better job of providing context as it gives almost none at all. Occasionally I'll cut and paste something more descriptive, but that's just a stopgap. I've noted similar things in the past: https:/
A possibly better version might be a mashup of Known's "Share" funcitonality, but with the proper markup for likes and reposts, but this would take a bit of reconfiguration which I haven't had the itch to fix just yet. My general value on likes and reposts like these is fairly low and if I want to keep more context I use other methods, particularly if I want to keep more context for my personal site search in the future.
In particular, for things like these, I'm a big fan of having the actual blockquote of tweets using their javascript for display, that way if Twitter were to fail one day, I'll still have the physical content even if I loose the display portion.
Eric, You'll get used to it all pretty quickly. Feel free to use my site to ping against if you want to test things out without annoying someone.
If you want a potential set up for using it with your mobile phone, try: http:/
It looks like you're using the hosted version of Known, but it you ever self-host, there's lots of additional goodies at: http:/
Testing with a reply from my own site without using Twitter or Facebook. Welcome to Known!
For those interested, @mapkyca has an Archive.org/Wayback Machine support plugin for @WithKnown #IndieWeb
https:/
I'm probably pretty close to being in your general boat on the technical side, though I may have been at it for about 5 minutes longer. Keep pecking away and you'll get there.
I notice that you don't seem to have connected your Instagram account to brid.gy yet, though you're collecting your Instagram posts via Known (presumably with OwnYourGram). Adding your URL links (with rel="me") properly (the Instagram account in your profile on vaviblog and the other in your IG account pointing to vaviblog (either in the website field OR your description field see https:/
Hint: Known already marks up links on your profile with rel="me" so you only need to put in the URL. Instagram doesn't support rel="me", but brid.gy routes around it on your behalf when you put it in one of the two locations described.
Jeremy, Like you, I had some of the same issues and questions when I first started. I'd had a primary website for a while that was a bit more blog-ish on WordPress with a few other subsidiary sites for work related things. When I got into IndieWeb, WithKnown had a great plug-and play set up for almost everything, so for me, it made a nice easy place to start. I also wanted to play with Known and use it to get my feet wet. I was particularly interested in owning a lot of the shorter form posting/microblogging like Twitter without overwhelming my prior subscribers on my WordPress blog with a lot of shorter "fluff". Once I'd gotten a few things working, Known was also incredibly good at quick short posts using bookmarklets (or this mobile solution I'd come up with: http:/
Slowly over time, as I've been adding bits and pieces here and there to my WordPress set up, it has been owning more and more while somewhat less lives on my Known Install. There's also been a huge amount of community development on the WordPress side, so that it's tremendously better now than it was when I started and continues to grow. I think I hit a bigger turning point after IndieWebCamp LA when I was able to work out a bit more about how I want to own and syndicate things from my primary hub (on WordPress). (See also: http:/
Ultimately, I'd recommend doing what works best for you at the moment as there are literally hundreds/thousands of ways to pull it off. Do things one at a time in small bite-sized chunks until you have it the way you want it. There's no reason to do everything all at once. Sometimes I've found that creating posts literally by hand in raw html has been a great way to start to see both how it looks/works, and then use that experience to figure out how to best/most easily automate it going forward.
I'll also note that my coding skills were old and rusty and have been slowly getting better over time as each piece evolves. Another nice part of the process is that you'll have a chance to see how others are doing things with examples from the wiki to help you figure out what might work best for you. Over the process I've also seen others stop, change gears, and even platforms, and try out something totally different. The key seems to be to start with something you know and begin working from there based on your particular "itches" and needs [http:/
Your post was certainly a good start for taking stock of what you've got and where you might like to go. Now just make a list of your itches and do things a step at a time. I know there's an IndieWeb Cat [https:/
Good luck!
The errors can sometimes be a result of which version of PHP you're running. Double check that, though I'm not sure what the minimum threshold Known requires at the moment. Usually these days v5.6 is a good sweet spot. Versions under 5.5 may cause errors like what you saw and I know my stupid host often defaults new installs to 5.4 for some reason.
You can also check to see if it's a known issue in the open or closed queues at the github repo: https:/
Otherwise cut/paste the error(s) into the issue queue in the repo to see what what others in the community think it could be.
Enjoying using Quill to post to my Known site. Thanks for the continual improvements Aaron!<p> #100daysofindieweb #quill</p>
@cswordpress @redcrew Thanks for the recommendation Amanda!
I'm guessing you installed PressForward directly on your production server without using a test environment? I can tell because all of your posts are trying to redirect, but are redirecting to themselves! It's a known bug I mentioned here: http:/
Until then you may want to go to the settings and set the redirect time to "0" which will prevent all of your pages from continually re-loading OR you could uninstall it from your production site and run on a test server.
I've been loving it since I installed and can't wait for the forthcoming patch. I'm curious what others think of it for the off-label use I've proposed.
@indiescripter I think you've probably got a pretty good start on the IndieWeb philosophy. And an even better start in that you're writing your thoughts on your own website first and then syndicating them to silos like Twitter.
I think that part of what you're missing about being able to reply to Aaron's original post is that his site both sends and accepts a new web protocol known as Webmention (http:/
I know Aaron also often syndicates copies of his posts to Twitter. There's another IndieWeb related service known as Brid.gy which bootstraps webmentions onto Twitter (in addition to other social silos) so that replies or comments to the copy that got syndicated to Twitter also send copies to the original post. In this case, he only syndicated it to news.indieweb.org, so it was less simple for you to have interacted with his post because there wasn't a Twitter version for you to interact with.
You'll find that within the broader community that different members will support varying levels of functionality (based mostly on what they're interested in), so someone like Tantek (tantek.com) will post on his own site and syndicate to Twitter, but he doesn't yet display webmentions. You can, however, post your replies to him on your own site and syndicate them to Twitter (perhaps using Brid.gy publish?) to reply to his syndicated copy on Twitter where he'll see the notification of your reply. You yourself serve as another example as you don't (yet?) offer a comment field on your own post. Perhaps you may never, but that's your choice. (I'll mention incidentally that many static website owners are using Aaron's Webmention.io for sending/receiving webmentions, see also: https:/
I think that a lot of the goal is to not only have fun with what you're doing on your own website, but do things which you find interesting/useful for yourself. Are you interested in locations/check-ins [http:/
Just be careful, because lurking in IRC or browsing the IndieWeb wiki for a while and seeing what others are working on or doing can make you very "itchy". Though the reverse is true that seeing what others have done (even how silos have done things in the past) can make it easier for you to build it not only better, but perhaps more quickly. Perhaps the CMS or language you're using is being used by others in the community [http:/
Keep up the search, and let us know if we can be of further help/assistance.
@EatPodcast Saw your conversation in chat earlier: In "Site Configuration" on Known set "Include permalinks" to "No" and you shouldn't get the repetitive Twitter card for things you send to twitter that are under the 140 character limit. If I recall, Brid.gy should still be able to find and backfeed comments based on the rel-me without needing the permalink in the tweet.
If you go over 140 characters, Known will automatically shorten the tweet and include the permalink so the reader can get the rest of the message. (I sometimes use this for longer than usual tweets in reply to people, like this one).
Generally you can include 117 characters + a URL and still always fit in under the 140 total.
If you manually include a URL, and the page has the correct meta data, the URL will turn into a Twitter card. If you include more than one URL, it's typically the last that will show the Twitter card metadata.
Hope this helps!
I've had issues in the past with using IndieAuth logins and Known. Sometimes it's finicky and prefers the http:/
I'll note that I've tried logging in with both:
http:/
http:/
and didn't have any problems/issues.
I suspect that for multi-user installations, Known needs the /profile/username addition to distinguish which account to allow publishing to. If I recall OwnYourGram had issues like this in the past if you need advice on what the solution was.
Does Kevin have a multiuser installation? Perhaps he was trying to log in with one account while logged into another?