World News
A community for discussing events around the World
Rules:
-
Rule 1: posts have the following requirements:
- Post news articles only
- Video links are NOT articles and will be removed.
- Title must match the article headline
- Not United States Internal News
- Recent (Past 30 Days)
- Screenshots/links to other social media sites (Twitter/X/Facebook/Youtube/reddit, etc.) are explicitly forbidden, as are link shorteners.
-
Rule 2: Do not copy the entire article into your post. The key points in 1-2 paragraphs is allowed (even encouraged!), but large segments of articles posted in the body will result in the post being removed. If you have to stop and think "Is this fair use?", it probably isn't. Archive links, especially the ones created on link submission, are absolutely allowed but those that avoid paywalls are not.
-
Rule 3: Opinions articles, or Articles based on misinformation/propaganda may be removed. Sources that have a Low or Very Low factual reporting rating or MBFC Credibility Rating may be removed.
-
Rule 4: Posts or comments that are homophobic, transphobic, racist, sexist, anti-religious, or ableist will be removed. “Ironic” prejudice is just prejudiced.
-
Posts and comments must abide by the lemmy.world terms of service UPDATED AS OF 10/19
-
Rule 5: Keep it civil. It's OK to say the subject of an article is behaving like a (pejorative, pejorative). It's NOT OK to say another USER is (pejorative). Strong language is fine, just not directed at other members. Engage in good-faith and with respect! This includes accusing another user of being a bot or paid actor. Trolling is uncivil and is grounds for removal and/or a community ban.
Similarly, if you see posts along these lines, do not engage. Report them, block them, and live a happier life than they do. We see too many slapfights that boil down to "Mom! He's bugging me!" and "I'm not touching you!" Going forward, slapfights will result in removed comments and temp bans to cool off.
-
Rule 6: Memes, spam, other low effort posting, reposts, misinformation, advocating violence, off-topic, trolling, offensive, regarding the moderators or meta in content may be removed at any time.
-
Rule 7: We didn't USED to need a rule about how many posts one could make in a day, then someone posted NINETEEN articles in a single day. Not comments, FULL ARTICLES. If you're posting more than say, 10 or so, consider going outside and touching grass. We reserve the right to limit over-posting so a single user does not dominate the front page.
We ask that the users report any comment or post that violate the rules, to use critical thinking when reading, posting or commenting. Users that post off-topic spam, advocate violence, have multiple comments or posts removed, weaponize reports or violate the code of conduct will be banned.
All posts and comments will be reviewed on a case-by-case basis. This means that some content that violates the rules may be allowed, while other content that does not violate the rules may be removed. The moderators retain the right to remove any content and ban users.
Lemmy World Partners
News [email protected]
Politics [email protected]
World Politics [email protected]
Recommendations
For Firefox users, there is media bias / propaganda / fact check plugin.
https://addons.mozilla.org/en-US/firefox/addon/media-bias-fact-check/
- Consider including the article’s mediabiasfactcheck.com/ link
view the rest of the comments
By "interface" I meant the data interface between systems. Not a User Interface.
Additionally, it's been my experience that I rarely get to design the full stack - we inevitably have to handled data exchange and legacy systems. Those legacy systems are a type of "user" in this instance that we have to program for. We can take a 13:30 string, and store it in UTC, but without location or time zone being provided through that (which the message queue that we pull from doesn't have), it doesn't do us anything.
The solution for these type of problems usually involve find another source of data and mapping the time that way. This inevitably ends up being far more work for us because of the security, traceability, auditing, etc.
In my own experience, ideally you try to avoid using such interfaces. If however you're forced to handle such things (which is far too common) the design which is cheapest and safest is to convert to UTC using a suitable default timezone at the interface level and store the result in your core system time field AND also store the local time but not in a field that you actually use for queries and computations in the core. If (more likely, when) some of those times converted with a "suitable" default turn out to have been wrong in some way - which is not necessarilly something due to the timezone conversion - you can manually fix just those (ideally with bulk data update).
Mind you, a lot of this shit needs to be solved at the systems design and requirements specifications level - either it's accepted that the system will have a fraction of the time data wrong (and it will always do anyway, even without timezones: users enter wrong dates, OCR data reading can't correct for users filling-in the wrong time in a time field on a document, timestamps generated by machines whose internal clocks are not regularly synched with NTP serves can be off my many minutes and so forth), or the whole thing is designed as I described above so that all data is treated as compatible and when it inneviably turns out some times in some fields were wrong or incorrectly translated, you can fixe it in an non-automated way.
As much as the dream is to have the computer do everything itself in code and the data be perfect, that's incompatible with the real world, and that's for way more things than just time values.
The point is, again, that programmers have to deal with the world as is (and dates are hardly the only "quirk" around), not the world as they would like it to be, and that needs to be dealt with already at the level of system design by the (supposedly) senior designers and technical architects rather than having programmers running around fixing the innevitable problems in a system whose design does not take in account the quirks of how certain kinds of data are produced and consumed: proper systems design is about minimising the direct and indirect consequences of data errors, inconsistencies and datatype-specific quirks, not trying to fulfill expectations that all data in one's system is perfect.