Ah. I was about to thank you and tell you it didn’t work. But it’s persisted per instances of the app. So since I recently switched from the web app to the iOS app, my list was currently empty even though I knew I had hidden multiple posts.
The location is a little weird to me though, as I think of this section more related to messages and comments.
I instead kept looking for it together with filtered and blocked users / communities.
While the root issue was still unknown, we actually wrote one. It sort of made sense. Check that the date from isn’t later than date to in the generated range used for the synchronization request. Obviously. You never know what some idiot future coder (usually yourself some weeks from now) would do, am I right?
However, it was far worse to write the code that fulfilled the test. In the very same few lines of code, we fetched the current date from time.now() plus some time span as date.to , fetched the last synchronization timestamp from db as date.from , and then validated that date.from wasn’t greater than date.to , and if so, log an error about it.
The validation code made no logic sense when looking at it.
This bug has created havocs for me. We had a “last synchronized” time stamp persisted to a DB so that the system was able to robustly deal with server restarts / bootstrapping on new environments.
The synchronization was used to continuously fetch critical incident and visualize them on a map. The data came through a third party api that broke down if we asked for too much data at a time, so we had to reason about when we fetched data last time, and only ask for new updates since then.
Each time the synchronization ran, it would persist an updated time stamp to the DB.
Of course this routine ran just as the server jumped several months into the feature for a few minutes. After this, the last run time stamp was now some time next year. Subsequent runs of the synchronization routine never found any updates as the date range it asked for didn’t really make sense.
It just ran successfully without finding any new issues. We were quite happy about it. It took months before we figured out we actually had a mayor discrepancy in our visualization map.
We had plenty of unit tests, integration tests, and system tests. We just didn’t think of having one that checked whether the server had time traveled to the future or not.
Good question, I may have worded that too strongly. But if they’ll approve it upon request that is pretty close to a recommendation still, even if they didn’t bring it up themselves. Keep in mind that all medicine will be subsidized and cost the government money, and afaik the medicine in question is fairly expensive, so doctors are in general supposed to be restrictive in prescribing medicine willy nilly - if they prescribe it, patients will trust that it will have effect and be safe.
It is. I’m not willing to try it myself. I wouldn’t like an untested drug that works in unknown ways and that goes into unwanted regions of my brain. But I still can very well understand it, especially when a doctor recommends it.
I think it’s just based on which 4-6 search results are ranked on top for you / your country, and then that’s used as basis for the quick answer. It also seems to cache the quick answer so even after I forced it so downrank some results, my answer was the same.
Alas, it has the emergent mind answer ranked fairly high still, and when search result was set to my country it was actually ranked highest.
Also, if you use Quick Answer, you’ll get same wrong answer:
Quick Answer
There are no countries in Africa whose name starts fully with the letter "K". While Kenya is the closest match, its name does not start solely with "K" [1]. All of the African countries' names were reviewed across multiple sources and none began completely with the letter "K" [2][3][4].
I couldn’t understand why you posted this complaint in c/politics.