Nicolas Delsaux

Without these containers, restarting beehive implies restarting all bees as if they never run. Typically, my RSS to Twitter chain would re-emit tweets each time beehive is restarted

My raspberry is able to connect to api.twitter.com, so it's not a network error curl https://api.twitter.com/1.1/account/verify_credentials.json?include_entities=false&skip_status=true&tweet_mode=extended {"errors":[{"code":215,"message":"Bad Authentication data."}]}

And notice I've literaly copy/pasted credentials obtained from twitter (and they are visible in the `beehive.conf` file (but I won't show them)

Interestingly, i've tried using those keys with tweetledee (http://tweetledee.github.io/tweetledee/), installed on the same Raspberry server, and it doesn't work either ! So it seems like the keys are ... not...

Yes that's exactly what I did I have created my application  And I've created my customer key/secret and access key/secret  That I've copied in beehive Twitter bee config...

oh yes it works ! https://twitter.com/riduidel/status/1133642224460283905

On 09/09/2014 17:20, nodiscc wrote: > @Riduidel https://github.com/Riduidel how is > |http://my-server:8080/Shaarli/?do=rss| incorrect? Where do you expect > the port number to be? > > Can this be closed? >...

On 09/09/2014 18:41, nodiscc wrote: > ``` > Do you see how both RSS and ATOM are wrong ? > ``` > > Ok I see it now. Strange, what...

On 21/10/2014 20:12, nodiscc wrote: > @Riduidel https://github.com/Riduidel can you merge #209 > https://github.com/sebsauvage/Shaarli/pull/209 in your install and > tell us if that fixes your problem? I don't have a...

OK, but I don't have a elinks version for my NAS (which serves as domestic linux box). BTW do you think it is possible to run the export command from...