wesson

Administrators
  • Content count

    4,085
  • Joined

  • Last visited

3 Followers

About wesson

  • Rank
    Community manager
  • Birthday 12/10/1983

Profile Information

  • Gender
    Male

Recent Profile Visitors

3,130 profile views
  1. diasp

    We are aware with this behavior but unfortunately we can't fix it on our side. The issue is about article title looking so 'ugly'. It's url-encoded and this is how it has to be, as title is part of the url during the process of sharing. I think Diaspora should take care about decoding of the title when it's already on their site.
  2. The process just came "up-to date". So, the things should start working as they should.
  3. No, no. Do not readjust anything. It took more time than expected (the caching up). I'll let you know as soon as its ready.
  4. OK, thanks for the understanding. Let us know about the result then.
  5. You are welcome. Actually new filters creation might take more time (because of the above) but they should create properly. You can try switching the feeds and then go back to the filtered one in order to check about the result. It should be filtered.
  6. P.S. Please note that they are still "catching up". So you may notice delays on some of your rules/filters but this guarantees that you wont loose some important results. Everything should become fully operational/real-time in the next 30-40 minutes.
  7. Hello, first of all sorry about the caused inconvenience. We had a stalled process which was affecting Rules and Filters processing. Anyways our engineers already fixed it and everything should work as expected from about 40 minutes ago. Are you still having issues with your Filters?
  8. Unfortunately no and we can't promise anything at this stage. Since the Kindle devices does not support officially Google services framework. Sorry.
  9. Thank you for your feedback and willing to use our higher tier of the subscription plans. About the issues: 1. We'll appreciate if you provide us the exact Rule setup and respectively the matched results in order to give you more adequate solution about your issues. Please note that when you are using "is" in the conditions, the articles authors should have exactly the same names (when we are talking about authors) and if they have only one additional/or less symbol (including spaces) they won't be matched. And as soon as you are having better results with "contains" this might be the case for you. BUt this is only an assumption since I don't know your Rule setup and respectively its matches. 2. Please note that the sorting inside Inoreader is always done by the articles received/tagged/starred dates not their published dates. Sorting by published dates hides many pitfalls bearing in mind that <pubdate> parameter is easily customizable and isn't reliable. You can read more about this here or here. You can't see their published dates (instead on mouse-hover over dates) as you can see them in "normal" articles list, because they are not stored in our database system as a regular articles and their dates are considered upon their tagging/starring per user. It’s by design. For example - if you have to make a research and tag different feed's different articles and maybe there are older ones, you can't use it as a checklist for later, because if again add an older article it will be mixed somewhere between the other articles. Also you can't really use this tag as HTML export or RSS because of the same reason, if you add an older article, it will be mixed somewhere between every other article by its date, and not as the newest item as expected. So this can't be changed such easily. 3. Please note that you can't keep unread states for articles older than a month. This is related to our database architecture. Unread articles older than a month are automatically considered as read and they can't be marked as unread again. Also, keep unread and mark above/below as read is not shown (not available) when you previously used "mark all as read" over these articles. We've created this mechanism purposely to prevent overloading of our databases, because of the huge amount of user flags we need to store. Do not hesitate to ask if you need any additional information related to our service.
  10. I'm not sure that i'm understanding properly but i'l try to give you some info. You cant merge tags (in bulk). You can manually assign the new tags or add already created ones for each article separately. Of course you can have multiple tags for a single article for better organisation.
  11. I see. Thanks for the additional info. We'll check what could cause that.
  12. It might be... Are you able to simulate it with any other article?
  13. You are welcome. Thanks for the quick response.
  14. Hello, I just wanted to let you know that this behavior should be already fixed.
  15. Thanks for clarification. We'll consider your suggestion.