Comments for Another blog bites the dust http://eran.sandler.co.il Not biting dust since 2005 Sun, 11 Dec 2016 12:25:45 +0000 hourly 1 https://wordpress.org/?v=4.7 Comment on 5 tips on future proofing your Medium posts by Eran Sandler http://eran.sandler.co.il/2007/10/17/oauth-c-very-basic-library/comment-page-1/#comment-114279 Sun, 11 Dec 2016 12:25:45 +0000 http://eran.sandler.co.il/2007/10/17/oauth-c-very-basic-library/#comment-114279 the code lives with a different namespace here: https://github.com/xamarin/google-apis/blob/master/src/Externals/google-api-dotnet-client/Src/GoogleApis/Apis/OAuthBase.cs

]]> Comment on 5 tips on future proofing your Medium posts by Fester http://eran.sandler.co.il/2007/10/17/oauth-c-very-basic-library/comment-page-1/#comment-114170 Mon, 03 Oct 2016 09:38:16 +0000 http://eran.sandler.co.il/2007/10/17/oauth-c-very-basic-library/#comment-114170 Is this code still available somewhere? The google SVN repository is down

]]> Comment on 5 tips on future proofing your Medium posts by Peter Rattew http://eran.sandler.co.il/2015/12/31/lets-encrypt-error-the-server-could-not-connect-to-the-client-to-verify-the-domain-failed-to-connect-to-host-for-dvsni-challenge/comment-page-1/#comment-113659 Tue, 19 Jan 2016 16:41:52 +0000 http://eran.sandler.co.il/?p=434#comment-113659 I could not work out why i was getting this error when trying to set up Lets Encrypt, found your post and instantly felt dumb. Thanks ha

]]> Comment on 5 tips on future proofing your Medium posts by Configure https for a web app hosted on AWS beanstalk | Chuang Liu's Blog http://eran.sandler.co.il/2015/12/31/lets-encrypt-error-the-server-could-not-connect-to-the-client-to-verify-the-domain-failed-to-connect-to-host-for-dvsni-challenge/comment-page-1/#comment-113598 Sun, 10 Jan 2016 09:15:24 +0000 http://eran.sandler.co.il/?p=434#comment-113598 […] “lets encrypt” needs access port 443 (https) of the host machine of the web app (see A blog by Eran Sandler).   Here are steps we used to get Certificate for a beanstalk web […]

]]> Comment on 5 tips on future proofing your Medium posts by Eran Sandler http://eran.sandler.co.il/2015/12/31/5-tips-on-future-proofing-your-medium-posts/comment-page-1/#comment-113584 Tue, 05 Jan 2016 13:50:11 +0000 http://eran.sandler.co.il/?p=437#comment-113584 When you say decay, you mean traffic decay. Not necessarily relevance. Depending on the content itself, some of it (say a blog post about fixing or handling some problem) will always get a certain amount of traffic and references and in time will only just grow stronger in search engine.

As a developer I feel it all the time when I come across posts that are a year or more old yet are still relevant.

Same goes for old code that you throw at github. I have projects that I put up and forgot about but somehow even 3 years later people are still thinking its relevant and are sending pull requests.

The indirect value is much much bigger and, looking at the big picture, worth it.

]]> Comment on 5 tips on future proofing your Medium posts by Oded Golan http://eran.sandler.co.il/2015/12/31/5-tips-on-future-proofing-your-medium-posts/comment-page-1/#comment-113582 Sun, 03 Jan 2016 09:45:30 +0000 http://eran.sandler.co.il/?p=437#comment-113582 Don’t get me wrong, I’m a big believer in content. For a brand it’s usually a good idea to post under it’s own domain with cross references from, let’s say, Medium. Point being is that the decay factor for content is high.

]]> Comment on 5 tips on future proofing your Medium posts by Eran Sandler http://eran.sandler.co.il/2015/12/31/5-tips-on-future-proofing-your-medium-posts/comment-page-1/#comment-113581 Sun, 03 Jan 2016 09:31:03 +0000 http://eran.sandler.co.il/?p=437#comment-113581 Oded, I don’t agree. I have plenty of posts in this blogs and other (usually more technical) blogs that still get traffic and people are still finding useful.

Posts sometimes resurface when referenced from other newer posts or just get re-shared and gain traction again after a long long time (you have more than ample examples on Facebook).

If you care for the things you write, write not just under your own name, but under your own control.

If you care about exposure in certain places, cross post it (make sure to have a link).

Besides, if you really think that, why do you have http://blog.startafire.com/ ? :-)

]]> Comment on 5 tips on future proofing your Medium posts by Oded Golan http://eran.sandler.co.il/2015/12/31/5-tips-on-future-proofing-your-medium-posts/comment-page-1/#comment-113580 Sun, 03 Jan 2016 08:37:28 +0000 http://eran.sandler.co.il/?p=437#comment-113580 Well, posts are pretty much perishables, no one will read your post (or everybody else’s posts) more than a year after you wrote it. You want to post it where the cool kids at to get more exposure. I think the rest is just digital hoarding :)

]]> Comment on 5 tips on future proofing your Medium posts by Eran Sandler http://eran.sandler.co.il/2015/11/17/nsq-to-gs-streaming-nsq-messages-directly-to-google-cloud-storage/comment-page-1/#comment-113577 Thu, 24 Dec 2015 15:43:30 +0000 http://eran.sandler.co.il/?p=420#comment-113577 Thanks for the tip.

]]> Comment on 5 tips on future proofing your Medium posts by Joe Blue http://eran.sandler.co.il/2015/11/17/nsq-to-gs-streaming-nsq-messages-directly-to-google-cloud-storage/comment-page-1/#comment-113470 Thu, 26 Nov 2015 18:20:29 +0000 http://eran.sandler.co.il/?p=420#comment-113470 check out minio. Its a cloud indepent storage project written in go.
so you can store in GS or AWS, but also run your own, and there is no changes to your code

]]>