aiolabs/castle
1
0
Fork 0
Code Issues 5 Pull requests 2 Projects Releases 5 Packages Wiki Activity Actions

Obscure user IDs in accounting display #7

New issue
Open
opened 2026-01-10 13:08:28 +00:00 by padreug · 0 comments
padreug commented 2026-01-10 13:08:28 +00:00
Owner
Copy link

Feature Request

Reduce the visibility of user IDs in accounting entries and displays.

Current Behavior

User accounts and transactions currently display user ID prefixes (e.g., User-e2598a84), which exposes internal identifiers.

Proposed Changes

Options to consider:

  • Use shorter ID prefixes (e.g., 4 characters instead of 8)
  • Replace with user-friendly aliases or display names
  • Use pseudonymous identifiers that map internally to real user IDs
  • Only show full IDs to super users, show masked versions to others

Benefits

  • Improved privacy for users
  • Cleaner accounting display
  • Less technical-looking interface
  • Reduced exposure of internal system identifiers

Considerations

  • Must maintain unique identification for accounting integrity
  • Super users may still need access to full IDs for debugging
  • Beancount account names need to remain valid and unique
## Feature Request Reduce the visibility of user IDs in accounting entries and displays. ## Current Behavior User accounts and transactions currently display user ID prefixes (e.g., `User-e2598a84`), which exposes internal identifiers. ## Proposed Changes Options to consider: - Use shorter ID prefixes (e.g., 4 characters instead of 8) - Replace with user-friendly aliases or display names - Use pseudonymous identifiers that map internally to real user IDs - Only show full IDs to super users, show masked versions to others ## Benefits - Improved privacy for users - Cleaner accounting display - Less technical-looking interface - Reduced exposure of internal system identifiers ## Considerations - Must maintain unique identification for accounting integrity - Super users may still need access to full IDs for debugging - Beancount account names need to remain valid and unique
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
fix/authorization-security-refactor
fix/concurrency-protection
v0.0.5
v0.0.4
v0.0.3
v0.0.2
v0.0.1
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: aiolabs/castle#7
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?