# scripted Published articles for scripted. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Flirty OnlyFans promoters on X may be using AI to appear human DevFeed: [Flirty OnlyFans promoters on X may be using AI to appear human]() Original publisher: [Read original article]() Author: Pieter Arntz Published: 2026-09-07T11:18:00Z Content type: article Language: en Sources: [Malwarebytes]() Topics: [AI Chat](), [Script](), [Chat Bot](), [Bot](), [ASCII]() Tags: [ai](), [ascii](), [bots](), [fraud](), [generative-ai](), [messaging](), [onlyfans](), [scam](), [scams](), [scripted](), [threat-intel](), [voice]() ### AI overview An investigation examines X accounts promoting OnlyFans pages that combine repetitive flirtatious scripts with dynamic replies, raising the possibility of generative AI-assisted messaging. It warns that personalized responses and voice notes may no longer reliably distinguish people from automated accounts. ### Source excerpt Personalized replies and voice notes make it increasingly difficult to tell whether you're talking to a human, chatbot, or AI agent. ## Updates to your AWS Sign-In experience DevFeed: [Updates to your AWS Sign-In experience]() Original publisher: [Read original article]() Author: Vaibhav Chowla Published: 2026-08-17T17:22:33Z Content type: release Language: en Sources: [AWS Security Blog]() Topics: [Amazon Web Services (AWS)](), [AWS IAM](), [identity and access management](), [AWS IAM Identity Center](), [browser]() Tags: [amazon-web-services-aws](), [aws](), [aws-iam](), [aws-iam-identity-center](), [aws-identity-and-access-management-iam](), [browser](), [identity-and-access-management](), [intermediate-200](), [scripted](), [security-blog](), [security-identity-compliance](), [uncategorized](), [updates]() ### AI overview AWS is gradually introducing a redesigned sign-in and sign-up experience to a limited number of customers. The changes add new account access options, unify the initial email entry point, and refresh the session selection page while existing customers continue using their current credentials and sign-in methods. ### Source excerpt Amazon Web Services (AWS) is gradually introducing updates to the AWS Sign-In and sign-up experience to a limited number of customers. We're sharing these changes so you will know what to expect as we gradually make the updated experience available to more customers. These updates include new options for creating and accessing AWS accounts. To [...] ## How to Improve User Experience (and Behavior): Three Papers from Stanford's Alexa Prize Team DevFeed: [How to Improve User Experience (and Behavior): Three Papers from Stanford's Alexa Prize Team]() Original publisher: [Read original article]() Author: A Href; Amelia Hardy; Haojun Li; Abigail See Published: 2022-02-01T08:00:00Z Content type: article Language: en Sources: [The Stanford AI Lab Blog]() Topics: [User Experience](), [Bot](), [Chat Bot](), [Language models](), [Open Source]() Tags: [alexa](), [chat](), [code](), [developers](), [experience](), [language-models](), [modular](), [neural](), [scripted]() ### AI overview This article presents research from Stanford's Alexa Prize team on improving user experience and behavior in socialbot conversations. It discusses user dissatisfaction, responses to offensive behavior, and how conversational control can be balanced between users and bots. The Chirpy Cardinal socialbot uses a modular combination of neural generation and scripted dialogue to support broad, open-domain conversations. ### Source excerpt Introduction In 2019, Stanford entered the Alexa Prize Socialbot Grand Challenge 3 for the first time, with its bot Chirpy Cardinal, which went on to win 2nd place in the competition. In our previous post, we discussed the technical structure of our socialbot and how developers can use our open-source code to develop their own. In this post we share further research conducted while developing Chirpy Cardinal to discover common pain points that users encounter when interacting with socialbots, and strategies for addressing them. The Alexa Prize is a unique research setting, as it allows researchers to study how users interact with a bot when doing so solely for their own motivations. During the competition, US-based Alexa users can say the phrase "let's chat" to speak in English to an anonymous and randomly-selected competing bot. They are free to end the conversation at any time. Since Alexa Prize socialbots are intended to create as natural an experience as possible, they should be capable of long, open-domain social conversations with high coverage of topics. We observed that Chirpy users were interested in many different subjects, from current events (e.g., the coronavirus) to pop culture (e.g., the movie Frozen 2) to personal interests (e.g,. their pets). Chirpy achieves its coverage of these diverse topics by using a modular design that combines both neural generation and scripted dialogue, as described in our previous post. We used this setting to study three questions about socialbot conversations: What do users complain about, and how can we learn from the complaints to improve neurally generated dialogue? What strategies are effective and ineffective in handling and deterring offensive user behavior? How can we shift the balance of power, such that both users and the bot are meaningfully controlling the conversation? We've published papers on each of these topics at SIGDIAL 2021 and in this post, we'll share key findings which provide practical insights for ## Grafana - installation and configuraton with InfluxDB and CollectD on Debian/Ubuntu DevFeed: [Grafana - installation and configuraton with InfluxDB and CollectD on Debian/Ubuntu]() Original publisher: [Read original article]() Author: Tom Published: 2016-01-10T00:00:00Z Content type: tutorial Language: en Sources: [Tomasz Gągor]() Topics: [Grafana](), [Debian](), [Ubuntu](), [MySQL](), [SQLite]() Tags: [apt](), [collectd](), [debian](), [grafana](), [https](), [influxdb](), [installation](), [linux](), [mysql](), [packages](), [permissions](), [play](), [port](), [scripted](), [sqlite](), [ubuntu]() ### AI overview A tutorial on installing and configuring Grafana with InfluxDB and CollectD on Debian or Ubuntu. It covers configuring the Grafana package repository, installing Grafana, choosing SQLite or configuring MySQL, connecting to Grafana on port 3000, and adding InfluxDB source data. ### Source excerpt Now when you have CollectD and InfluxDB installed you may configure Grafana 😃 First configure repo with current Grafana version (select your distro): curl https://packagecloud.io/gpg.key | sudo apt-key add - deb https://packagecloud.io/grafana/testing/debian/ wheezy main Now install package (on wheezy I needed to install apt-transport-https to allow installation of packages from repo via HTTPS): apt-get update apt-get install -y apt-transport-https apt-get install -y grafana By default Grafana will use sqlite database to keep information about users, etc: ## People who use screen readers don't use JavaScript DevFeed: [People who use screen readers don't use JavaScript]() Original publisher: [Read original article]() Author: Dave Rupert Published: 2013-04-21T00:00:00Z Content type: opinion Language: en Sources: [The A11Y Project]() Topics: [JavaScript](), [Web Development](), [Forms]() Tags: [developers](), [forms](), [javascript](), [scripted](), [ui](), [web](), [web-developers]() ### AI overview The article challenges the misconception that screen-reader users avoid JavaScript. It states that 97.6% of surveyed screen-reader users had JavaScript enabled and advises developers to make JavaScript applications, custom controls, forms, and other functionality accessible, while also providing fallbacks for users with JavaScript disabled. ### Source excerpt A common misconception among web developers is that screen readers only read the non-JavaScript page. Due to this misconception, we sometimes assume it's unnecessary to make JavaScript apps and other functionality accessible. This is categorically false. According to a January 2014 survey conducted by WebAIM, 97.6% of screen reader users have JavaScript enabled. Be sure to make efforts to ensure that all functionality (apps, custom UI controls, forms, etc) within your site is accessible with JavaScript enabled as well as provide accessible fallbacks for the 2% of users (globally) with JavaScript disabled. A good starting point might be to use native anchor links and form inputs instead of custom scripted form elements.