Patrick Britton 3c4680bdd7 Initial commit: Complete threaded conversation system with inline replies

**Major Features Added:**
- **Inline Reply System**: Replace compose screen with inline reply boxes
- **Thread Navigation**: Parent/child navigation with jump functionality
- **Chain Flow UI**: Reply counts, expand/collapse animations, visual hierarchy
- **Enhanced Animations**: Smooth transitions, hover effects, micro-interactions

 **Frontend Changes:**
- **ThreadedCommentWidget**: Complete rewrite with animations and navigation
- **ThreadNode Model**: Added parent references and descendant counting
- **ThreadedConversationScreen**: Integrated navigation handlers
- **PostDetailScreen**: Replaced with threaded conversation view
- **ComposeScreen**: Added reply indicators and context
- **PostActions**: Fixed visibility checks for chain buttons

 **Backend Changes:**
- **API Route**: Added /posts/:id/thread endpoint
- **Post Repository**: Include allow_chain and visibility fields in feed
- **Thread Handler**: Support for fetching post chains

 **UI/UX Improvements:**
- **Reply Context**: Clear indication when replying to specific posts
- **Character Counting**: 500 character limit with live counter
- **Visual Hierarchy**: Depth-based indentation and styling
- **Smooth Animations**: SizeTransition, FadeTransition, hover states
- **Chain Navigation**: Parent/child buttons with visual feedback

 **Technical Enhancements:**
- **Animation Controllers**: Proper lifecycle management
- **State Management**: Clean separation of concerns
- **Navigation Callbacks**: Reusable navigation system
- **Error Handling**: Graceful fallbacks and user feedback

This creates a Reddit-style threaded conversation experience with smooth
animations, inline replies, and intuitive navigation between posts in a chain.

2026-01-30 07:40:19 -06:00

1.3 KiB

Raw Blame History

Supabase Clean-up Intel

Overview

The supabase folder has been moved to c:\Webs\Sojorn\_legacy\supabase. This folder contains the legacy backend logic (Edge Functions) and database migrations that were used before the migration to the Go backend.

Key Components

1. Edge Functions (`supabase/functions/`)

Contains the TypeScript source for the original serverless functions. Use these as a reference if any logic is missing in the Go backend.

publish-post, feed-personal -> internal/handlers/post_handler.go
follow, block -> internal/handlers/user_handler.go
tone-check -> internal/handlers/analysis_handler.go
notifications -> internal/services/push_service.go or notification_handler.go

2. Migrations (`supabase/migrations/` & Root SQLs)

The supabase/migrations folder contains the initial schema definitions.

go-backend/internal/database/migrations is the new source of truth.
Root SQL files (e.g., check_index.sql, setup_cms.sql) have been moved to c:\Webs\Sojorn\migrations_archive.
apply_e2ee_migration.sql (in _legacy/supabase) contained the E2EE schema changes that were recently applied.

3. Verification

If any "sanity check" is needed, compare the Go handlers against the logic in supabase/functions/<name>/index.ts.

1.3 KiB Raw Blame History