Wikipedia:Reference desk/Archives/Computing/2021 September 20

From Wikipedia, the free encyclopedia
Computing desk
< September 19 << Aug | September | Oct >> September 21 >
Welcome to the Wikipedia Computing Reference Desk Archives
The page you are currently viewing is a transcluded archive page. While you can leave answers for any questions shown below, please ask new questions on one of the current reference desk pages.


September 20[edit]

Reporting twitter content[edit]

A few days ago I (and lots of others, none of whom I've ever heard of) received a strange (and completely unprompted) message in my "notifications". I had never heard of, much less interacted with, the user who sent it, and he appeared to have 0 followers and follow 0 other users when I hovered my mouse over his username. I was sufficiently disturbed by the message that I "reported" it w/in a few minutes, but I think I reported it as "offensive/disrespectful", when I probably should have reported it as "harmful/abusive", as the latter option allows you to summarize the problematic content. After reporting it the tweet vanished w/o a trace-& unfortunately I did not get a screenshot of the tweet & thus cannot remember the user's username, & thus while I would like to re-report the tweet as "harmful/abusive", I don't know how as I don't know the username of the person who sent it.

What should I do? I've tweeted at both Twitter Safety and Twitter Support and heard nothing back

Every now and then I receive messages that appear strange because they were actually meant for someone else with a similar user name. Was the message truly harmful/abusive, as in phishing, or merely strange and out of the blue? In the latter case you may simply ignore it. Otherwise, let it lie till it happens again.  --Lambiam 05:36, 20 September 2021 (UTC)[reply]

Potentially harmful/abusive.

Where does the power of content management systems end?[edit]

Content management systems (such as MediaWiki with which Wikipedia is built) are programs that can help to create very powerful websites; Encyclopedias, news portals, government organization websites and large e-commerce websites, but still sometimes they are being heavily customized.

From my experience, such customizations are typically done when there is a need to synchronize a website (by which services and/or products are being sold) with a stock management program and/or an accounting program; the term API often pops up in these contexts.

Perhaps the answer is just "their power ends in content", but maybe not; for example, is a program which is both a content management system and an artificial-intelligent-being which can contact every API, still a CMS? 49.230.6.7 (talk) 12:29, 20 September 2021 (UTC)[reply]

"Is an X which is both a Y and a Z still a Y?" I would have to say, yes. To ask a similar question, is the phone in your pocket, that has so many capabilities beyond point-to-point voice communications, still a phone? Perhaps you can refine your question. -- Tom N talk/contrib 00:39, 21 September 2021 (UTC)[reply]
I just name what you meant to "Smartphone" (or a pocket computer for that matter). 2001:44C8:4144:C83E:A899:C903:8885:B582 (talk) 04:38, 21 September 2021 (UTC)[reply]
@49.230.6.7: I agree with the other replies but just to add some more: Content Management systems are very similar to what (before the Internet) were called Document Management systems such as Documentum. When the dot.com boom first happened document management companies added content management to their features and the newer Content Management products like Interwoven (which I think was purchased by IBM) added document management. Essentially content/document management includes 1) A repository for documents, videos, etc. 2) Tools to define and enforce workflows and roles, e.g., a change to the web site can't be published until a manager has reviewed and approved it 3) Tools to define automatic processes, e.g., to make a backup of the site every day, to populate various pages with the latest info from databases, etc. What inevitably happens though is that each vendor tries to differentiate their product by adding functionality that goes beyond basic content management. E.g., for a while Portals were a big deal, a page where you could have a central location where all the features of your system could be accessed (these were typically internal Intranet but could also be Internet). There were vendors that just did portals but they added content management capabilities while the content/document management vendors added portal functionality (and then they all got bought by IBM anyway, just kidding... sort of). The most recent update to content/document management is Semantic Web or Knowledge Graph technology. With languages like the Web Ontology Language (OWL) you can define ontologies (logical models similar to object-oriented models but with more capabilities to make formal definitions about why a class is a subclass of another, that a property is a sub-property or inverse of another property, etc.). You can use the ontology to index your documents and other content in much richer ways than keywords. As an example check out RelFinder on DBpedia. DBpedia is a huge knowledge graph that is created by crawling the Info boxes of Wikipedia. RelFinder allows you to do queries like "show me all the researchers who worked with Godel and Einstein" It will draw a graph and you can then expand any of the nodes (e.g., Von Neumann) and see where he was born, who his colleagues were, etc. Pool Party is one of the vendors that utilizes this technology for content/document management. Top Braid is another although Top Braid also includes functionality for an Enterprise Data Model, a way to centrally define all the data for the software of an enterprise. The bottom line is that with any kind of system like Content Management, the boundaries are fuzzy as each vendor branches out into other areas to differentiate themselves and you really can't draw rigid boundaries that say X is content management but Y isn't. --MadScientistX11 (talk) 17:41, 23 September 2021 (UTC)[reply]