beclab/Olares
Mar 2025 – Jun 2026
16 Months active
Languages Used
YAMLNginxshyamlgoMarkdownDockerfileJavaScript
Technical Skills
ContainerizationDevOpsHelmKubernetesConfiguration ManagementNginx Configuration
wiy
PROFILE
Wiy
Over 16 months, contributed to the beclab/Olares repository by building and maintaining a robust, scalable platform for file management, user authentication, and real-time collaboration. Leveraged Go, Node.js, and Kubernetes to deliver features such as multi-node file services, Redis-backed user data, and CLI tools for advanced file operations. Focused on deployment reliability through Helm-based upgrades, Docker image management, and CI/CD pipelines, while enhancing security and user experience with authentication hardening and UI improvements. Addressed bugs in backup, uploads, and network configuration, ensuring stable releases. Emphasized maintainability with code refactors, comprehensive testing, and detailed documentation updates throughout the project.
Overall Statistics
Feature vs Bugs
70%Features
Repository Contributions
138Total
Bugs
16
Commits
138
Features
37
Lines of code
683,886
Activity Months16
Your Network
27 peopleSame Organization
@bytetrade.io4
Work History
June 2026
9 Commits • 3 Features
Jun 1, 2026June 2026 monthly summary focusing on key accomplishments and business impact across the beclab/Olares repo. Delivered major frontend/backend image updates, enhanced CLI capabilities (archive management and full-content search), and reliability/performance improvements enabling faster feature delivery and improved user experience.
9 Commits • 3 Features
Jun 1, 2026June 2026 monthly summary focusing on key accomplishments and business impact across the beclab/Olares repo. Delivered major frontend/backend image updates, enhanced CLI capabilities (archive management and full-content search), and reliability/performance improvements enabling faster feature delivery and improved user experience.
June 2026
May 2026
18 Commits • 2 Features
May 1, 2026May 2026 focused on delivering business value through up-to-date system images, safer and more productive CLI tooling, and robust file workflows across the Olares suite. Highlights include: (1) System Image Upgrades and Codebase Enhancements delivering newer system-frontend images (v1.10.22–v1.10.34), Docker/Node.js/Nginx refinements, and a major code refactor that stabilizes configs and improves security posture. (2) CLI Enhancements, Hardening, and UX Improvements adding NewCmdFrp, files chown/edit, preflight checks, and path-traversal protections, with tests and updated SKILL docs. (3) Bug Fixes addressing non-standard HTTP 459 auth errors and directory upload regression for namespace root paths, plus regression tests. (4) Market/UX parity improvements across the CLI with install-state filtering and UX naming changes (market list --installed renamed to --mine, etc.). (5) Tests and documentation investments ensuring error messaging, preflight validation, and safety guarantees are well covered. Overall impact: improved reliability, security, and developer productivity; reduced user friction in file operations; safer interactions with external AI mountpoints; and faster deployment of updates.
May 2026
18 Commits • 2 Features
May 1, 2026May 2026 focused on delivering business value through up-to-date system images, safer and more productive CLI tooling, and robust file workflows across the Olares suite. Highlights include: (1) System Image Upgrades and Codebase Enhancements delivering newer system-frontend images (v1.10.22–v1.10.34), Docker/Node.js/Nginx refinements, and a major code refactor that stabilizes configs and improves security posture. (2) CLI Enhancements, Hardening, and UX Improvements adding NewCmdFrp, files chown/edit, preflight checks, and path-traversal protections, with tests and updated SKILL docs. (3) Bug Fixes addressing non-standard HTTP 459 auth errors and directory upload regression for namespace root paths, plus regression tests. (4) Market/UX parity improvements across the CLI with install-state filtering and UX naming changes (market list --installed renamed to --mine, etc.). (5) Tests and documentation investments ensuring error messaging, preflight validation, and safety guarantees are well covered. Overall impact: improved reliability, security, and developer productivity; reduced user friction in file operations; safer interactions with external AI mountpoints; and faster deployment of updates.
April 2026
10 Commits • 3 Features
Apr 1, 2026Beclab/Olares — April 2026 quarterly/monthly summary: Delivered major platform deployment and stability updates across olares-app, wizard, auth-front, and monitoring by consolidating deployment, Docker image management, and service version upgrades to the v1.10.x line (from v1.10.10 to v1.10.19). This included multi-component image bumps and container updates to ensure the latest features, security fixes, and operational stability with minimal downtime. Implemented User Authentication hardening and URL handling refactor to centralize login URL construction using the olares package, improving security, maintainability, and reliability for vault and desktop environments; updated first/second factor TOTP flows to rely on unified URL logic. Expanded CLI toolset with new file management commands (copy, move, rename, share) and mkdir for remote directory creation, enhancing productivity and remote file organization; added unit tests to validate behavior. Notable commits across the period include: 738068a631fd423f801657a67e295a4c03ec5595, ce5f11e96273b7a21bd0ecbe8be7d9b7d59d0058, 5cf49d34ae07c5e45f1ecf28be6c1c4ffa8adda0, 160562e7cd389a9175b2ab9e1d8a8079144034ec, 6045255df82c714aa4f0ee364eeccd75841744d0, 4cdf097575e5bf6d89800334f42a1ee6d3e52ca8, fb8ce3815bf8f46de7945036bc2ee09c13d23432, 2b2c0a23c35d06fc95dd7bb83a223387e2cffee8, cc000e1f640070e05e1117eb53b11d8414388e1d, dc876ada71f787a72298b75af14a020a9ac64252.
10 Commits • 3 Features
Apr 1, 2026Beclab/Olares — April 2026 quarterly/monthly summary: Delivered major platform deployment and stability updates across olares-app, wizard, auth-front, and monitoring by consolidating deployment, Docker image management, and service version upgrades to the v1.10.x line (from v1.10.10 to v1.10.19). This included multi-component image bumps and container updates to ensure the latest features, security fixes, and operational stability with minimal downtime. Implemented User Authentication hardening and URL handling refactor to centralize login URL construction using the olares package, improving security, maintainability, and reliability for vault and desktop environments; updated first/second factor TOTP flows to rely on unified URL logic. Expanded CLI toolset with new file management commands (copy, move, rename, share) and mkdir for remote directory creation, enhancing productivity and remote file organization; added unit tests to validate behavior. Notable commits across the period include: 738068a631fd423f801657a67e295a4c03ec5595, ce5f11e96273b7a21bd0ecbe8be7d9b7d59d0058, 5cf49d34ae07c5e45f1ecf28be6c1c4ffa8adda0, 160562e7cd389a9175b2ab9e1d8a8079144034ec, 6045255df82c714aa4f0ee364eeccd75841744d0, 4cdf097575e5bf6d89800334f42a1ee6d3e52ca8, fb8ce3815bf8f46de7945036bc2ee09c13d23432, 2b2c0a23c35d06fc95dd7bb83a223387e2cffee8, cc000e1f640070e05e1117eb53b11d8414388e1d, dc876ada71f787a72298b75af14a020a9ac64252.
April 2026
March 2026
10 Commits • 4 Features
Mar 1, 2026March 2026 monthly summary for beclab/Olares: Delivered deployment and versioning updates across the olares-app stack, implemented UI interaction enhancements, improved development workflows, and refined repository hygiene. Key changes include Docker image and app version bumps (from v1.9.12 through v1.9.25, including related login/notifications updates), UI cursor enhancements for navigation, development environment alignment to the correct test domain, and removal of apps/packages from .gitignore to enable proper version control tracking. Minor UI bug fixes (button cursor behavior and missing styles) improved user experience and reduced interaction friction. These efforts enhanced deployment reliability, security posture, onboarding, and cross-team collaboration while maintaining feature velocity.
March 2026
10 Commits • 4 Features
Mar 1, 2026March 2026 monthly summary for beclab/Olares: Delivered deployment and versioning updates across the olares-app stack, implemented UI interaction enhancements, improved development workflows, and refined repository hygiene. Key changes include Docker image and app version bumps (from v1.9.12 through v1.9.25, including related login/notifications updates), UI cursor enhancements for navigation, development environment alignment to the correct test domain, and removal of apps/packages from .gitignore to enable proper version control tracking. Minor UI bug fixes (button cursor behavior and missing styles) improved user experience and reduced interaction friction. These efforts enhanced deployment reliability, security posture, onboarding, and cross-team collaboration while maintaining feature velocity.
February 2026
5 Commits • 1 Features
Feb 1, 2026February 2026 — Beclab/Olares monthly summary focusing on cross-component release work and value delivery. Executive summary: Delivered the Olares App Version Upgrade Rollout (v1.9.x) across core components, including Docker images for olares-app, login, and user-service, plus the Helm chart. This release ensures users receive the latest features, fixes, and compatibility improvements. Version bumps were synchronized across services, progressing from v1.9.1 to v1.9.6 and captured through a sequence of commits coordinated to keep all artifacts in lockstep. Major bugs fixed: No standalone bug tickets identified for February in this repo. The primary impact was stability and compatibility improvements delivered via the v1.9.x rollout, with risk-reducing changes across services. Overall impact and accomplishments: Strengthened deployment reliability and time-to-value by delivering a coordinated multi-service upgrade, reducing upgrade friction and ensuring end-users benefit from latest features and fixes. Improved release hygiene and traceability across Docker images, login, user-service, and Helm artifacts. Technologies/skills demonstrated: Docker-based image updates, Helm chart deployments, semantic versioning, CI/CD release coordination, cross-service collaboration, and release management." ,
5 Commits • 1 Features
Feb 1, 2026February 2026 — Beclab/Olares monthly summary focusing on cross-component release work and value delivery. Executive summary: Delivered the Olares App Version Upgrade Rollout (v1.9.x) across core components, including Docker images for olares-app, login, and user-service, plus the Helm chart. This release ensures users receive the latest features, fixes, and compatibility improvements. Version bumps were synchronized across services, progressing from v1.9.1 to v1.9.6 and captured through a sequence of commits coordinated to keep all artifacts in lockstep. Major bugs fixed: No standalone bug tickets identified for February in this repo. The primary impact was stability and compatibility improvements delivered via the v1.9.x rollout, with risk-reducing changes across services. Overall impact and accomplishments: Strengthened deployment reliability and time-to-value by delivering a coordinated multi-service upgrade, reducing upgrade friction and ensuring end-users benefit from latest features and fixes. Improved release hygiene and traceability across Docker images, login, user-service, and Helm artifacts. Technologies/skills demonstrated: Docker-based image updates, Helm chart deployments, semantic versioning, CI/CD release coordination, cross-service collaboration, and release management." ,
February 2026
January 2026
6 Commits • 3 Features
Jan 1, 2026January 2026 focused on delivering user-facing reliability improvements, scalable upload handling, and a coordinated deployment upgrade for Olares. We shipped feature enhancements to the olares-app (WebSocket reliability and QR code sizing in the wizard UI), added a total_size parameter for file uploads with a corresponding Infisical deployment image upgrade, and fixed a user-facing upload-limit error message. A synchronized rollout updated core versions across the stack (app/login to v1.7.4, Helm to v1.7.7, Docker image to v1.8.2), ensuring consistency and lowering deployment risk. These changes reduce friction for end users, improve upload throughput, and strengthen our delivery pipeline.
January 2026
6 Commits • 3 Features
Jan 1, 2026January 2026 focused on delivering user-facing reliability improvements, scalable upload handling, and a coordinated deployment upgrade for Olares. We shipped feature enhancements to the olares-app (WebSocket reliability and QR code sizing in the wizard UI), added a total_size parameter for file uploads with a corresponding Infisical deployment image upgrade, and fixed a user-facing upload-limit error message. A synchronized rollout updated core versions across the stack (app/login to v1.7.4, Helm to v1.7.7, Docker image to v1.8.2), ensuring consistency and lowering deployment risk. These changes reduce friction for end users, improve upload throughput, and strengthen our delivery pipeline.
December 2025
16 Commits • 4 Features
Dec 1, 2025December 2025 focused on stabilizing and securing the Olares platform while enabling scalable deployments and improved user experience. Key deliveries include core app upgrades with security hardening and API improvements, file upload readiness, and a deployment infrastructure overhaul that enables more reliable releases. A critical bug fix addressed a payment template ID issue in the notifications API, reducing payment workflow risk. The combined work improves security, reliability, and speed-to-market, delivering measurable business value.
16 Commits • 4 Features
Dec 1, 2025December 2025 focused on stabilizing and securing the Olares platform while enabling scalable deployments and improved user experience. Key deliveries include core app upgrades with security hardening and API improvements, file upload readiness, and a deployment infrastructure overhaul that enables more reliable releases. A critical bug fix addressed a payment template ID issue in the notifications API, reducing payment workflow risk. The combined work improves security, reliability, and speed-to-market, delivering measurable business value.
December 2025
November 2025
3 Commits • 2 Features
Nov 1, 2025Month 2025-11 focused on delivering user-facing sharing capabilities, stabilizing file uploads in sync shares, and refreshing deployment infrastructure. Key features delivered include a new Share File Feature with a dedicated Share Service and a Custom Resource Definition (CRD) to manage share items, enabling users to securely share files and manage shared items. A major bug fix addressed file uploads under sync shares, improving stability and user experience. Deployment and upstream alignment were strengthened by Helm chart upgrades to the latest system-frontend and related services. These changes reduce collaboration friction, increase reliability, and accelerate time-to-value for customers. Technical highlights include CRD design, Helm chart upgrades, and release-version bumps (olares-app: v1.6.1; v1.6.6).
November 2025
3 Commits • 2 Features
Nov 1, 2025Month 2025-11 focused on delivering user-facing sharing capabilities, stabilizing file uploads in sync shares, and refreshing deployment infrastructure. Key features delivered include a new Share File Feature with a dedicated Share Service and a Custom Resource Definition (CRD) to manage share items, enabling users to securely share files and manage shared items. A major bug fix addressed file uploads under sync shares, improving stability and user experience. Deployment and upstream alignment were strengthened by Helm chart upgrades to the latest system-frontend and related services. These changes reduce collaboration friction, increase reliability, and accelerate time-to-value for customers. Technical highlights include CRD design, Helm chart upgrades, and release-version bumps (olares-app: v1.6.1; v1.6.6).
October 2025
8 Commits • 3 Features
Oct 1, 2025October 2025 focused on simplifying deployment, stabilizing asset hosting, and extending platform capabilities. Key outcomes include decommissioning cloud drive support from Helm-based deployments to reduce complexity, migrating asset hosting to a new CDN domain for improved performance and reliability, and delivering a consolidated platform versioning and API extension across olares-app and system frontend with multiple version bumps and a new API endpoint on the user-service-provider. These efforts reduce maintenance overhead, streamline releases, and position the platform for faster feature delivery with clearer hosting semantics and fewer runtime dependencies.
8 Commits • 3 Features
Oct 1, 2025October 2025 focused on simplifying deployment, stabilizing asset hosting, and extending platform capabilities. Key outcomes include decommissioning cloud drive support from Helm-based deployments to reduce complexity, migrating asset hosting to a new CDN domain for improved performance and reliability, and delivering a consolidated platform versioning and API extension across olares-app and system frontend with multiple version bumps and a new API endpoint on the user-service-provider. These efforts reduce maintenance overhead, streamline releases, and position the platform for faster feature delivery with clearer hosting semantics and fewer runtime dependencies.
October 2025
September 2025
13 Commits • 1 Features
Sep 1, 2025September 2025 monthly summary for the Olares beclab repository. Delivered a major multi-service release cycle (v1.x) across System frontend and related components, implemented security and stability improvements, and fixed critical data issues in vault and settings backups. Key outcomes included cross-service version alignment, new environment config HYDRATOR_QUEUE_SIZE, added desktop notification, and RBAC improvements, enabling safer, faster deployments and improved user experience. The vault import bug was fixed by updating olares-app-init to v1.4.39, and the system frontend backup/settings bug fix was addressed with a related user-service image update, improving backup reliability. These efforts reduced release risk, improved data integrity, and demonstrated strong CI/CD and containerization skills.
September 2025
13 Commits • 1 Features
Sep 1, 2025September 2025 monthly summary for the Olares beclab repository. Delivered a major multi-service release cycle (v1.x) across System frontend and related components, implemented security and stability improvements, and fixed critical data issues in vault and settings backups. Key outcomes included cross-service version alignment, new environment config HYDRATOR_QUEUE_SIZE, added desktop notification, and RBAC improvements, enabling safer, faster deployments and improved user experience. The vault import bug was fixed by updating olares-app-init to v1.4.39, and the system frontend backup/settings bug fix was addressed with a related user-service image update, improving backup reliability. These efforts reduced release risk, improved data integrity, and demonstrated strong CI/CD and containerization skills.
August 2025
7 Commits • 2 Features
Aug 1, 2025August 2025: Focused on delivering cross-cutting market data capabilities, upgrading the frontend stack, and hardening security to improve reliability, performance, and data integrity across the Olares suite.
7 Commits • 2 Features
Aug 1, 2025August 2025: Focused on delivering cross-cutting market data capabilities, upgrading the frontend stack, and hardening security to improve reliability, performance, and data integrity across the Olares suite.
August 2025
July 2025
12 Commits • 5 Features
Jul 1, 2025July 2025 performance summary for beclab/Olares focused on scalability, reliability, and deployment discipline, delivering business value through improved data handling, resilient services, and streamlined release processes. Key features delivered: - Files service scalability with multi-node support: transitioned to DaemonSet and updated deployment configs and image versions to enable scalable, fault-tolerant file operations. - Redis-backed user-service data storage and frontend cleanup: moved user data storage to Redis and cleaned up system-frontend/Argo Workflow configurations to simplify ops and improve data access latency. - System release readiness: version bumps for system-frontend and market-backend to unlock new capabilities and ensure compatibility. - Backup reliability enhancements: introduced NATS messaging for backup workflows and applied dashboard fixes to improve monitoring and reliability. - System-wide version alignment and studio removal: harmonized versions across services, removed the studio component from system-frontend and user-service, and updated Helm/Kubernetes configurations to reduce deployment drift. Major bugs fixed: - Redis host dynamic username fix in user-service, resolving connectivity/configuration errors and stabilizing deployments. - Cross-service stability improvements and bug fixes embedded in system-frontend, notification-api, and related components during the version alignment effort. Overall impact and accomplishments: - Significantly improved scalability and resilience of core services, enabling larger workloads with lower risk of outages. - Reduced deployment complexity and operational overhead via version alignment and component removal, accelerating future feature delivery. - Strengthened disaster recovery readiness and observability through NATS-backed backups and dashboard fixes. - Demonstrated end-to-end system modernization across data storage, messaging, and deployment tooling, delivering measurable business value and faster time-to-value for features. Technologies/skills demonstrated: - Kubernetes: DaemonSet, deployments, Helm/Kubernetes configurations - Data storage: Redis integration for user data - Messaging and reliability: NATS-based backup workflows - Release engineering: cross-service version alignment and removal of legacy studio component - Frontend/backend cleanup and system-frontend orchestration
July 2025
12 Commits • 5 Features
Jul 1, 2025July 2025 performance summary for beclab/Olares focused on scalability, reliability, and deployment discipline, delivering business value through improved data handling, resilient services, and streamlined release processes. Key features delivered: - Files service scalability with multi-node support: transitioned to DaemonSet and updated deployment configs and image versions to enable scalable, fault-tolerant file operations. - Redis-backed user-service data storage and frontend cleanup: moved user data storage to Redis and cleaned up system-frontend/Argo Workflow configurations to simplify ops and improve data access latency. - System release readiness: version bumps for system-frontend and market-backend to unlock new capabilities and ensure compatibility. - Backup reliability enhancements: introduced NATS messaging for backup workflows and applied dashboard fixes to improve monitoring and reliability. - System-wide version alignment and studio removal: harmonized versions across services, removed the studio component from system-frontend and user-service, and updated Helm/Kubernetes configurations to reduce deployment drift. Major bugs fixed: - Redis host dynamic username fix in user-service, resolving connectivity/configuration errors and stabilizing deployments. - Cross-service stability improvements and bug fixes embedded in system-frontend, notification-api, and related components during the version alignment effort. Overall impact and accomplishments: - Significantly improved scalability and resilience of core services, enabling larger workloads with lower risk of outages. - Reduced deployment complexity and operational overhead via version alignment and component removal, accelerating future feature delivery. - Strengthened disaster recovery readiness and observability through NATS-backed backups and dashboard fixes. - Demonstrated end-to-end system modernization across data storage, messaging, and deployment tooling, delivering measurable business value and faster time-to-value for features. Technologies/skills demonstrated: - Kubernetes: DaemonSet, deployments, Helm/Kubernetes configurations - Data storage: Redis integration for user data - Messaging and reliability: NATS-based backup workflows - Release engineering: cross-service version alignment and removal of legacy studio component - Frontend/backend cleanup and system-frontend orchestration
June 2025
9 Commits • 2 Features
Jun 1, 2025June 2025 performance highlights for beclab/Olares: Implemented enterprise-grade real-time capabilities via WebSocket across user-service and related components, with corresponding NATS subject configurations. Executed system-wide frontend consolidation and Helm-based upgrades to a unified system-frontend initialization flow, including Nginx path fixes and image upgrades across dashboard, desktop, and system frontends (to v1.3.86). Addressed critical reliability issues in desktop websocket notifications and search functionality, and corrected nginx address path in system-frontend deployment. These changes deliver tangible business value: real-time user interactions, more reliable deployments, and a streamlined ops surface for frontend services.
9 Commits • 2 Features
Jun 1, 2025June 2025 performance highlights for beclab/Olares: Implemented enterprise-grade real-time capabilities via WebSocket across user-service and related components, with corresponding NATS subject configurations. Executed system-wide frontend consolidation and Helm-based upgrades to a unified system-frontend initialization flow, including Nginx path fixes and image upgrades across dashboard, desktop, and system frontends (to v1.3.86). Addressed critical reliability issues in desktop websocket notifications and search functionality, and corrected nginx address path in system-frontend deployment. These changes deliver tangible business value: real-time user interactions, more reliable deployments, and a streamlined ops surface for frontend services.
June 2025
May 2025
8 Commits • 1 Features
May 1, 2025Monthly summary for 2025-05 focusing on beclab/Olares delivery, stability, and operational efficiency. Highlights include feature enhancements in settings and backup, infrastructure/runtime upgrades, frontend deployment simplification, and reliability fixes across websocket and asset serving. Emphasizes business value such as safer backups, improved security, and streamlined deployments.
May 2025
8 Commits • 1 Features
May 1, 2025Monthly summary for 2025-05 focusing on beclab/Olares delivery, stability, and operational efficiency. Highlights include feature enhancements in settings and backup, infrastructure/runtime upgrades, frontend deployment simplification, and reliability fixes across websocket and asset serving. Emphasizes business value such as safer backups, improved security, and streamlined deployments.
April 2025
3 Commits • 1 Features
Apr 1, 2025April 2025 — Focused on delivering a coordinated multi-service release, stabilizing infrastructure/network access, and addressing UI behavior issues. The work delivered business value through faster, more reliable releases across services, improved network reliability in the Settings stack, and corrected administrator-facing UI settings flows. This period demonstrates end-to-end delivery from code changes to deployment, with clear impact on release cadence, system stability, and user experience.
3 Commits • 1 Features
Apr 1, 2025April 2025 — Focused on delivering a coordinated multi-service release, stabilizing infrastructure/network access, and addressing UI behavior issues. The work delivered business value through faster, more reliable releases across services, improved network reliability in the Settings stack, and corrected administrator-facing UI settings flows. This period demonstrates end-to-end delivery from code changes to deployment, with clear impact on release cadence, system stability, and user experience.
April 2025
March 2025
1 Commits
Mar 1, 2025Concise monthly summary for beclab/Olares (March 2025). This month focused on stabilizing the files stack by updating Docker images across files-server, files, and settings to fix critical issues related to external folder moves, Google Drive root errors, and frontend default language settings. The changes were implemented as a single coordinated release to ensure compatibility across the backend files services and frontend.
March 2025
1 Commits
Mar 1, 2025Concise monthly summary for beclab/Olares (March 2025). This month focused on stabilizing the files stack by updating Docker images across files-server, files, and settings to fix critical issues related to external folder moves, Google Drive root errors, and frontend default language settings. The changes were implemented as a single coordinated release to ensure compatibility across the backend files services and frontend.
Activity
Loading activity data...
Quality Metrics
Correctness91.4%
Maintainability90.6%
Architecture90.2%
Performance86.6%
AI Usage23.4%
Skills & Technologies
Programming Languages
CSSDockerfileGoJavaScriptMarkdownNginxShellTypeScriptVueYAML
Technical Skills
API DevelopmentAPI IntegrationAPI developmentAPI integrationAsynchronous ProgrammingBackend DevelopmentCI/CDCLI DevelopmentCloud IntegrationConfiguration ManagementContainerizationContinuous IntegrationContinuous Integration/Continuous Deployment (CI/CD)DevOpsDocker
Repositories Contributed To
Overview of all repositories you've contributed to across your timeline