#ListUsers
if i want to cache that, i'd annotate the listUsers function somehow. decorators, jsdoc, imaginary funcs, whatever you prefer that the build process can pick out and understand. the runtime RPC logic would be setup with the right cache impl on whatever end (cli/serv) you configured
November 3, 2025 at 10:05 PM
Managing user accounts is an important part of Linux administration. Knowing how to list users in CentOS 10 will help you monitor activity and troubleshoot effectively.

Learn more:
greenwebpage.com/community/ho...

#ListUsers #CentOS10 #LinuxAdministration #GreenWebpage
How to List All Users on CentOS 10 - Greenwebpage Community
This guide will explore the different ways to list users in CentOS 10. We'll cover cat, getent, awk, compgen, and many more.
greenwebpage.com
November 19, 2025 at 4:53 AM
🚨 EUVD-2026-44954
📊 4.3/10
🏢 yamcs

📝 Yamcs is a mission control framework. Prior to 5.12.7, the IAM API endpoints listUsers, getUser, listGroups, and getGroup in yamcs-core did not enforce the ...

🔗 https://euvd.enisa.europa.eu/vulnerability/EUVD-2026-44954

#cybersecurity #infosec #cve #euvd
July 16, 2026 at 6:01 PM
I wonder if apfs syncPatchUsers or apfs listUsers may be of any use.
February 24, 2025 at 8:18 PM
:sparkles: Ozone team member manager (#2460)
:sparkles: Ozone team member manager (#2460) · bluesky-social/atproto@3ad0519
:sparkles: Ozone team member manager (#2460) * :construction: Proposal for moderator manager lexicons * :sparkles: CRUD for moderator management works * :sparkles: Add profile view to moderator user list * :sparkles: Seed mod users from env var to db * :white_check_mark: Adjust tests * :white_check_mark: Update snapshots * :sparkles: Fix type and lexicon token issues * :sparkles: Add pagination to listUsers * :sparkles: Use sort order in pagination * :memo: Change error name * :white_check_mark: Update snapshots * :white_check_mark: seed mods in sync to avoid re-order * :broom: Remove unnecessary import * :bug: Re-run codegen * :broom: Some cleanup * :broom: Cleanup unnecessary properties on auth-verifier * :sparkles: Rename terminologies from moderator to team and member * :broom: Cleanup * :sparkles: Allow admin tokens to update/add member * :sparkles: Delete members in transaction * :sparkles: Use db transactions and move profile hydration to the service layer * :white_check_mark: Add test for addMember endpoint * :bug: wait on adding admin DID * :sparkles: Do not allow updating/deleting service owner and always give service owner admin access * :broom: Cleanup * :sparkles: Make timestamp columns non null * :broom: Cleanup * :sparkles: Update mod role definition in getConfig * :sparkles: Deletion and update guards * :bug: don't prefill service did * :memo: Add changeset
github.com
June 18, 2024 at 11:43 PM
because, in this case of `listUsers`, im seeing it as "choose a caching strategy for this function". the fw/tools implement that in runtime code for you

if for w/e reason i wanted to cache that clientside unknown to the server, i'd write separate explicit client-only code (by choice)
November 3, 2025 at 11:23 PM
e.g. `listUsers()` is a func defined entirely in `users.server.ts`. when i author my client code, i import from that file and call `await listUsers()`. under the hood, RPC or whatever preferred form of comms to call the real thing at runtime
November 3, 2025 at 10:04 PM