186 results for “device”
If you're looking for a #clearcom #tw47 two-way radio to clearcom interface, I've got you covered! These retail for $1,600 CND - yours for half price! New old stock, in box, opened, unused.
This small device allows you to bridge your clearcom party line to your two-way radio system - bi-directionally!
If you're reading this post it is still available.
On Tubidy.Mobile's Tools page, the free in-browser audio utilities - cutter, speed changer, pitch changer, and looper - work only on files you own. You load a file from your own device and all processing runs inside your browser: nothing is uploaded to any server, so your audio stays on your machine the whole time. The changes are produced locally and the result is a file you download yourself. Try the tools at https://tubidy.mobile/tools
The San Francisco 49ers play the Atlanta Falcons on Sunday, October 25th at 1:00 p.m.
ET at Mercedes-Benz Stadium in Atlanta, Georgia.
The game will be broadcast on Fox, with live TV streaming supported across services like DirecTV, Fubo, Hulu, Sling, and YouTube TV.
Additional viewing options include NFL+ for mobile devices and international streams such as 7Plus in Australia.
https://en.hacks.gr/pos-na-parakoloythisete-zontana-ton-agona-anamesa-se-49ers-kai-falcons/
🥕 PantryPulse — Your Kitchen, Organized
This is a submission for the Hacktoberfest Open-Source AI Challenge Week 3: Slow and Steady.
What I Built
PantryPulse is a kitchen companion that helps you cook with what you already have and throw away less food. It aims to:
📸 Scan ingredients and keep a running inventory of your fridge
⏰ Watch expiry dates and flag items that should be used first
🍳 Suggest recipes based on what’s in stock
🛒 Build grocery lists so you only buy what you need
🌱 Cut food waste with smarter day-to-day planning
The idea is to spend less time managing your kitchen and more time enjoying what comes out of it.
Demo
💻 GitHub: MohdOves/Dev-Weekeend-Challenge-3
How I Built It
PantryPulse pairs a cross-platform mobile front end with a Python backend and AI-assisted food features.
React Native + Expo for the mobile and web app
TypeScript for safer, easier-to-maintain code
FastAPI (Python) for the backend API and logic
Expo SQLite for local storage of inventory and grocery data
Docker to containerize the backend
Gemma 3 4B (planned) for on-device ingredient recognition and recipe help, not yet implemented
A key goal is privacy-friendly, offline-first AI that works across devices.
Why Does Open Innovation Matter?
Open-source tools let me inspect, adapt, and improve what I build on. For PantryPulse, that means I can try running AI locally instead of relying on closed services, and other developers can contribute features, fixes, and new ideas.#devchallenge #hf26challenge #software #coding #development #engineering #inclusive #community
PantryPulse — Your Kitchen, Organized
Interesting links of the week:
Strategy:
* https://www.youtube.com/watch?v=WXL6K1lhvt0 - weeding out the undesirables, if we're not calling out this kind of shit, we're absolutely part of the problem
* https://www.ncsc.gov.uk/collection/problem-book/ai-cyber - NCSC turns the page and finds more problems
* https://cert.cyber.gouv.fr/dur/CERTFR-2025-DUR-003/ - more fun with water, this time in .fr
Threats:
* https://elkentaro.github.io/jp_incidents/ - .jp having a bad day^Wweek^Wtime of it with baddies
* https://emudhra.we-have-a-problem.com/ - did you just get a shitty certificate which means nothing?
* https://www.microsoft.com/en-us/security/blog/2026/10/21/storm-0940-uses-artex-agentic-ai-connectwise-supply-chain-compromise/ - is it simulation or emulation if the TA is using pen testing tools? 🤖
* https://blog.nviso.eu/2026/10/16/keystrokes-in-disguise-forensic-analysis-of-a-digispark-hid-device/ - key logging in the wild
Detection:
* https://righteousit.com/2026/10/20/mtt-sh-mounting-linux-images/ - @hal_pomeranz on the pain that is "mount"
Bugs:
* https://hackyboiz.github.io/2026/10/17/millet/cve-2026-58222/ - let's all do the Samba
* 4 - important contribution to cyber awareness month
* https://calif.io/php2shell/ - another important contribution to cyber awareness
Exploitation:
* https://www.netcraft.com/blog/how-attackers-get-into-your-calendar-the-easy-way - when you're offered a date, be careful where you put it....
* https://0xrefs.github.io/ - interactive cheat sheet
* https://blog.trailofbits.com/2026/10/14/package-managers-have-an-integrity-problem/ - not sure I'd refer to language specific tooling as package management, given their varying capability levels, but it's certainly true that they often lag behind distros' traditional package management
* https://blackfield.ch/blog/defeating-enforced-smb-signing/ - is SMB signing al that it promised to be?
Hard hacks:
* https://www.usenix.org/system/files/usenixsecurity24-lisowski.pdf - fun with SIMs
* https://www.usenix.org/system/files/woot26-lisowski.pdf - more fun with SIMs
Crypotography:
* https://emudhra.we-have-a-problem.com/ - the story of 4
Hardening:
* https://ghuntley.com/patch/ - can AI help us mitigate threats?
[#TRADESHOW] 140th #CantonFair #Phase 3 2026 will be held from October 31 to November 4, 2026, at #China #Import and #Export #Fair Complex in #Guangzhou. Officially themed #Better #Life, Phase 3 focuses on #fashion, #textiles, #footwear, bags, #food, #healthcare, #medical devices, #baby and #maternity #products, #toys, personal care, #sports, #travel, #office #supplies, and pet products. https://chinaexpohub.com/event/140th-canton-fair-phase-3-2026/
Subject: CoderNet IRC access and details
For: #irc #socialmedia #selfhosting
Image: An IRC exchange from today [posted with permission]
Short link: https://dansu.org/codernet-irc
IRC chat is due for a comeback. It’s the cat’s meow 🐈⬛ relative to Discord and other corporate chats 💬 #IRC is Free, Open Source, light, portable to nearly every device, and everything that you type doesn’t go into #AI. 😈
Some Mastodon 🦣 and Akkoma setups support #chat in the Fediverse client. However, that feature isn’t in wide use yet. IRC is the more standard option.
I was in #Freenode IRC off and on for a decade [2008 to 2017]. I’ve run a separate network, CoderNet, from 2012 to date on different dedis and VPSes.
Subsequent to an update on October 24, 2026, CoderNet can be reached as follows:
N1) any IRC client using secure mode, host irc.oldcoder.org, port 6697
or
N2) any IRC client using insecure mode, host irc.oldcoder.org, port 6667
or
N3) any major web browser, go to either irc.oldcoder.org or irc.minetest.org
If you make it into CoderNet, you can IRC PM me using:
/query OldCoder HelloMy hours excluding errands, rest breaks, and trips are typically noon til midnight Pacific Time. Initial responses typically take from 1 minute to 1 hour.
For options N1 and N2, the recommended GUI client for Linux and Windows is ZoiteChat:
CLI IRC clients include irssi and weechat. For Android, Revolution IRC is a free GUI client that works well for me. I don’t have a position on clients for Apple devices.
Option N3 lets you to connect to IRC using just a web browser. The IRC GUI in this case is The Lounge. For more information about The Lounge, visit:
The sample screenshot is of a IRC PM exchange with MURB, who was actually one of the first people that I chatted with in IRC 18 years ago. MURB is in his late 30s now and disabled but looking to be productive in #gamedev.
The IRC software stack used by CoderNet on the server side is as follows
ngircd - core IRC daemon
nginx - web server
lego - certs generator
anope - IRC services such as NickServ
thelounge - IRC web GUI
ocbip - a fork of the bip IRC bouncer
Presently, the network is running on a low-end Debian box. [IRC needs very little in the way of hardware.]
The Fediverse weblog site for CoderNet is located at:
Additional technical notes:
a. CoderNet uses valid certs as opposed to self-signed certs, so cert error messages shouldn’t be an issue.
b. IRC visitors don’t need to install The Lounge in order to use it. Nothing but a web browser is required.
c. The bouncer feature mentioned on The Lounge home page isn’t supported by the CoderNet setup. I use ocbip as my own bouncer and I could set it up for other people in some cases.
d. If anonymous is a priority, connect to CoderNet in secure mode, IRC PM me as explained above, and ask for a Freenode-type cloak.
e. The Edgy channels shown in the screenshot are in Edgy McEdge’s IRC network as opposed to CoderNet. I’m not Edgy, though I’ve known her since 2018.
To see a larger version of the screenshot, in most web browsers, right-click on the image, select “Open in New Window”, and resize the new window.
🚨 EUVD-2026-109320
📊 Score: 5.3/10 (CVSS v3.1)
📦 Product: phpipam, phpipam, phpipam (+1 more)
📅 Updated: 2026-10-24
📝 A vulnerability was detected in phpIPAM up to 1.8.3. Affected by this issue is the function create_rack_link of the file app/tools/racks/show-rack-popup.php of the component Rack Link Creation. Performing a manipulation of the argument deviceid r...
🔗 https://euvd.enisa.europa.eu/vulnerability/EUVD-2026-109320
🚨🇺🇸 Wisconsin man charged after online child abuse tips led investigators to his home
Steven Steele, 27, of Ladysmith, faces felony charges for allegedly possessing child sexual abuse material.
⠀
The investigation began after Wisconsin’s Division of Criminal Investigation received CyberTipline reports from the National Center for Missing & Exploited Children.
Investigators later searched Steele’s residence and seized electronic devices as evidence.
Source: https://drydenwire.com/news/rusk-county-man-charged-after-online-child-abuse-tips-lead-to-search/
New Googlebooks have hit the market, powered by a custom variant of Android 17 and integrated with Google's Gemini AI system.
The hardware utilizes Intel Core Ultra 5 or Qualcomm Snapdragon X Elite processors, with options for 120Hz OLED displays.
A key technical constraint is that these devices are restricted solely to Android applications.
Pricing for the new lineup begins at $899.99, positioning them against the current MacBoo…
https://en.hacks.gr/googlebooks-oi-neoi-foritoi-ypologistes-tis-google-me-android-17/
Things that I've gotten working so far on the NLS eReader: a braille shell, Tailscale networking, "Development Tools" submenu, editor package, working volume buttons, enhanced speech settings so you can toggle between more than the two voices that come with stock. Rewrote the unlocker to not use any proprietary Humanware drivers. Oh, right. The eReader doesn't ship with Acapela, so installing the "nls-speech" package will enable eSpeak which is included in all copies of Bread, for some reason. Then we have other packages for doubletalk, Dectalk, Pico and BestSpeech which will also work on non-NLS devices. The package manager is almost done, then I think I'll be ready for something for people to test and play around with.
"Indeed, if we want to improve the quality of all that jailbreaking code the chatbots are writing and circulating, we need to be able to put those jailbreaks in public repositories for public inspection and public critique. It's possible for some of the code produced by an LLM to be slop, and for other code to be fine, and for yet a third tranche of code to be remediable slop that can be made robust and reliable through auditing and refactoring. You can't figure out which is which if you have to keep that vibe code a secret on pain of a long prison-sentence.
I think there's good cause to be excited at the prospect of getting your devices working better, or just working at all. I think that even if the code stops working after a while, that's still fine – either you got more use out of your device than you would have without the new code, or maybe you just make more code that runs for a while for you, and then you do it again.
These individual improvements to your devices and technology are worth celebrating. But they are no substitute for systemic intervention. If we're going to have a new, good internet, a post-American internet that truly disenshittifies America's defective tech exports and replaces them with robust, transparent digital public goods, we need to make reverse-engineering legal again. Once we fix our policy, then we can fix our code"
https://pluralistic.net/2026/10/21/brittle-individualism/#gnireenigne
#AI #GenerativeAI #LLMs #VibeCoding #DRM #Copyright #IP #ReverseEngineering #Interoperability #AdversarialInteroperability
it's official peeps!! Cava Reader is coming to iOS!
remember when I said "coming soon TM??" up there... it's actually happening! a very kind friend gave me an Apple device so she could use Cava too 🥹 I'm aiming for early 2027, but knowing me it might land sooner lol
and some other news:
75 of you have installed it and 3 of you bought Full!! that genuinely made my week, thank you so much :D
v1.0.1 is out with bug fixes, plus a switch to turn off the anonymous usage stats without blocking the app's network access, so you keep the free library and language downloads
you can now buy Full with Monero (XMR), and it's 10% off since there's no payment processor taking a cut. that means you can get Cava with no Google and no bank card at all: APK + Obtainium, and pay in XMR
happy to answer any questions!
#Android #iOS #Audiobooks #Ebooks #Accessibility #ADHD #Monero #DeGoogle
Minimalism is a popular ethic, and one that I resonate with. However, it has brought with it a less spoken about secondary effect that I I call the 'Swiss Army Strife'.
We trade away our large collection of single purpose machines and replace them with one or two 'everything' devices, instead. But when your device can do everything, it becomes much harder to only use it for the right things...
The #Global #Memory #Innovation #Forum 2026 (#GMIF 2026) brought together 40 companies in #Shenzhen, #China to demonstrate how artificial intelligence is changing the #commercial value of memory and #storage. #Exhibitors presented #technologies intended to improve #AI #inference, extend limited #GPU memory, move #data more efficiently and support increasingly demanding #cloud, #edge, #automotive and on-device workloads. https://chinaexpohub.com/gmif-2026-ai-storage-memory-supply-chain/
The #Global #Memory #Innovation #Forum 2026 (#GMIF 2026) brought together 40 companies in #Shenzhen, #China to demonstrate how artificial intelligence is changing the #commercial value of memory and #storage. #Exhibitors presented #technologies intended to improve #AI #inference, extend limited #GPU memory, move #data more efficiently and support increasingly demanding #cloud, #edge, #automotive and on-device workloads. https://chinaexpohub.com/gmif-2026-ai-storage-memory-supply-chain/
Due to ongoing (mis)use of the exposed geospatial query capabilities "pos/dist" and "bbox" which severely degrades the whole system performance, we have to immediately block these parameters and cut off public access. These measures ensure the ongoing availability, performance and reliability of the whole system. If your app relies on geospatial awareness, you need to do client logic on the device/system now, not on the data source.
Buyers arrive at this question after a bad meeting: someone asked for "monitoring", someone else heard "time clock", and nothing was decided.
The two are different products, bought for different reasons, and governed by different rules.
The difference in one line each
The rule that settles most arguments
Time tracking is something you owe to the record. Monitoring is something you have to justify.
If the justification takes more than one sentence, you probably do not need the second one yet.
Four situations
The mistake
Buying the full feature set "so it is there if we need it", then leaving collection on. Capability you do not use is fine. Collection you do not need is the liability.
General information, not legal advice. The rules differ by jurisdiction; confirm the local position with a professional.#productivity #management #tools #discuss #software #coding #development #engineering #inclusive #community
Time tracking vs employee monitoring: they are not the same purchase
Deploy #Gotify Push Server on #Ubuntu #VPS
This article provides a guide to deploy Gotify push server on Ubuntu VPS.
What is Gotify Push Server?
Gotify is a self-hosted, open-source server for sending and receiving real-time messages and push notifications via WebSockets. It features a web interface for managing applications and is commonly used to send alerts to mobile devices or ...
Continued 👉 https://blog.radwebhosting.com/deploy-gotify-push-server-on-ubuntu-vps/?utm_source=mastodon&utm_medium=social&utm_campaign=mastodon.social #websockets #docker #selfhosting #selfhosted #pushover #letsencrypt
Fortinet's Oct. 22 releases fix critical and high-severity issues in FortiOS, FortiManager and FortiAnalyzer. Another patch cycle.
Full advisories arrive Nov. 10. For now, check the affected and fixed version tables, back up configurations, and patch internet-facing devices first.
Thought to Google “intel 660p firmware update” and yes: mine has (had) version 002C, but the most recent version is 005C. Hard to find historic changelogs since Intel sold their SSD business to Solidigm, but one purportedly for 004C copy/pasted to reddit says something about hanging, so let's try it.
Had to jump through a hoop or two to unpack the Solidigm Storage Tool™ (it really wants to be in /usr, not /usr/local, boo), but `sudo sst show --ssd` found the drive and indicated that a firmware update was available, and after taking a slightly-breathtaking minute, `sudo sst load --ssd /dev/nvme0n1` has reported success. What a world we live in. (The last time I was knowingly involved in the process of updating the firmware on a storage device, I wasn't actually the one to do it – Seagate warranty support did, to unbrick my 500 GB drive after the internal uptime counter got too high.) Now it tells me to reboot...
Detecting CVE-2026-96655 exploitation in Plex logs
Patching Plex Media Server to 1.43.3.10861 removes the SSRF described in CVE-2026-96655. It does not tell you whether someone already used it. That question is answerable, but only if you know what the server records.
The flaw lets an authenticated user supply a path parameter to /video/:/transcode/universal that the server then fetches on their behalf. Detection therefore rests on three observables: who called the endpoint, what target they nominated, and what the server did with the response.
Observable one: the request itself
Plex Media Server logs transcoder activity. Requests to the universal transcoder endpoint appear with client identity and session context. In a normal household, calls to that endpoint come from a small set of device identities at predictable hours.
The signal is not "the endpoint was called". It is "the endpoint was called by an identity that normally only browses", or "the endpoint was called with an unusual parameter shape". Build a baseline from a quiet week, then review deviations. Any review that starts after detecting a compromise has no baseline, which is why this step belongs in routine work.
Observable two: outbound destinations
The stronger signal lives outside the application log. A Plex server that suddenly opens connections to loopback administrative ports, to a router management interface, or to a link-local metadata address is doing something a media server has no reason to do.
If you have flow logs from a firewall, a router, or a cloud VPC, query for traffic originating from the Plex host toward internal management subnets. Plex fetches artwork, subtitles and metadata from the internet; it does not legitimately talk to 169.254.169.254 or to your hypervisor console.
On a single host without flow telemetry, host-level tooling can fill the gap. Connection auditing or a short-lived packet capture on the media server's interface will show the second hop within minutes of a test request.
Observable three: response handling anomalies
A forged request that succeeds returns content the transcoder did not expect. That frequently produces parse errors, unusual media probe failures, or transcode sessions that start and immediately stop. Spikes in transcode failures with no corresponding client complaint are worth a look.
This is a weak signal on its own, and it should not be treated as evidence. It is a triage prompt, not a conclusion.
Building the query
The remediation guidance from CISA sets a federal due date of 3 November 2026 under BOD 26-04, and organisations that follow KEV-driven prioritisation can reuse the same timeline. A useful internal ticket contains a list of hosts running 1.43.2 or earlier, a pointer to the log fields above, and an explicit statement of what "no evidence of exploitation" means in your environment.
The ZoomEye product query app="Plex Media Server" returns 507,974 matching assets, which is a reminder of how many servers exist outside any inventory you control. The vul.cve="CVE-2026-96655" query returns zero, meaning asset-level attribution for this CVE is not yet indexed. Absence of indexed vulnerable hosts is not absence of vulnerable hosts.
If you find something
Preserve the log segment and the connection records before rotating anything. Identify the account that made the request and disable it. Check what the forged requests reached: a response from a router admin page is different from a response from a metadata service that returned credentials. Rotate any credential or token the target could have disclosed. Then patch, because containment without the upgrade leaves the capability in place.
A detection rule that never fires is not proof of safety. It is a reason to keep the rule running while the patch rolls out.
References
#vulnerability #cve202696655 #plex #ssrf #software #coding #development #engineering #inclusive #community
Detecting CVE-2026-96655 exploitation in Plex logs
9to5 Google: Some Google Home Speakers downloading massive amounts of data in the background. “In my case, a Google Home Speaker that has not been used in the past day for voice commands or media streaming consumed 17 GB of data in 24 hours. At 3 a.m. PT, it downloaded 9.99 GB. Given the timing, this could be related to failed attempts to download device firmware.”
https://rbfirehose.com/2026/10/23/9to5-google-some-google-home-speakers-downloading-massive-amounts-of-data-in-the-background/
DATE: October 26, 2026 at 12:00PM
SOURCE: PSYPOST.ORG
** Research quality varies widely from fantastic to small exploratory studies. Please check research methods when conclusions are very important to you. **
-------------------------------------------------
TITLE: Frequent cannabis use linked to higher odds of nighttime breathing problems
URL: https://www.psypost.org/frequent-cannabis-use-linked-to-higher-odds-of-nighttime-breathing-problems/
Adults who use cannabis are more likely to report loud snoring and pauses in breathing during the night, according to new research published in Sleep Health: Journal of the National Sleep Foundation. The findings indicate that more frequent cannabis consumption corresponds with higher odds of experiencing these nocturnal breathing issues, even after accounting for factors like body weight and tobacco smoking. This relationship raises important questions for the growing number of people who turn to cannabis as a sleep aid.
Sleep-disordered breathing is an umbrella term for medical conditions characterized by abnormal respiratory patterns or insufficient ventilation during rest. The most common form is obstructive sleep apnea, a disorder in which the muscles in the back of the throat relax too much, causing the upper airway to narrow or collapse entirely. People with this condition require extra physical effort to breathe, often resulting in loud snoring, gasping, or brief, repeated stops in breathing known as apneas. Standard treatments like continuous positive airway pressure machines, oral appliances, and surgery can be effective, yet many patients find the devices uncomfortable or difficult to tolerate over the long term.
At the same time, cannabis has become increasingly accessible across the United States, and difficulty sleeping is one of the most common reasons people cite for using it. While users frequently report that the plant helps them rest, controlled clinical trials examining cannabinoids and sleep have produced mixed outcomes.
For example, a 2023 clinical trial covered by PsyPost found that consuming medicinal cannabis oil improved sleep duration and increased midnight melatonin levels in adults with insomnia, whereas a study covered by PsyPost in 2024 indicated that a cannabis compound called cannabinol reduced nighttime awakenings when taken alone but showed no benefit when combined with cannabidiol, another cannabis compound. Observational tracking also points to potential drawbacks, such as a 2026 longitudinal study of military service members that linked current cannabis use to worse overall sleep quality and longer times needed to fall asleep.
When it comes to breathing disorders specifically, tetrahydrocannabinol, the primary psychoactive compound in cannabis, has shown some potential to stabilize breathing in animal experiments and small human trials using oral pills. However, the broader clinical evidence remains inconsistent, leading the American Academy of Sleep Medicine to formally advise against using cannabis to treat obstructive sleep apnea. Most everyday consumers inhale cannabis rather than taking standardized pills, exposing their airways to smoke and heat that could inflame the tissues of the throat.
The new research, led by Tyler J. Gallagher, a resident physician in the Caruso Department of Otolaryngology-Head and Neck Surgery at the Keck School of Medicine of the University of Southern California, and co-first author Matthew E. Lin of the David Geffen School of Medicine at the University of California, Los Angeles, sought to evaluate how everyday consumption relates to signs of breathing issues at night.
“While some studies have explored cannabinoids as potential treatments for obstructive sleep apnea, there has been relatively little population-level research examining whether real-world cannabis use is associated with common signs of sleep-disordered breathing, such as loud snoring and pauses in breathing during sleep,” Gallagher told PsyPost. “We sought to better understand this relationship using a nationally representative sample of US adults.”
To investigate this connection, the authors analyzed information from the 2017 to 2018 Behavioral Risk Factor Surveillance System, a state-based telephone survey coordinated by the Centers for Disease Control and Prevention. Although nearly 900,000 adults completed the main survey during those two years, only Minnesota and Tennessee included optional survey modules asking about both cannabis habits and sleep breathing symptoms. From the respondents in those two states who had complete data, the researchers selected a stratified random sample of 14,485 adults designed to match the demographic profile of the broader United States population.
Participants were asked how many days they had used marijuana or cannabis during the past 30 days, as well as their primary method of consumption and whether they used it for medical or recreational purposes. The researchers grouped the respondents into three categories: non-users (zero days in the past month), non-regular users (1 to 15 days), and regular users (16 to 30 days). Signs of sleep-disordered breathing were assessed using two yes-or-no questions asking if anyone had ever observed the respondent stop breathing during sleep, and if the respondent had ever been told that they snore loudly.
Of the participants, 13,461 reported no current cannabis use, 438 were classified as non-regular users, and 364 were regular users, meaning about 5.5 percent of the sample currently used cannabis. Smoking was by far the most common consumption method, reported by about 87 percent of both non-regular and regular consumers, followed by vaporizing and eating. Among non-regular users, 61.6 percent used cannabis strictly for recreational reasons, whereas 37.6 percent of regular users reported using it strictly for medical reasons and another 24.7 percent used it for both medical and recreational purposes.
Overall, signs of sleep-disordered breathing were common across the entire cohort, with 44.7 percent reporting either loud snoring or witnessed apneas. In the unadjusted raw numbers, 44.3 percent of non-users reported at least one of the two breathing signs, compared to 48.4 percent of non-regular users and 55.2 percent of regular users. Specifically, witnessed breathing pauses were reported by 15.3 percent of non-users, 17.1 percent of non-regular users, and 19.8 percent of regular users. Loud snoring was reported by 41.3 percent of non-users, 44.5 percent of non-regular users, and 50.0 percent of regular users.
To account for other differences between users and non-users, the researchers ran statistical models that applied national survey weights (statistical adjustments that make a sample better mirror the U.S. adult population) and controlled for a wide range of potentially confounding factors. These adjustments accounted for age, sex, race and ethnicity, education, income, health insurance status, diabetes, body mass index, alcohol consumption, traditional cigarette smoking, and electronic cigarette use. Even after factoring out the influence of tobacco smoking and body weight, cannabis use remained independently associated with higher odds of sleep-disordered breathing symptoms.
Compared to non-users, non-regular cannabis users had 41 percent higher odds of reporting witnessed apneas, 26 percent higher odds of reporting loud snoring, and 33 percent higher odds of experiencing either symptom. The association was more pronounced among regular consumers. Those who used cannabis 16 to 30 days per month had 73 percent higher odds of witnessed apneas, 68 percent higher odds of loud snoring, and 82 percent higher odds of reporting either sign compared to non-users. These figures describe odds rather than probabilities, so the absolute differences are smaller than the percentages might suggest; in the raw numbers, about 55 percent of regular users reported at least one sign, compared with about 44 percent of non-users.
“While the impact of infrequent use is relatively small, the odds of irregular breathing during sleep almost double with more frequent cannabis use, making this a strong association worthy of consideration before frequent cannabis utilization,” Gallagher explained.
The researchers also analyzed cannabis consumption as a continuous spectrum from zero to 30 days. In the weighted models, each additional day of cannabis use per month was associated with an approximate 2 percent increase in the odds of reporting witnessed apneas, loud snoring, or either sign, an estimate the authors note is clinically small and serves as a general summary across use levels rather than a strict per-day effect. When the authors repeated the analysis without the national survey weights, regular cannabis use remained linked to both breathing signs, though the estimates were smaller (for example, 36 percent higher odds of either sign rather than 82 percent). In that analysis, non-regular use was no longer linked to loud snoring or to either sign, and its link with witnessed breathing pauses sat right at the threshold of statistical significance.
“The strength of the association and its greater magnitude among more frequent users were notable, particularly given that some studies have investigated cannabinoids as potential treatments for sleep apnea,” Gallagher said. “These findings may reflect differences between isolated cannabinoids studied in clinical settings and real-world cannabis use, including differences in composition and method of consumption.”
The authors proposed two primary biological mechanisms that might explain why cannabis consumers report more signs of airway obstruction at night. Because roughly 87 percent of the consumers in the sample smoked their cannabis, physical irritation from smoke is one possible contributor. Unlike tobacco, cannabis smoke is typically inhaled through deeper breaths without a filter, and it burns at a higher temperature, which can cause thermal injury and inflammation in the throat tissues that narrow the upper airway.
A second potential mechanism involves the way cannabis interacts with the autonomic nervous system, which regulates involuntary body functions. While small doses of cannabis tend to stimulate the sympathetic nervous system, the body’s “fight or flight” system, higher doses activate the parasympathetic nervous system, which promotes physical relaxation. Frequent users may develop tolerance and consume larger quantities, and the resulting parasympathetic activity may cause the muscles that hold the upper airway open to relax excessively during sleep, making the throat more likely to collapse.
There are a few things to keep in mind when interpreting these findings. Because the survey captured information at a single point in time, the study cannot establish whether cannabis use causes sleep-disordered breathing or if the relationship works in the opposite direction. People who suffer from undiagnosed sleep apnea often experience fragmented, unrefreshing sleep, and it is possible that some of these individuals turn to cannabis in an attempt to self-medicate their exhaustion or insomnia. The researchers also could not account for factors such as sleeping pill or sedative use, heavy drinking, or psychiatric conditions, any of which might influence both cannabis use and nighttime breathing.
The reliance on self-reported telephone survey data also introduces constraints. Asking participants if they have been told they snore or stop breathing is less reliable than conducting an overnight medical sleep study, and people who sleep alone may be unaware of their nighttime breathing habits. Additionally, the survey only tracked how many days a person used cannabis over the past month, without measuring the exact dosage, potency, or ratio of specific compounds like tetrahydrocannabinol and cannabidiol.
The data came from just two states, Minnesota and Tennessee, because they were the only ones to include both sets of questions, and roughly 98 percent of the original survey respondents were excluded for that reason or because of missing information. Survey weights help align the sample with national demographics, but the authors note that applying them to such a small subset is debated among statisticians. In addition, the breathing questions asked whether these symptoms had ever been observed, while the cannabis question covered only the past month, so some symptoms may have predated participants’ current cannabis habits.
Gallagher emphasized that reporting these symptoms is not the same as receiving a formal medical diagnosis. “While obstructive sleep apnea – a clinically defined and hazardous intermittent airway obstruction during sleep – is a type of sleep-disordered breathing, this study cannot make conclusions about the association between cannabis use and sleep apnea or other associated long-term risks,” he noted.
Future research will need to incorporate objective sleep testing, such as polysomnography, an overnight sleep study that monitors breathing, oxygen levels, and brain activity, to verify whether cannabis habits correspond with clinically diagnosed sleep apnea. Scientists also need to compare different delivery methods, such as edibles versus inhalation, to separate the chemical effects of cannabinoids on throat muscles from possible damage from inhaling hot smoke.
“Further research is required to examine the long-term effects of cannabis use on sleep and to determine the effects of cannabis dosage, different cannabis compositions, and different methods of consumption on sleep-disordered breathing,” Gallagher said. “Additionally, the long-term consequences of these impacts must be studied.”
Until those relationships are clarified, the authors suggest that physicians should counsel patients about the potential respiratory risks of using cannabis, particularly for individuals who already show signs of sleep-disordered breathing. “People experiencing persistent snoring, pauses in breathing, or other symptoms of sleep apnea should seek medical evaluation rather than trying to utilize cannabis to manage their sleep,” Gallagher advised.
“This study highlights the importance of evaluating the broader health effects of substances that people increasingly use for self-management,” Gallagher added. “Cannabis may have benefits for certain symptoms or conditions, but those potential benefits should be considered alongside possible risks. Sleep-disordered breathing is particularly important because it can go unrecognized for years while causing significantly worse quality-of-life. We hope these findings encourage further research and help clinicians have more informed conversations with patients who use cannabis for sleep-related concerns.”
The study, “Cannabis use and associated sleep-disordered breathing among US adults,” was authored by Tyler J. Gallagher, Matthew E. Lin, Ian Kim, Ziva D. Cooper, Sebastian M. Jara, and Eric J. Kezirian.
URL: https://www.psypost.org/frequent-cannabis-use-linked-to-higher-odds-of-nighttime-breathing-problems/
-------------------------------------------------
Private, vetted email list for mental health professionals: https://www.clinicians-exchange.org
Unofficial Psychology Today Xitter to toot feed at Psych Today Unofficial Bot @PTUnofficialBot
-------------------------------------------------
#psychology #counseling #socialwork #psychotherapy @psychotherapist @psychotherapists @psychology @socialpsych @socialwork @psychiatry #mentalhealth #psychiatry #healthcare #depression #psychotherapist #Cannabis #SleepHealth #SleepApnea #SleepDisorderedBreathing #LoudSnoring #NighttimeBreathing #RespiratoryHealth #HealthResearch #MedicalResearch #SleepAwareness
I’m building EatNeat, a mobile app that helps people turn a nutrition plan into a manageable routine—before “What should I eat?” takes over the evening.
A lot of meal-planning tools focus on creating a plan. I’m focused on what comes after: remembering it, finding something practical when hunger clocks in, and tracking what you ate without turning dinner into a spreadsheet assignment.
EatNeat is still a prototype. Here’s what’s working, what I’m figuring out, and how the mascot Bitey provides moral support.
The core loop
The app is organized around a simple cycle:
1. Create a meal plan or bring in an existing one.
2. See the day’s meals and get reminders at their scheduled times.
3. Browse meal ideas that match selected constraints.
4. Capture or mark a meal as eaten.
5. Review progress over the day and across recent days.
The Today screen brings schedule and progress together. Meals can be marked eaten when their scheduled time arrives, and progress includes estimated nutrition metrics. The user stays in control; the app helps without handing out gold stars for lunch.
AI as a helper, not the whole app
EatNeat has AI-assisted flows for personalized plans, meal recommendations, recipes, and optional photos. Requests include selected filters and nutrition targets. Practical constraints are requirements: an “under 15 minutes” meal can’t hide a 40-minute oven step, and equipment filters should match the actual cooking method.
Food photos are optional and handled separately from meal text. Without a photo, the meal still appears with a bundled animation or illustration. The recipe shouldn’t vanish because its glamour shot is late.
The app can call configured service endpoints. During local development, some AI flows can call Gemini directly with a development environment key. A production app should route requests through an authenticated server and keep provider keys off the client.
AI nutrition values are estimates. EatNeat is not a medical tool, and the prototype does not treat a missed meal as a failure or make clinical recommendations.
Local-first state and reminders
Plans and meal logs are stored on-device with AsyncStorage. Writes are debounced and serialized, and local notifications remind users at planned meal times—because remembering breakfast shouldn’t require remembering to remember breakfast.
Private meal-log photos stay on-device. If a user uploads a plan photo for parsing, it goes to the configured plan-reading service, with that made clear before upload.
The stack
The current app uses:
What is still a prototype
The accountability feed displays sample posts and does not publish to a social service. Some preview screens use illustrative nutrition data. The app doesn’t ship a backend, so server-based AI features need a configured endpoint. For now, the social circle is supportive and fictional.
I’m also breaking larger screens into focused components. The Today screen’s progress visualization and schedule calculations now live outside its route file, making the daily flow easier to evolve.
What I’m learning
The most useful decision so far: keep the basic habit loop independent of AI. Meal ideas work without generated photos; logging works without image analysis; plans can be reviewed when a service is down. A flaky model shouldn’t get veto power over lunch.
AI can add convenience, but a slow request or missing key shouldn’t block the everyday action. The meal still exists even if the pixels don’t.
EatNeat is under active development. I’m currently refining the meal flow, reminders, and progress UI while building toward a more complete, privacy-conscious backend.
If you’re building a habit-focused app, I’d love to hear how you decide which parts should depend on AI and which should keep working on their own.#buildinpublic #mobile #showdev #software #coding #development #engineering #inclusive #community
# Building EatNeat: Meal Plans, Gentle Reminders, and a Supportive Mascot
Short answer: find people through work you can already click on, judge them by five specific pages instead of the homepage, and use the first call to ask what is not included. Those three habits filter out most of the bad options before money comes up.
Where to look
Start with sites you already use in your own industry. Scroll to the footer and look for a "site by" credit. If there isn't one, ask the owner who built it. A referral from someone whose site you can open and poke at is worth more than any directory listing.
Other places that work:
What not to use as a filter: the lowest price, the longest list of services, and any promise about search rankings.
The five pages to open on every portfolio site
Their homepage is the page they spent the most time on. It is the least informative page they have.
1. The busiest page. Find the page with the most repeated elements — a product listing, a services index, a team page. Ask yourself: does the layout hold with three items? With thirty? Does a long paragraph still read, or does the text run into the next block? This is the page that resembles your actual site.
2. The contact or enquiry page. Submit a test enquiry with your real email address. Did you get a confirmation? Did the form tell you clearly when you submitted it empty? A broken form on a developer's own site is the single most useful signal you will get, and it costs you two minutes.
3. The mobile version, on your phone, on mobile data. Not on their office wifi and not in a device simulator. Time how long until you can read the headline, tap the menu open, and try to fill the form with one thumb.
4. The second language, if you need one. Do not check whether the words are translated — check whether the pages are. Click three links from the translated homepage. Do they stay in that language, or dump you back into the default one? Does the product list show the same products?
5. The footer pages. Privacy policy, terms, cookie notice. If they build for customers in Europe or the United States and their own site has none of these, that tells you what will be missing from yours.
Two more checks, thirty seconds each:
One more thing worth doing: portfolios often include sites the person only partly worked on, or maintained rather than built. That is not dishonest, but it is worth asking directly — "what was your part on this one?" A straight answer is a good sign.
The first call: eleven questions
Ask these before you talk about price. The point is not to catch anyone out; it is to find out whether they have done this enough times to have opinions.
1. Who actually does the work? A good answer names the person and says whether any part is subcontracted. A warning sign is "our team" with no names, or a salesperson who will not be involved after signing.
2. What do you need from me, and what happens if it arrives late? A good answer is a written list — logo files, company text, product photos, product data, hosting login — plus an explicit statement that the clock starts when the materials arrive, not when you pay. A warning sign is "just send whatever you have."
3. What will I see first, and when? A good answer is a live preview address with a date attached. A warning sign is "we'll send you screenshots."
4. How many rounds of changes are included, and what counts as a change? A good answer gives a number and a definition: text swaps and colour changes are one thing, a new page or a new feature is another. A warning sign is "unlimited changes" — that is not a policy, it is the absence of one.
5. What is not included? A good answer is a list: domain, hosting, business email, copywriting, photography, translation, ongoing updates. A warning sign is silence, or "everything is included."
6. Whose name is the domain and hosting in? A good answer is yours, from day one, and you get the login. A warning sign is theirs, "for management purposes." This is the most expensive mistake on the list — recovering a domain from someone who stops answering is slow and sometimes impossible.
7. Will I have admin access to the site when it's finished, and can I export the content? A good answer is yes, plus a plain explanation of what you will be able to change yourself. A warning sign is "you don't need access, we handle updates."
8. What happens after launch — what's covered, for how long, and what's billed extra? A good answer defines a window for fixing defects and a rate for everything after it. A warning sign is "free support forever", or no answer at all.
9. What is the timeline measured from? A good answer is a number of working days counted from the date your materials are complete. A warning sign is a confident "two weeks" said before they have seen your content.
10. What would make you turn this project down? A good answer names something real — a deadline they cannot hit, a platform that does not fit, a budget that does not match the scope. A warning sign is "nothing, we can do anything." Anyone who has done this for a while has walked away from something.
11. Can I speak to the client whose site you just showed me? A good answer is "I'll ask them" or "they've agreed to be a reference." A warning sign is every single project being off-limits.
Red flags and green flags
Red flags, in roughly the order they should worry you:
Green flags:
Payment and paperwork
Two rules that solve most disputes before they start.
Do not pay the full amount up front. Split it against things you can see: a deposit to start, a payment when the preview is up, the rest at launch. Milestones tied to deliverables beat milestones tied to calendar dates.
Get the scope in writing, including the number of pages, who writes the text, who supplies the photos, and what happens if you add a page later. If the document does not mention something, assume it is not included.
Before you contact anyone: thirty minutes of prep
Write these down and the conversation becomes much shorter:
The quotes you get will only be as good as the brief you send. And a developer who asks you good questions is telling you they have been burned before — that is usually the one worth a second call.#career #freelance #webdev #software #coding #development #engineering #inclusive #community
How to vet a web developer before you pay: which pages to open, which questions to ask
Why 10,000 Steps a Day? The Curious Story Behind a Number We Took as Gospel
Ten thousand steps became a famous fitness goal, but the science behind the number is more interesting than you might think.Dear Cherubs, why are we all chasing 10,000 steps a day as though a tiny digital counter holds the secret to eternal youth? The surprising answer takes us back to 1960s Japan, a clever marketing campaign and a number that may have become a health obsession partly because a machine reset at 10,000.
THE NUMBER THAT SOLD A WALKING HABIT
According to The BMJ, the familiar target traces back to Japan in the mid-1960s, when a company called Yamasa introduced a pedometer known as the manpo-kei. The name translates roughly as “10,000-step meter”, and it arrived during the excitement surrounding the 1964 Tokyo Olympics.
The timing was excellent. Japan was becoming increasingly interested in physical fitness, and the idea of tracking daily movement offered people a simple way to get more active. Ten thousand was memorable, easy to communicate and satisfyingly round. Marketing departments have been exploiting those qualities for decades. No surprises there.
But here comes the interesting bit. Research published in the journal Ethnographiques.org reports that the original manpo-kei reset to zero after every 10,000 steps. That detail gives the machine-reset theory some credibility: a device designed around a particular number could have helped reinforce that number as a daily target.
However, it would be a stretch to claim that the reset mechanism alone created the trend. The product was already named after 10,000 steps, and the slogan was being promoted as a walking goal. The evidence points to a combination of marketing, product design and a catchy number rather than one mechanical quirk changing humanity forever.
A MARKETING NUMBER BECOMES A HEALTH RULE
The real plot twist is that 10,000 steps was not originally established through clinical trials proving that this exact number was necessary for good health. The scientific evidence came later, while the target had already gained popularity.
According to The BMJ, the figure became widely recognised through the Japanese campaign rather than emerging from a scientific discovery. Over time, pedometers, fitness trackers, smartphones and workplace challenges helped turn it into a familiar benchmark.
And it stuck. There is something wonderfully human about preferring a clear target to a complicated explanation. Ten thousand feels like a mission. Six thousand feels like an unfinished spreadsheet.
Does that mean walking 10,000 steps is pointless? Absolutely not. Walking regularly supports health, and increasing activity can be beneficial, particularly for people who spend much of the day sitting. The problem is treating one round number as a universal medical requirement.
Research published in JAMA Internal Medicine in 2019 found that, among older women studied, taking around 4,400 steps daily was associated with a lower risk of death than taking around 2,700. The association levelled off at approximately 7,500 steps in that study. Results from one group do not establish the perfect target for everyone, but they show that meaningful benefits can occur below 10,000.
The takeaway? Aim to move more, build a routine you can maintain and adapt your goals to your circumstances. Missing an arbitrary number on your watch is not a moral failure.
For more curious explainers about everyday myths and surprising facts, explore Thisclaimer at thisclaimer.com and its YouTube channel. Because sometimes the real story behind a modern habit is far more interesting than the habit itself.
Sources
The BMJ — “Sixty seconds on… 10 000 steps” — https://www.bmj.com/content/384/bmj.q598
Ethnographiques.org — “Taking 10,000 steps a day – really? A survey of ordinary self-tracking practices” — https://shs.cairn.info/article/E_RES_216_0157/pdf?lang=en
Cairn.info
JAMA Internal Medicine — “Association of Step Volume and Intensity With All-Cause Mortality in Older Women” — https://jamanetwork.com/journals/jamainternalmedicine/fullarticle/2734709
Step Counting: A Review of Measurement Considerations and Health-Related Applications — https://pmc.ncbi.nlm.nih.gov/articles/PMC5488109/
Thisclaimer — https://thisclaimer.com/
Thisclaimer YouTube — https://www.youtube.com/@thisclaimer?sub_confirmation=1
The Thisclaimer logo blends a classic warning symbol with a brain icon to represent critical thinking, curiosity, and thoughtful disclaimers #10000Steps #dailyExercise #fitnessMyths #fitnessTrackers #healthFacts #japaneseInventions #pedometerHistory #surprisingHistory #tokyoOlympics #walkingFacts
The future of AI? (2) The older you are …
What is for sure is that AI has a future – it’s among the technologies that will stay for a long time, and dominate an era, or more than just one. Humankind won’t do away with it. And that can be a scary prospect. In a scenario described by "The Economist" in its May 16th edition,
Eventually humans could, like horses in the age of the car, become uneconomical. Income may go mostly or entirely to owners of capital, who then go on to spend it on things that are made by AI and robots using natural resources that they monopolise.
Scenarios elsewhere suggest that AI may do away with all of humankind, capitalists and workers alike.
My current experience with AI is that it is extremely useful. Read here how AI can work for a shortwave listener who listens to programs in languages he doesn’t know himself.
But there are drawbacks. Tibetan isn’t so readable, because there isn’t enough data for bots to learn from. The same may be true for other languages, be it because their use becomes restricted by nationalist governments, be it because parents put an emphasis on more "useful" languages than those they themselve speak as their native one. Besides workers, AI may also throw languages and national identities under the bus.
When the internet became widely used, it raised hopes that it could become empowering. That was before "Facebook", "X" and other platforms of their kind swamped the new medium. Many decades earlier, in the late 1920s, German playwright Bertolt Brecht’s radio theory tried to take stock of the – then brand-new – medium’s potential: instead of broadcasting stale banalities, radio should be "transformed from a distributive into a communication device" (Der Rundfunk ist aus einem Distributionsapparat in einen Kommunikationsapparat zu verwandeln). A few years later, radio became Goebbels’ distributive device. It was a fast negation of the medium’s positive potential.
Thirty-five years after the end of Nazi rule, in 1970, Hans-Magnus Enzensberger built on Brecht’s theories, in his media construction kit. Having seen the use of the medium by the Nazis, he didn’t just see an either positive or a trivial effect of the media, but restrictive and liberating elements alike. Their effect as means of production depended, not least, on the forms of ownership. Capitalists, or the masses?
Your age could play a role, too, when you try to assess the use or the risks of AI. It’s understandable when young people fear AI, even while making use of it themselves. Older people may be more playful. Wang Meng, a Chinese author and former party official born in 1934, certainly is.
Help yourself to a translation!
#artificialIntelligence #broadcasting #dailyprompt #dailyprompt2924 #internet #languages #technology你比如说现在找AI，给咱们刚才的谈话做一个，他完全立刻就可以说他们对那个王蒙老师也是很有了解，很有研究的。王蒙也是热情地回答了他们的问题。
但是毕竟这么简单地谈谈也不可能太深入，也不会有什么特别新的见解。他一定会这么说的。这是一种情况。
但是他有时候又突然特棒的。我写的一首诗里头，其中提到就这样等待着须发变白。他给我分析什么呢？“须发变白并不仅仅是时光过去人变老了。白发是对你的人生经历的，所发给你的荣誉轩冕。而且别处你查不出来！他这一手是厉害。
所以它是很有意思的。但是你从里边要找知识，那就太方便了。 […..] 作为助手行。如果说你要真正我认为将来这是一个标准，如果你一查是那种AI式的作品，那就是表面光光。实际上没有多少创造性地东西。
I wish people could actually watch listen and read this, and with actual comprehension and compassion realize the desperate need to have people actively provide meaningful lasting support;
The Physical Reality of My Existence
Existence is stealing my vision, as constant pain and exhausting reign in this disabled, poverty-stricken corpse. My sight, along with the rest of me, is suffering. Some days things are clear and vibrant for a little while, but more often than not, it's all a dark fuzzy blur that often feels like a shrinking tunnel. The brighter the light the harder it is, and darker light makes fine observations impossible to see. When you couple that with my joints that are actively revolting against me, it makes the mundane an extraordinary feat.
If I sit too long my ankles, knees, and hips lock up; if I stand too long my leg muscles all burn and become stiff. Vertigo keeps me dizzy, and sometimes between bad knees and that, I have issues walking, stooping, or bending down. My hands randomly drop things along with aching all day long, and my blood pressure is on a continuous rollercoaster. Due to poverty, I have a very poor and often absent nutritional uptake, so my body simply ages ten times faster than the average person. I tell people I am 48 but more like an 80-year-old man, and they simply cannot wrap their heads around it. It takes me an hour or two in the morning before my legs work, and often three to four before my eyes focus and my brain is fully functioning.
The Cycle of Sleeplessness and Decline
If I lay down in my torture device of a bed—a mattress that is 20 years old and completely useless for support, with no room for a couch or recliner to alternate to—everything goes haywire. My wrists and hands go numb as my shoulders and back ache, and trying to upright myself seems to take days. The more I do, the less I sleep. When I am past tired, I won't actually sleep at all; I will simply get aggravated by the circumstances.
Every movement, every breath, seems to become a battle that simply lasts too long. My overall mental executive cognitive functions are declining at a noticeable rate, and my thoughts are fading and fraying more each day. It is very much tiring to be me.
The Isolation and Misunderstanding
I really don't feel well, I am exhausted, I am in pain, and my anxiety is bothering me. I am plum wore out from it all, and sadly, people simply do not understand, nor do they even attempt to feign empathy or compassion if they cannot express it naturally. It gets really old explaining over and over that I am disabled and I am aging, which means my disabilities just get worse.
They see me helping and doing what I can when I can, and assume it is all easy for me and no big deal, yet have no clue of the physical pain and constant exhaustion. It is infuriating when people think you can just do A, B, C, etc., despite you making it clear you cannot. I have no family to call on and no friends to rely on.
The Crushing Weight of Poverty
I exist in poverty because I am disabled, and every facet of my life hangs on a precarious precipice. My tiny cave is a mess; I really need to organize and clean, but between physical energy not being there and financially not able to obtain what I need to do so, everything is chaos.
My bowels constantly complain there is no food in here. I fight with what I can eat today versus can I afford to take a shower and will I have clean clothes to put on. From the constant need for food I can never afford, to underwear, socks, shoes, pants, shirts, and personal hygiene, there is so much I truly need and no real way to obtain any of it. My near non-existent disability income cannot cover even a quarter of life today, and I have no safety at all. For if I was an actual corpse this decay would seem okay, but as I am somehow still alive, simply existing is becoming more than I can bear.
My Plea for Dignity and Support
This disabled man existing in poverty is really, truthfully struggling. I am exhausted mentally, spiritually, and physically. It is imperative that I raise the money I need to buy property to build my own forever home, so that I have security and stability. I need a massive infusion of cash to get myself caught up, and then I need a monthly support amount to stay somewhat stable.
I have never expected one person to bear the brunt of my burdens; rather, I hope that all will help how they can, with the compassion, empathy, and understanding that if it was them in need, would they not pray for the same? If only humanity was not a failure, maybe I could actually raise the money I need to live beyond barely existing. And if I am lucky, I will be able to help others through the rest of my life by having my own place to offer them the help they may need.I have had a very hard life. How much longer must I be forced to fight and endure an existence void of compassion, empathy, support, respect, dignity, and safety? I am begging for help to live, I am begging for compassion and dignity. Please, I am not in a good place. Please help me climb out of this hell of desperation today.
This Disabled Man Existing In Poverty, Is $8,505 Away From Being Able To Afford To Take Care Of Myself And The Things I Still Need To Take Care Of Right Now. Your support today could mean the difference between nourishment and starvation and some kind of stability.
This is not a request for luxury. This is a cry for dignity.
Urgent need: $27,305, Monthly survival: $1,500, Long-term liberation: $25,000 to climb out. $5 million to build a forever home and sanctuary for others like me.
If you’ve ever wondered what despair looks like, this is it. If you’ve ever wanted to make a real difference, this is your chance $5-10-15 It All Helps,
🔗 Donate here: paypal.com/donate?campaign_id=… 💸 CashApp: $woctxphotog
#MutualAid, #Disabled, #Poverty, #Help, #Survival, #Compassion, #Pain, #MentalHealth, #Food, #Groceries, #Hygiene, #Anxiety, #PTSD, #Bipolar, #Dignity, #Disablity, #Life, #Housing, #Support, #Aging, #Love, #Empathy, #Health, #Rent, #Cronicillness, #dentalhealth, #healthcare, #dental, #Emergency, #oralhealth,
Stop sharing your credentials with agents — per-agent identity is here, and here's the order to fix things in.
Disclosure: some links in the original are affiliate links, and we may earn a commission if you buy through them — at no extra cost to you. It doesn't change our analysis, and the security advice below is the same advice we'd give with no links at all.
You gave an agent a job. To do it, the agent needed to log in somewhere — a dashboard, a cloud console, a bank, a SaaS tool. So you did what almost every developer has done this year: you handed it your password, or a key that works just like one. It is probably still sitting in a prompt, a script, or a .env file you meant to clean up later. That is the quiet security debt of the agent era. Your agents are logging in as you, everywhere — and the institutions on the other end have started to notice.
How we put this together
We based this piece on vendor launch materials from 1Password and IDENTOS, reporting by Axios on bank responses to agentic activity, and 1Password's Developer Pulse survey of developers. Where a claim comes from a vendor — launch features, plan inclusion, partner lists, survey results — we label it as a vendor claim or cite the source by name. We have not hands-on tested 1Password for Agents or IDENTOS PolicyArc; this is researched analysis, not a product review.
Verdict
Stop sharing your own credentials with agents, starting now. Give each agent its own identity, scoped to one task, for a limited time, with a log you can read and a revoke button that works. Per-agent identity is becoming the default — 1Password for Agents and IDENTOS PolicyArc, both launched this week, are early, concrete versions of it. Fix in this order: inventory what your agents can reach, kill shared passwords, then add scoping, expiry, and audit.
Why banks are suddenly interested in your agents
Start with the bank's point of view, because it explains everything else.
According to Axios reporting, US banks are detecting unverified agentic activity on customer accounts. Chase has warned customers not to share their credentials with third-party agents. Read that warning carefully. The bank is not making a philosophical point about AI. It is telling you that when an automated agent signs in with your username and password, the bank cannot verify who — or what — is actually on the other end.
Mechanically, the bank is right. A legitimate agent using your password and a criminal using your stolen password produce nearly identical signals: correct credentials, an unfamiliar device or location, odd hours, rapid navigation, no human typing pattern. Fraud systems were built to flag exactly that shape of activity. Your agent does not look like innovation to a risk engine. It looks like account takeover that happens to be polite about it.
That distinction matters for you even if you never automate a bank login. The same pattern is now playing out across cloud consoles, payment dashboards, ad accounts, and production SaaS tools. When something goes wrong — a bad transaction, a deleted resource, a leaked export — the audit log will say you did it. Because as far as the system is concerned, you did. You gave the agent your identity, so every action it takes inherits your name, your permissions, and your liability.
And developers are doing this at scale, under real pressure to keep doing it. In 1Password's Developer Pulse survey, 65% of developers said they are expected or encouraged to use AI agents. Only 33% said they have a secure way to let agents sign in. That gap — between "you must use agents" and "here is a safe way to give them access" — is where passwords end up in prompts. It is not carelessness, mostly. It is a missing piece of infrastructure. This week, two companies shipped attempts to fill it.
The five ways agents sign in today, compared
There are really only five patterns in use right now. They are not equally good, and we are not going to pretend they are. Here they are, worst to best, with the two launches from this week placed where they belong.
1. Your shared password — the worst option, and still the most common
How it works: You give the agent your actual username and password. It stores them in a prompt, a script, a config file, or its own memory, and signs in exactly as you would.
Strength: It works with everything, immediately, with zero setup. That is the entire list of strengths.
Weakness: Everything else. The credential has your full permissions — no scoping, no expiry, no way to tell agent actions from your actions in a log. If the prompt leaks, the password leaks. If the agent is compromised, you are compromised. Rotating the password breaks every agent using it, so nobody rotates it. If you are doing this today, you are not alone — but you should treat it as an incident waiting for a date, not a workflow.
2. Long-lived API keys — better than a password, worse than you think
How it works: Instead of your password, the agent carries an API key — often created under your account, often with broad permissions, often valid until someone remembers to delete it.
Strength: At least it is separate from your human login, and most platforms let you revoke a key without changing your password. For machine-to-machine calls to a single API, this is a reasonable baseline.
Weakness: "Long-lived" is the problem. Keys get copied into repos, CI logs, screenshots, and chat transcripts. They rarely expire, rarely get scoped tightly, and rarely have a human in the loop when they are used. A leaked long-lived key with broad scope is a password with better branding.
3. Scoped, short-lived tokens — the right shape
How it works: The agent gets an OAuth-style token limited to specific permissions, for a specific service, for a short window — minutes or hours, not months. When the window closes, the token dies and a new one must be issued.
Strength: This is the pattern security teams actually want. Least privilege by default, automatic expiry, and a much smaller blast radius if a token leaks. A stolen token that expires in an hour and can only read one project is a bad day. A stolen password is a bad quarter.
Weakness: Support is uneven. Plenty of tools your agents need still do not offer fine-grained, short-lived tokens, and wiring up issuance and refresh for every agent and every service is real engineering work. The pattern is right; the ecosystem is still catching up.
4. Per-agent keys with human approval — 1Password for Agents
How it works: Each agent gets its own identity instead of borrowing yours. 1Password for Agents, launched October 22, 2026, is the clearest consumer-and-developer example so far. As 1Password describes it — a vendor claim, based on its launch materials — each AI agent signs in with its own unique digital key, you approve every sign-in attempt on your own device, and the actual password never reaches the agent. 1Password lists the feature as included in its Individual and Family plans via 1Password.com.
1Password names its launch partners as rolling out, including Meta's Muse and Grok Bot, with Claude Duet, ChatGPT Work/dots, and Townie listed as coming soon. It also says integrations are being built by Browserbase, Browser Use, Perplexity, and Ramp. Treat that partner list as a vendor roadmap claim until each integration is live and documented — but note the shape of it: browser agents and finance tooling are exactly where credential-sharing risk is highest.
Strength: The password never reaches the agent, every sign-in needs your approval on your device, and each agent is distinguishable from you and from every other agent. Revoking one agent does not mean changing your password everywhere.
Weakness: Human approval does not scale forever. Approving every sign-in works for high-value logins; it will chafe for agents that authenticate constantly in the background. And you are trusting one vendor's vault and approval flow with the keys to a lot of doors — convenient, and a concentration risk you should choose with your eyes open.
5. Policy and audit engines — IDENTOS PolicyArc
How it works: Instead of managing credentials agent by agent, you define policy in one place: who and what can access which resources, for which tasks, for how long — and you get an audit trail across all of it. IDENTOS PolicyArc, which reached general availability on October 23, 2026, is positioned exactly there. As IDENTOS describes it — a vendor claim from its launch materials — PolicyArc is one place to define, enforce, and audit access policy for people and agents, with task-specific, time-limited access grants.
Strength: This is the enterprise-grade answer to the real question, which is not "how does this one agent log in?" but "what is every agent in this organization allowed to reach, and can we prove it later?" Central policy, time limits, and audit in one system is what compliance and security teams will ask for.
Weakness: Weight. A policy engine is infrastructure to evaluate, buy, integrate, and operate. For a solo developer or a three-person team, it can be more machine than the problem needs today. It also only governs the systems you connect to it — an agent with your password typed into a prompt is outside the policy no matter how good the engine is.
Our ranking, plainly: shared passwords are last, and it is not close. Long-lived keys are a distant fourth. Scoped, short-lived tokens are the baseline every developer should aim for today. Per-agent keys with human approval rank first for individual developers and small teams right now, because they fix the worst failure — password exposure — without a platform rebuild. Policy and audit engines rank first for organizations managing many agents across many people, where the audit trail is the point. Pick based on your scale, but do not pick option one.
What to do this week
You do not need to buy anything to start. You need an inventory and the willingness to delete some credentials. Work through this in order — and if you want a structured pass, run our Agent Access Readiness checklist on Pick a Tools alongside it, then read the broader background in our AI Agent Identity hub.
When the inventory is done, score yourself honestly with the Agent Access Readiness tool and fix the lowest-scoring area first. The goal for this week is not perfection. It is making sure no agent anywhere is signing in with your personal password.
The honest limits
Some restraint is warranted, because this category is three days old in its current shape and the marketing is running ahead of the standards.
The standards are unsettled. There is no single, widely adopted protocol for agent identity yet. What 1Password ships, what IDENTOS ships, and what the browser-agent platforms build may converge — or may leave you migrating between incompatible approaches in a year. Early adoption buys you safety now at the price of some rework later. For the password-sharing problem, that trade is still worth it. For a full platform commitment, go in knowing it.
Platform lock-in is a real risk. If one vault holds every agent key and one vendor's approval flow gates every sign-in, leaving that vendor becomes a project, not a settings change. That may be an acceptable trade — password managers already hold that position in most of our lives — but count it as a cost, not a footnote.
Small teams may not need an enterprise policy engine yet. If you are two developers with four agents, a written inventory, scoped tokens, and a calendar reminder to rotate keys will carry you further than a policy platform you have not finished integrating. Buy the layer that matches the number of agents and people you actually have. PolicyArc-class tooling earns its keep when "who approved this agent's access, and when does it expire?" becomes a question you cannot answer from memory.
And this is a developer story first, a consumer story later. The Developer Pulse numbers describe developers because developers are the ones wiring agents into real systems today. Consumers handing agents their banking passwords are the next wave of the same problem — which is precisely why the Chase warning matters. The tooling will follow the developers down-market. Your job is to not still be sharing passwords when it arrives.
The bottom line has not changed since the first paragraph. Agents are useful, agents are not going away, and agents need to sign in to things. All of that can be true while "sign in as me, with my password, forever" is a bad answer. This week gave developers the first mainstream alternatives. Use them — starting with the unglamorous work of listing what your agents can reach, and taking your own password back.
FAQ
How do AI agents log in today?
Most agents today log in with credentials borrowed from a person: a shared password, a long-lived API key pasted into a prompt or .env file, or a broad OAuth token. Newer approaches give each agent its own scoped, short-lived credential, or a per-agent key that requires human approval for every sign-in.
What is 1Password for Agents?
1Password for Agents, launched October 22, 2026, is a feature where each AI agent signs in with its own unique digital key instead of your password. You approve every sign-in attempt on your own device, and the actual password never reaches the agent. 1Password lists it as included in its Individual and Family plans.
Why are banks flagging agent activity?
According to Axios reporting, US banks are detecting unverified agentic activity on accounts. An agent signing in with your password from an unfamiliar location or automation pattern is mechanically indistinguishable from account takeover fraud, which is why Chase has warned customers not to share credentials with third-party agents.
What is an agent identity?
An agent identity is a distinct, revocable identity for a single AI agent — separate from any human user — with its own credential, limited permissions, and an audit trail. It lets you grant task-specific, time-limited access and revoke that one agent without changing your own password or breaking other tools.
What should a developer do first?
Inventory every agent you run and what it can reach, then kill shared credentials first. Move agents to scoped, short-lived, or per-agent credentials, add time limits and audit logs, and make sure you can revoke any single agent in one click.
What is IDENTOS PolicyArc?
IDENTOS PolicyArc, which reached general availability on October 23, 2026, is described by IDENTOS as a single place to define, enforce, and audit access policy for people and agents, including task-specific, time-limited access grants.
Originally published on Pick a Tools.#security #ai #programming #devops #software #coding #development #engineering #inclusive #community
Your AI Agents Are Logging In With Your Password. Banks Have Noticed.