I ultimately edited the original instagram post to remove the emoji to get around it, but haven't dug further into the issue after Otto's post via wordpress support. I suspect that I need to update the encoding to my database to have it work, but haven't had time to tinker with it recently.
I've seen the problem via two other hosts which aren't GoDaddy managed, so I don't suspect that's the underlying problem.
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!
@cswordpress I hadn't run across the keyboard issue with the bookmarklet yet, but I'm glad you're taking a look at fixing it. If you get some time, feel free to add your fix and links to the code at http:/
Several of us in the WordPress IndieWeb "camp" have been pushing to have more microformats2 compatible themes available to increase the selection. If you can push the Genesis framework project to include them, that would be phenomenal! Some of the notes on this work can be found and added to at https:/
@cswordpress @webrocker I'd noticed that WP-Social quit support a while back, but didn't know why; sorry to hear it. I wrote some thoughts here [https:/
If you go the route of API's you're on the hook for maintenance which can be troublesome at best. If you want a PESOS solution there are a few options listed on https:/
If you have a few minutes, you might find that POSSE is a better/more robust method, in which case you could set up the basic IndieWeb Plugin and use JetPack's Publicize (or SNAP or something similar) to syndicate your status updates to twitter. https:/
I'd be happy to help you if you have questions. Many of the developers of these plugins spend time in the Indieweb Chat [http:/
@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.
@ivasef85 @lukashmayyn @Anthony @WordPress @hypothes_is I know. I was *highlighting* it! ;)
@ivasef85 @lukashmayyn @Anthony Adding highlighting to my @WordPress blog with fragmentions and @hypothes_is took 2 minutes.
I know this was fixed in a prior version, but it looks like it's slipped back in again in v3.0.2?
Perhaps it was fixed in one of the dev versions I downloaded from Github, but it's not in the production version on WordPress.org at the moment.
Only secure locations allowed (Chrome) · Issue #17 · dshanske/simple-location https:/
Using Simple Location Version 3.0.2 (most recent stable from WordPress.org) in Chrome (both desktop and in Chrome mobile browser on Android):
When I click on "Get Location" button, I get a modal window that says:
Only secure locations allowed (see https:/
This is on a "live" site and not a dev environment. I'm guessing it may be because I'm using http and not https while requesting my location?? I'm anything but a js expert, so this is just a guess...
In Firefox, it correctly asks "Would you like to share your location with this site?" and proceeds properly.
It's called PressForward. I wrote up some more details here: http:/
I've been following the conversation on https:/
I'll spend some time in the next two days to see if i can stumble across the "fix" snarfed did and close this out. Thanks for the reminder @pfefferle.
@aaronpk @indiescripter Another option to encourage others to post their replies on their own sites rather than directly on yours, you could provide a URL box and details for people to webmention you indirectly (especially if they don't support Webmention yet). See the comment section at the bottom of http:/
For additional ideas, see: http:/
@Chronotope Okay, so I've spent the majority of my time since your tweet playing with (read: drooling over) @pressfwd.
It is awesome and almost exactly what I've been looking for for ages without knowing it. I think that I'm not only an immediate convert, but an evangelist.
In fact, not just hours earlier in the day, I'd made this comment on the WordPress Reader Refresh (at https:/
"Some nice visual changes in this iteration. Makes it one of the most visually pretty feed readers out there now while still maintaining a relatively light weight.
I still wish there were more functionality pieces built into it like the indie-reader Woodwind.xyz or even Feedly. While WordPress in some sense is more creator oriented than consumption oriented, I still think that not having a more closely integrated reader built into it is still a drawback to the overall WordPress platform."
From the sound of your tweets and how I see it laid out, in some sense I suspect you're personally almost also using it as a built in bookmark or to-read app like Pocket or InstaPaper? This is almost exactly the type of "off label" use case I'd like to bend it to--though it doesn't really require that much bending given its current architecture. Are you displaying all the items you've read/commented on publicly (and where is it?) or are you just using the comment functionality and the nominated portions as a private "I've read this list" on your back end?
I've been thinking about the topic for a while since just before InstaPaper's acquisition by Pinterest and recently written a few things including about Owning My Online Reading Status Updates: http:/
I've even thought about using the Wallabag self-hosted version of something similar to this, but I'd prefer something more closely integrated with WordPress and PressForward has almost everything one could dream for.
If you have a few minutes next week to chat via phone about some of these uses, I have a feeling you could expand your user base a bit as a result. I also know of a few folks working on similar WP-based readers who might be encouraged to merge their work into your much more polished project.
My thanks to the whole team for not only a beautiful plugin, but for some well written and spectacularly documented code on Github!
The IndieWeb plugin does have quite a few related plugins which all interact well, but you don't necessarily need them all. You can obviously pick and choose based on the specific functionality you'd like to have. Their modularity helps to make understanding what sets of functionality each piece provides a lot easier.
In particular the two that will recreate most of the requested functionality of wp-social above are [Webmention ](https:/
The other sub-plugins within the larger IndieWeb suite add supplementary functionality if you want/need it. This also helps to cut down on code bloat which can slow your site down. In fact, if you only want a few in the suite, you can install them separately from the larger plugin. The others also help to not only extend functionality, but to better automate portions of it.
They are all also are being actively developed/supported on GitHub.