No description
padreug
0da23e9332
Key changes:
- Add notification store with path-based wildcard support (chat/*, chat/{pubkey}, *)
- Remove UnreadMessageData interface and processedMessageIds Set tracking
- Implement timestamp-based "seen at" logic with wildcard matching
- Add markAllChatsAsRead() for batch operations
- Integrate ChatNotificationConfig for module configuration
- Create useNotifications composable for easy notification access
Benefits:
- Simpler architecture (removed processedMessageIds complexity)
- Flexible wildcard-based "mark as read" operations
- Future-proof for Primal-style backend sync
- User-scoped storage via StorageService
- Clean separation of concerns
refactor: enhance chat service with activity tracking and sorting
- Updated the ChatService to track lastSent, lastReceived, and lastChecked timestamps for peers, improving message handling and user experience.
- Implemented sorting of peers by last activity to prioritize recent conversations.
- Adjusted message handling to update peer activity based on message direction.
- Ensured updated peer data is saved to storage after modifications.
These changes streamline chat interactions and enhance the overall functionality of the chat service.
refactor: improve ChatService and notification store initialization
- Updated ChatService to ensure the notification store is initialized only after user authentication, preventing potential errors.
- Introduced a new method to safely access the notification store, enhancing error handling.
- Enhanced peer activity tracking by calculating last activity based on actual message timestamps, improving sorting and user experience.
- Added debounced saving of notification state to storage, optimizing performance and reducing unnecessary writes.
- Improved logging for better debugging and visibility into notification handling processes.
These changes enhance the reliability and efficiency of the chat service and notification management.
refactor: clean up logging in ChatService and notification store
- Removed unnecessary console logs from ChatService to streamline the code and improve performance.
- Simplified the initialization process of the notification store by eliminating redundant logging statements.
- Enhanced readability and maintainability of the code by focusing on essential operations without excessive debug output.
These changes contribute to a cleaner codebase and improved performance in chat service operations.
FIX BUILD ERRORS
refactor: update chat module notification configuration
- Refactored the notification settings in the chat module to use a nested structure, enhancing clarity and organization.
- Introduced `wildcardSupport` to the notification configuration, allowing for more flexible notification handling.
- Maintained existing functionality while improving the overall configuration structure.
These changes contribute to a more maintainable and extensible chat module configuration.
refactor: optimize ChatComponent and ChatService for improved performance
- Removed unnecessary sorting of peers in ChatComponent, leveraging the existing order provided by the chat service.
- Updated the useFuzzySearch composable to directly utilize the sorted peers, enhancing search efficiency.
- Cleaned up logging in ChatService by removing redundant console statements, streamlining the codebase.
- Added critical checks to prevent the current user from being included in peer interactions, improving user experience and functionality.
These changes contribute to a more efficient and maintainable chat module.
refactor: simplify message publishing in ChatService
- Removed unnecessary variable assignment in the message publishing process, directly awaiting the relayHub.publishEvent call.
- This change streamlines the code and enhances readability without altering functionality.
These modifications contribute to a cleaner and more efficient chat service implementation.
|
||
|---|---|---|
| .vscode | ||
| docs | ||
| electron | ||
| public | ||
| src | ||
| .cursorrules | ||
| .env.example | ||
| .gitignore | ||
| CLAUDE.md | ||
| components.json | ||
| forge.config.js | ||
| index.html | ||
| nginx.conf.example | ||
| package-lock.json | ||
| package.json | ||
| README.md | ||
| tailwind.config.js | ||
| test-formatting.html | ||
| tsconfig.app.json | ||
| tsconfig.json | ||
| tsconfig.node.json | ||
| vite.config.ts | ||
Ario Web App
A modular Vue 3 + TypeScript application with Nostr protocol integration and Lightning Network wallet functionality.
Features
- Modular Architecture: Plugin-based system with dependency injection
- Nostr Integration: Decentralized social networking and messaging
- Lightning Wallet: Real-time balance updates with LNbits WebSocket integration
- Event Ticketing: Lightning-powered event tickets and marketplace
- PWA Support: Progressive Web App with offline capabilities
- Desktop App: Electron-based desktop application
Real-Time Wallet Features
The application provides seamless Lightning Network wallet integration:
- Lightning Invoice Creation: Create BOLT11 invoices for receiving payments with QR codes
- Smart Payment Scanning: QR code scanner for Lightning invoices, LNURL, and Lightning addresses
- Universal Payment Support: Send to Lightning invoices, Lightning addresses (user@domain.com), and LNURL
- Smart Amount Fields: Amount input only appears when needed (LNURL, Lightning addresses, or zero-amount invoices)
- Instant Balance Updates: WebSocket connection provides real-time balance updates when payments are sent or received
- Live Notifications: Toast notifications for incoming payments
- Connection Management: Automatic reconnection with exponential backoff
- Battery Optimization: Pauses WebSocket when app is not visible to save battery
- Multi-Wallet Support: Manages multiple Lightning wallets with the first wallet as default
WebSocket Configuration
Configure WebSocket behavior in src/app.config.ts:
modules: {
wallet: {
enabled: true,
config: {
websocket: {
enabled: true, // Enable/disable real-time updates
reconnectDelay: 1000, // Initial reconnection delay (ms)
maxReconnectAttempts: 5 // Maximum reconnection attempts
}
}
}
}
Development
# Install dependencies
npm install
# Start development server with hot reload
npm run dev
# Build for production
npm run build
# Run Electron desktop app
npm run electron:dev
Environment Setup
Required environment variables:
# LNbits server URL for Lightning wallet functionality
VITE_LNBITS_BASE_URL=http://localhost:5000
# Nostr relay configuration (JSON array)
VITE_NOSTR_RELAYS='["wss://relay1.example.com","wss://relay2.example.com"]'
Architecture
The application follows a modular architecture with the following core modules:
- Base Module: Authentication, Nostr client, PWA functionality
- Wallet Module: Lightning payments, WebSocket balance updates, transaction management
- Events Module: Event ticketing with Lightning payment integration
- Market Module: Nostr marketplace functionality
- Chat Module: Encrypted messaging via Nostr
For detailed development guidelines, see CLAUDE.md.