11 Open Issues Need Help Last updated: Aug 2, 2025

Open Issues Need Help

View All on GitHub

AI Summary: Implement AJAX calls using JavaScript's Fetch API or similar to handle file deletion and renaming requests to the `/delete` and `/rename` endpoints. Upon successful server responses, dynamically update the UI to reflect changes without requiring a full page reload. This involves modifying the frontend JavaScript to send asynchronous requests and update the file list accordingly.

Complexity: 3/5
enhancement help wanted good first issue ux feature

AI Summary: Modify the `check_origin` method in the `FileStreamHandler` and `FeatureFlagSocketHandler` to verify that the WebSocket connection's origin matches the application's domain, accounting for potential port variations during development. This prevents cross-site WebSocket hijacking vulnerabilities.

Complexity: 3/5
help wanted security websocket

AI Summary: Implement Cross-Site Request Forgery (CSRF) protection in the Filey web application by enabling Tornado's built-in `xsrf_cookies` setting and ensuring all forms and AJAX requests include the XSRF token. This involves modifying the application's settings and updating relevant form submissions and AJAX calls to include the token.

Complexity: 3/5
help wanted good first issue security

AI Summary: Implement file size limits for uploads and explore streaming large files for viewing to prevent Denial of Service attacks caused by excessively large files. This involves configuring maximum upload sizes, modifying file handling to process files in chunks rather than loading them entirely into memory, and implementing graceful error handling for oversized files.

Complexity: 4/5
bug help wanted performance file-operations memory

AI Summary: Implement a 'Copy to Clipboard' button on the file view page of the Filey web application. This button should copy the entire file content to the user's clipboard when clicked. The button should be added to the existing UI alongside the 'Download' and 'Stream' buttons.

Complexity: 2/5
enhancement good first issue

AI Summary: Implement a progress bar for file uploads in the Filey web application. This involves adding frontend JavaScript code to monitor the XMLHttpRequest upload progress event and update a progress bar element in real-time, handling both success and error scenarios. The backend does not require changes.

Complexity: 3/5
enhancement help wanted good first issue

AI Summary: Reintegrate the `browse.html` template as a beta UI for the Filey web-based file browser. This involves adding the template back to the project, creating a handler to render it, ensuring authentication, updating routing, and potentially adding a way to access this beta view (e.g., a button or URL).

Complexity: 3/5
enhancement help wanted good first issue

AI Summary: Enhance the Filey application to ensure consistent functionality across Ubuntu and Windows operating systems. This involves reviewing and updating all path handling to use OS-agnostic methods, ensuring file operations are robust on both platforms, avoiding non-portable shell commands, and adding documentation or tests for cross-platform compatibility.

Complexity: 4/5
enhancement help wanted

AI Summary: Implement a search bar and sortable columns (name, size, modification date) for the file listing in the Filey web application. The search should filter results in real-time, and sorting should be done client-side if possible, otherwise server-side.

Complexity: 3/5
enhancement help wanted

AI Summary: Implement in-browser previews for common file types like images (.png, .jpg) within the Filey web application. This involves adding functionality to detect the file type, render the appropriate preview (e.g., using an image tag for images), and potentially handling other file types like PDFs or Markdown in the future.

Complexity: 3/5
enhancement help wanted

AI Summary: Modify the Filey application's startup process to prevent the logging of the access token to the console. This involves removing the code responsible for printing the token during initialization, ensuring no sensitive information is exposed in server logs.

Complexity: 2/5
good first issue