Hey guys, if you find a bug in SETT, reply to this with the info. You can embed screenshots if necessary or paste error messages. If you've experienced a bug that someone else has already reported, you can vote it up so that we know it's more important.
I like reading your and SebastianMarshall's blog post in my Kindle. I send both of your blog post to my kindle but the problem is that it doesn't display the Title of the blog post. It displays TYNAN or SEBASTIAN MARSHALL instead of blog post title.
There should be blog post title instead of SEBASTIAN MARSHALL. There is no way to figure out the blog post. Whenever I send WordPress Hosted blog posts to my kindle it shows the blog posts title at the left and authors name at the right side.
It would be easier to navigate if we could see the name of the blog post.
I didn't know you could do this. How do you do it?
You mean, How do I send Tynan's and Sebastian Marshall's blog post to my kindle?
If that's what you asked then, here's how I do.
1) Go to readability and then install the app on your browser.
2) After that you'll have readability plugin in the address bar.
3) Go to any blog post you'd like to be sent to your kindle.
4) Click on readability plugin and click to 'Send to Kindle'.
5) You're done.
Of course, this is not the only way to send blog posts to kindle. There are many other different ways to send, but I prefer sending it this way.
If you want to send Tynan's blog post automatically to kindle, then you can use kindlefeeder.com. But I haven't used it though. And I don't know how it works.
Hope it helps.
Can't subscribe or unsubscribe to SETT blogs. Clicking "subscribe" on drodio doesn't do anything. Also tested unsubscribing from sebastian's blog, and no result.
I'm on chrome and windows 7.
The front page of the blog (not the community side) currently says "Create New Post You're a curator of this blog, so you can post here." I'm probably not supposed to see that.
The old RSS feed stopped working after April 14. Tricky, since people that read only via RSS might not necessarily notice the absence of your posts.
So, I'm trying to search this site to figure out which security system you purchased for the Rialta.
So I load up Google and enter this query: 'security system site:tynan.com' - which searches all the pages indexed on tynan.com with a query of 'security system'.
Well, the Read Next box in the bottom right seems to embed the whole content of the posts it's suggesting into the parent page body. Google then indexes each page with content from 3 blog posts: the post which the page is about, and the two blog posts that are suggested in Read Next.
Try that sample search. Notice many results come back with the phrase '...even a solar powered security system.' That's because the Read Next box in each of those results suggests/embeds this post right here:
...and Google indexes the content from that post in every page Read Next is suggesting it for.
Without having spent a second reverse engineering this page, I think you might want to async-ly populate the Read Next content with an AJAX call or something. Then, that way, that content is *added* to the page, from the browser, as opposed to being part of the actual page, sent from the server (which, I believe, is what Google indexes).
Does that make sense? If not, don't hesitate ask for clarification.
Hey Tynan. Don't know if others have had this problem, but I'm unable to get a photograph into my post. It either
a) Let's me click on the 'insert picture button' and select my photo (or even drag drop it into the box) but doesn't insert it, or
b) Let's me drag drop it into the post itself but then doesn't let me Post it to my blog. I click the Blue "Post" button with no result.
Any idea why?
Using HTML Code generated to produce syntatic highlighting for a programming language (e.g. using http://tohtml.com/) works when a post is initially created. However when you go back to edit that post and save changes the HTML code is broken and does not produce proper syntax highlighting but instead tries to display the actual html code itself.
Is there a way to see what e-mail addresses are subscribed to your blog? Or possibly do some type of offer like "Put your e-mail address here and get a free e-book" off to the side (or next to the subscribe button)? Thanks!
I found a typo and also possibly a bug.
When replying to a private message a popup opened asking me to login. The messages said "Great! Now we need to who you are to post this" I think it's supposed to read "Great! Now we need to know who you are to post this."
The bug(?) is that it even asked me to login since I was already reading a private message, so clearly I must be logged in already.
When I tried to enter sebastianmarshall.com but it says,"Unable to select DB".
He hasn't pointed www.sebastianmarshall.com over yet. Remove the www and it will work. I'll remind him again, too.
SETT has now been powering Tynan.com for a month! The transition wasn't completely without hiccups (several of my most popular posts disappeared, for example), but by and large it has been a big success. After all, the blog's still standing, right?
I know that by making my own blog the test site for SETT I'm inadvertently making you a guinea pig, so thank you for putting up with the glitches (and bad email formatting) that have come along the way.
For those of you who haven't had a chance to explore the new SETT stuff on the blog, here's a short video highlighting some of the biggest changes:
Within 2-3 weeks, we'll be getting a few of our friends migrated over to SETT, and from there our next goal will be to open it to the public so that anyone will be able to have a SETT blog. You may have noticed that I now reply to pretty much every comment. It's not just because I'm trying promote SETT, it's because the process of replying to people is way easier now, and I know they'll get an email saying there's a reply. I'm really excited about getting more people running SETT and helping to make blogs a more social and interactive experience.
Just as the article says:
A rough, unpolished version of the site is on the brink of going live. There is (was?? Fingers crossed!), one bug that kept cropping up: There was an error coming up when trying to edit the priority queue once the draft had started. As you can imagine, this is a bit of a deal-breaker.
Anyway, we think we have fixed it now. We'll do another round of testing tomorrow (or today rather, it's past midnight here Down-under) and if the Footballing Gods are in a happy mood, have a beta site up and running tomorrow. Hoping to disappoint plenty of wives and girlfriends this weekend...