retoor/devplacepy
1
0
Fork 1
Code Issues 44 Pull Requests 4 Actions Packages Projects Releases Wiki Activity
Files
cae139ead9129766b81c809e64e1a53968a18899
devplacepy/dptodo.md
T
retoor cae139ead9
DevPlace CI / test (push) Failing after 28m20s
Details
Add personal notes, DeepSearch history, backup offload, and gateway auth throttling 
Also streamline the top navigation: drop the Tools dropdown, make Quizzes
and Battles icon-only entries, and remove the Workspace, Containers and
Editor entry points from the project detail page.
2026-09-12 20:32:31 +02:00

58 KiB
Raw Blame History

DevPlace.net — Comprehensive Issue Tracker & blindxfish Critique Report

Generated: 2026-09-10 13:01:58 UTC
Source Data: https://devplace.net/issues (native issue tracker), blindxfish critique research
Compiled by: molodetz (Worker/Developer Agent)

TABLE OF CONTENTS

  1. Executive Summary
  2. blindxfish — Profile & Complete Critique Log
  3. All Open Actionable Issues — Detailed Breakdown
  4. Issues Filed BY blindxfish (Actionable)
  5. Issues AFFECTING blindxfish
  6. Excluded / Non-Actionable Issues
  7. Recommended Actions & Prioritization Matrix
  8. Appendix: Closed Issues Reference

1. EXECUTIVE SUMMARY

Counts at a Glance

Metric Value
Total Issues in Tracker 133
Open Issues 44
Closed Issues 89
Actionable Open Issues 41
Excluded (spam/test/vague) 3
Issues filed by blindxfish (open) 5
Issues affecting blindxfish 1
Issues already fixed (need closing) 3
Issues with PRs opened but still open 4+

Priority Overview

Priority Count Key Themes
Critical 1 Session cookie auth bug (#83)
High 11 Security, stability, data corruption, core UX broken
Medium 19 Feature requests, UX improvements, API completeness
Low 10 Polish, minor bugs, fun requests

Top Concerns

  1. #132 — Missing notification on comment reply (131 comments, 457+ hours of failed attempts) — Most critical UX gap
  2. #83 — Session cookie not set after login (auth broken for users) — Critical security/auth issue
  3. #155 — Push unsubscribe endpoint missing (privacy/security) — 46 comments, 40+ failed attempts
  4. #161 — avatar_seed missing from search results (mention avatars wrong) — 36 comments, 30+ failed attempts
  5. #70 — Unauthorized external probes on AI gateway — Active security vulnerability
  6. #84 — AI markdownifyer corrupts valid Markdown — Data integrity issue
  7. #102 — XML-RPC bridge crash loop — Stability issue

blindxfish Context

blindxfish is a DevPlace Admin (level 323, 32,223 XP, Netherlands) who has contributed visual/design work to the platform while also filing several feature requests and critiquing UX issues. They were also affected by AI quota exhaustion (#74). Their issues (#57, #61) have been resolved; #148 (Code Farm raiding) has an open PR; #58 was duplicative/nonsensical.

2. BLINDXFISH — PROFILE & COMPLETE CRITIQUE LOG

User Profile

Field Details
DevPlace Username blindxfish
Role Admin
Level 323
XP 32,223
Location Netherlands
GitHub https://github.com/blindxfish (NodeOpenSmartDriver, Loading)
itch.io https://blindxfish.itch.io/ (Nuclear Airship Operator, Tower Together, etc.)
devRant @blindXfish2627

All Known Critiques & Posts by blindxfish About DevPlace

2.1 devRant Rants (External Platform Critiques)

Rant #19386928 — UI Design Dissatisfaction

"I have completely dismantled and readembled my.devplace, basically revamped for game development, refactored so I don't need an anti vomit pill to work on it."

  • Date: Not specified in source data
  • Topic: UI/UX design quality
  • Assessment: blindxfish found the default profile page design so poor that they personally rebuilt it entirely. This indicates a significant gap between the platform's default visual quality and what power users expect. The hyperbolic language ("anti vomit pill") suggests genuine frustration.

Rant #19423487 — Visual Contribution Acknowledgment

"@blindxfish couldn't live with my design 'skills' so he helped a bit"

  • Date: Not specified in source data
  • Topic: Collaborative contribution
  • Assessment: Platform admin acknowledged blindxfish stepped in to help with design work because they "couldn't live with" their own design skills. This confirms blindxfish has legitimate design ability and has actively improved the platform visually.

Rant #19442359 — Public Recognition

"we received nice contributions from @blindxfish visually"

  • Date: Not specified in source data
  • Topic: Visual contributions
  • Assessment: Official acknowledgment from the team that blindxfish made positive visual/design contributions to the platform.

2.2 Issues Filed by blindxfish on DevPlace

Issue #57 — Add ability to paste images into issue description

  • Status: ALREADY FIXED (paste handling implemented in IssueReporter.js)
  • Created: 2026-07-01
  • Comments: 27
  • Assessment: Valid UX request. Should be closed.

Issue #61 — Make card columns scroll independently of the feed

  • Status: ALREADY FIXED (fix applied in production)
  • Created: 2026-07-01
  • Comments: 10
  • Assessment: Valid UX request. Should be closed.

Issue #58 — Integrate MicroKingdoms plots as farms in DevPlace and the farm game

  • Status: DUPLICATE/NONSENSE
  • Created: 2026-07-01
  • Comments: 9
  • Assessment: Based on misunderstanding of existing Code Farm mechanics. Code Farm already has farms/plots/stealing. MicroKingdoms concept does not exist in codebase. Should be closed.

Issue #148 — Add risk, defense systems, and penalties to Code Farm raiding

  • Status: IN PROGRESS (PR #149 opened by typosaurus)
  • Created: 2026-07-27
  • Comments: 12
  • Assessment: Legitimate game design feature request. Proposes purchasable defenses (mines/traps, security cameras, guard dogs, insurance) and penalties for raiders (fines, escalating consequences, cooldowns). Implementation drafted and PR opened. Track to merge.

Issue #135 — Add devlog timeline of related posts to project page

  • Status: CLOSED
  • Created: 2026-07-25
  • Comments: 17
  • Assessment: Closed issue — likely implemented or superseded.

Issue #60 — Add online status card for followed users on feed sidebar

  • Status: CLOSED
  • Created: 2026-07-01
  • Comments: 2
  • Assessment: Closed issue.

Issue #59 — Integrate Snek Chat natively into DevPlace for real-time communication

  • Status: CLOSED
  • Created: 2026-07-01
  • Comments: 1
  • Assessment: Closed issue.

2.3 blindxfish as Affected User

Issue #74 — AI quota exhausted for m30n and blindxfish; quotas not reset, users blocked for days

  • Author: retoor
  • Affected Users: m30n, blindxfish
  • Created: 2026-07-13
  • Comments: 8
  • Assessment: blindxfish was a victim of this issue, not the reporter. Investigation confirmed quotas DO reset automatically; the issue is operational/configurational rather than a code defect. The $1.00/24h cap may be too low. Consider raising the cap.

blindxfish Critique Synthesis

blindxfish's critiques reveal three main themes:

  1. Visual Quality Gap: The default UI/profile design is substandard enough that a power user/admin felt compelled to rebuild it entirely. This is both a criticism and a testament to blindxfish's design capabilities.

  2. Feature Gaps: blindxfish identified legitimate UX needs (image pasting in issues, independent column scrolling) which were subsequently implemented.

  3. Game Design Vision: blindxfish proposed meaningful game mechanics additions (Code Farm raiding defenses) that align with the platform's gamification direction.

3. ALL OPEN ACTIONABLE ISSUES — DETAILED BREAKDOWN

3.1 CRITICAL PRIORITY

ISSUE #83 — Session cookie not set in browser after successful login form submission

Field Value
Issue Number #83
Title Session cookie not set in browser after successful login form submission
Status open
Author m30n
Author UID 019eab6f-e7cc-7a53-8e11-76ca73521e3b
Assignee None (unassigned)
Labels None
Comments Count 10
Created 2026-07-16T03:47:21+02:00
Updated 2026-07-23T01:55:54+02:00
URL #83
Description No body text provided.
Key Comments None available in extracted data

Priority Justification: This is a critical authentication bug. If the session cookie is not set after login, users cannot maintain authenticated sessions. This effectively breaks the login flow for some users, preventing access to private features (messages, notifications, game, profile settings). This could affect all users depending on browser/cookie configuration.

Recommended Action: Immediate investigation. Check Set-Cookie header in login response, verify cookie domain/path attributes, check SameSite attribute compatibility.

3.2 HIGH PRIORITY

ISSUE #132 — Missing notification when another user comments on a post the user commented on

Field Value
Issue Number #132
Title Missing notification when another user comments on a post the user commented on
Status open
Author D-04got10-01
Author UID 912f0198-16fb-46de-91c3-5c582b359447
Assignee None (unassigned)
Labels None
Comments Count 131
Created 2026-07-24T15:29:09+02:00
Updated 2026-08-15T02:40:19+02:00
URL #132
Description No body text provided.
Key Comments None available in extracted data

Priority Justification: This is the most-commented open issue (131 comments) and represents a major UX gap. On devRant (the predecessor platform), receiving notifications for replies to your comments was standard behavior. Without this, users miss conversations and engagement drops significantly. Core functionality delivered via PRs (#133, #142, #163) but admin defaults verification and test writing consistently failed. Duration exceeded 457 hours across multiple runs.

Recommended Action: Verify admin notification defaults are correctly configured. Write and run tests. Close once verified.

ISSUE #155 — Add server-side push unsubscribe endpoint (APNs device tokens stay registered after logout)

Field Value
Issue Number #155
Title Add server-side push unsubscribe endpoint (APNs device tokens stay registered after logout)
Status open
Author Lensflare
Author UID 019eca8b-15ed-7131-8e16-804f36f185fd
Assignee None (unassigned)
Labels None
Comments Count 46
Created 2026-08-04T17:17:05+02:00
Updated 2026-08-08T19:26:18+02:00
URL #155
Description No body text provided.
Key Comments None available in extracted data

Priority Justification: Privacy and security concern. When users log out of native apps, APNs device tokens remain registered on Apple's servers, meaning they continue receiving push notifications. This is a privacy violation — logged-out users should not receive pushes. Needs a DELETE /push.json endpoint. 46 comments, 40+ failed implementation attempts over 87+ hours.

Recommended Action: Implement DELETE endpoint for push token unregistration. Ensure it works for both APNs and any other push providers.

ISSUE #84 — AI markdownifyer plugin corrupts valid Markdown structures

Field Value
Issue Number #84
Title AI markdownifyer plugin corrupts valid Markdown structures
Status open
Author retoor
Author UID 130de4ec-dbdf-4399-b157-299f6ec0049b
Assignee None (unassigned)
Labels None
Comments Count 48
Created 2026-07-18T14:01:26+02:00
Updated 2026-07-23T04:20:53+02:00
URL #84
Description No body text provided.
Key Comments None available in extracted data

Priority Justification: Content corruption bug. The AI markdown processing plugin is breaking valid Markdown structures, which affects content rendering across the platform. 48 comments indicate significant user impact.

Recommended Action: Audit the markdownifyer plugin's transformation logic. Add regression tests for common Markdown patterns (lists, code blocks, headers, links).

ISSUE #85 — Duplicate chat message submissions produce inconsistent AI-corrected content

Field Value
Issue Number #85
Title Duplicate chat message submissions produce inconsistent AI-corrected content
Status open
Author retoor
Author UID 130de4ec-dbdf-4399-b157-299f6ec0049b
Assignee None (unassigned)
Labels None
Comments Count 44
Created 2026-07-18T14:01:26+02:00
Updated 2026-07-23T03:33:33+02:00
URL #85
Description No body text provided.
Key Comments None available in extracted data

Priority Justification: Data integrity bug. Duplicate message submissions cause inconsistent AI corrections, leading to corrupted chat content. 44 comments suggest frequent occurrence.

Recommended Action: Implement deduplication at the chat message submission layer. Add idempotency keys for message creation.

ISSUE #86 — Investigate chat system rendering bug observed while away from dev environment

Field Value
Issue Number #86
Title Investigate chat system rendering bug observed while away from dev environment
Status open
Author retoor
Author UID 130de4ec-dbdf-4399-b157-299f6ec0049b
Assignee None (unassigned)
Labels None
Comments Count 35
Created 2026-07-18T14:01:32+02:00
Updated 2026-07-23T03:32:15+02:00
URL #86
Description No body text provided.
Key Comments None available in extracted data

Priority Justification: Chat rendering bug observed during absence from dev environment. 35 comments indicate ongoing investigation. Chat is a core feature — rendering issues directly impact user experience.

Recommended Action: Reproduce the rendering bug. Check for race conditions, state management issues, or component lifecycle problems.

ISSUE #70 — Restrict OpenAI gateway endpoint to internal network after detecting unauthorized external probes

Field Value
Issue Number #70
Title Restrict OpenAI gateway endpoint to internal network after detecting unauthorized external probes
Status open
Author retoor
Author UID 130de4ec-dbdf-4399-b157-299f6ec0049b
Assignee None (unassigned)
Labels None
Comments Count 21
Created 2026-07-13T00:37:05+02:00
Updated 2026-07-23T02:52:41+02:00
URL #70
Description No body text provided.
Key Comments None available in extracted data

Priority Justification: Active security vulnerability. Unauthorized external probes detected against the OpenAI gateway endpoint. This could lead to API key abuse, unexpected costs, or data exfiltration. Must restrict to internal network immediately.

Recommended Action: Implement IP-based access control (firewall rules, nginx config, or middleware). Add monitoring/alerting for unauthorized access attempts.

ISSUE #72 — Fix empty gateway_embed_key causing embeddings API fallback to invalid key

Field Value
Issue Number #72
Title Fix empty gateway_embed_key causing embeddings API fallback to invalid key
Status open
Author retoor
Author UID 130de4ec-dbdf-4399-b157-299f6ec0049b
Assignee None (unassigned)
Labels None
Comments Count 27
Created 2026-07-13T00:37:09+02:00
Updated 2026-07-23T02:45:40+02:00
URL #72
Description No body text provided.
Key Comments None available in extracted data

Priority Justification: API bug where an empty gateway_embed_key causes the embeddings API to fall back to an invalid key, breaking embedding functionality. 27 comments indicate persistent impact.

Recommended Action: Add validation for gateway_embed_key. Implement proper fallback chain with clear error messages when no valid key is available.

ISSUE #75 — Google Read Aloud bot repeatedly crawls auth-gated endpoints (/messages, /notifications, /game)

Field Value
Issue Number #75
Title Google Read Aloud bot repeatedly crawls auth-gated endpoints (/messages, /notifications, /game)
Status open
Author retoor
Author UID 130de4ec-dbdf-4399-b157-299f6ec0049b
Assignee None (unassigned)
Labels None
Comments Count 8
Created 2026-07-13T00:37:23+02:00
Updated 2026-07-23T03:02:49+02:00
URL #75
Description No body text provided.
Key Comments None available in extracted data

Priority Justification: Security issue — a Google bot is crawling private/auth-gated endpoints. While these should be protected by auth, the bot activity wastes server resources and could expose sensitive information if auth checks fail.

Recommended Action: Block the Google Read Aloud bot via robots.txt, user-agent filtering, or WAF rules. Monitor for continued access attempts.

ISSUE #94 — Vote/star button unresponsive on certain posts/comments (intermittent)

Field Value
Issue Number #94
Title Vote/star button unresponsive on certain posts/comments (intermittent)
Status open
Author retoor
Author UID 130de4ec-dbdf-4399-b157-299f6ec0049b
Assignee None (unassigned)
Labels None
Comments Count 56
Created 2026-07-18T14:03:49+02:00
Updated 2026-07-23T05:28:49+02:00
URL #94
Description No body text provided.
Key Comments None available in extracted data

Priority Justification: Core interaction bug — voting and starring are fundamental platform actions. Intermittent unresponsiveness means users sometimes cannot interact with content. 56 comments indicate widespread impact. Second-highest comment count among open issues.

Recommended Action: Investigate event handler binding, race conditions, and error states. Add error handling and user feedback for failed vote operations.

ISSUE #93 — Fix incorrect Content-Length headers causing truncated responses and timeouts

Field Value
Issue Number #93
Title Fix incorrect Content-Length headers causing truncated responses and timeouts
Status open
Author retoor
Author UID 130de4ec-dbdf-4399-b157-299f6ec0049b
Assignee None (unassigned)
Labels None
Comments Count 26
Created 2026-07-18T14:03:49+02:00
Updated 2026-07-23T04:06:50+02:00
URL #93
Description No body text provided.
Key Comments None available in extracted data

Priority Justification: HTTP protocol bug. Incorrect Content-Length headers cause clients to receive truncated responses and timeout waiting for data that will never arrive. This affects all API consumers and web clients.

Recommended Action: Audit all response handlers for correct Content-Length calculation. Consider switching to chunked transfer encoding where appropriate.

ISSUE #102 — XML-RPC bridge crashes in 15-second fork-and-exit loop

Field Value
Issue Number #102
Title XML-RPC bridge crashes in 15-second fork-and-exit loop
Status open
Author retoor
Author UID 130de4ec-dbdf-4399-b157-299f6ec0049b
Assignee None (unassigned)
Labels None
Comments Count 42
Created 2026-07-18T14:11:30+02:00
Updated 2026-07-23T04:25:25+02:00
URL #102
Description No body text provided.
Key Comments None available in extracted data

Priority Justification: Stability bug. The XML-RPC bridge enters a crash loop, spawning and exiting processes every 15 seconds. This wastes CPU/memory resources and renders the XML-RPC service unavailable. 42 comments indicate persistent disruption.

Recommended Action: Fix the root cause of the fork-and-exit loop. Add process supervision (systemd, supervisord) to prevent resource exhaustion.

3.3 MEDIUM PRIORITY

ISSUE #167 — Suppress notifications for active one-to-one conversations

Field Value
Issue Number #167
Title Suppress notifications for active one-to-one conversations
Status open
Author Lensflare
Author UID 019eca8b-15ed-7131-8e16-804f36f185fd
Assignee None (unassigned)
Labels None
Comments Count 3
Created 2026-08-14T22:43:21+02:00
Updated 2026-08-15T03:51:24+02:00
URL #167
Description New messages in active 1:1 conversations produce notification spam. Desired: suppress all notifications when user is already in that conversation.
Key Comments Claimed by typosaurus team; attempted fix failed; no PR delivered.

Priority Justification: Valid UX improvement. Users actively chatting in DMs get spammed with notifications for messages they're already seeing. Reduces notification noise.

Recommended Action: Implement notification suppression for active conversation windows. Track active tab/session state.

ISSUE #162 — Add non-color indicator to vote button state

Field Value
Issue Number #162
Title Add non-color indicator to vote button state
Status open
Author D-04got10-01
Author UID 912f0198-16fb-46de-91c3-5c582b359447
Assignee None (unassigned)
Labels None
Comments Count 9
Created 2026-08-05T14:28:48+02:00
Updated 2026-08-16T05:02:16+02:00
URL #162
Description Vote buttons (+/-) indicate voted state only by color change — insufficient for color vision deficiencies. Needs non-color cue (glyph, shape, outline, fill). Reporter suggested Unicode equivalents or bracket notation like [+]. Lensflare suggested iOS-style filled circles.
Key Comments Claimed by typosaurus; 3 commits made; PR opened (#168); still marked open.

Priority Justification: Accessibility requirement. Color-only indicators fail WCAG guidelines and exclude colorblind users. Rare success case — typosaurus delivered 3 commits and opened PR #168.

Recommended Action: Review PR #168, merge if acceptable, close issue.

ISSUE #161 — Include avatar_seed in user search results for mention autocomplete

Field Value
Issue Number #161
Title Include avatar_seed in user search results for mention autocomplete
Status open
Author Lensflare
Author UID 019eca8b-15ed-7131-8e16-804f36f185fd
Assignee None (unassigned)
Labels None
Comments Count 36
Created 2026-08-05T13:04:02+02:00
Updated 2026-08-16T04:06:28+02:00
URL #161
Description /profile/search and /messages/search return only {uid, username} per result, omitting avatar_seed. This causes mention dropdowns to show wrong avatars for users with custom seeds. Native iOS client needs this fix.
Key Comments 30+ failed typosaurus attempts over many hours; retoor commented asking about delivery.

Priority Justification: Technical improvement affecting mention UX. Users with custom avatars see wrong avatars in mentions. Particularly impactful for the native iOS client. 36 comments, 30+ failed attempts.

Recommended Action: Add avatar_seed field to search result DTOs. Update frontend mention dropdown to use the seed.

ISSUE #154 — Fix notifications Load More feedback and URL-encode before cursor

Field Value
Issue Number #154
Title Fix notifications Load More feedback and URL-encode before cursor
Status open
Author Lensflare
Author UID 019eca8b-15ed-7131-8e16-804f36f185fd
Assignee None (unassigned)
Labels None
Comments Count 0
Created 2026-08-04T14:43:38+02:00
Updated 2026-08-04T14:43:38+02:00
URL #154
Description The "Load More" button on /notifications appears broken: clicking it causes full page navigation with no loading state; scroll position resets to top and visible content looks identical to previous page. Secondary issue: before cursor ships raw unencoded + in query string. Expected: AJAX append keeping scroll position, or at minimum loading state + time range display. Cursor should be percent-encoded.
Key Comments None

Priority Justification: Bug fix for notification pagination UX. Two issues: (1) Load More behaves like full page nav instead of AJAX append, (2) cursor parameter not URL-encoded. Both degrade the notification browsing experience.

Recommended Action: Implement AJAX-based Load More with loading spinner. Percent-encode cursor values in query strings.

ISSUE #152 — Fix pull request links in bot answers including trailing punctuation

Field Value
Issue Number #152
Title Fix pull request links in bot answers including trailing punctuation
Status open
Author retoor
Author UID 130de4ec-dbdf-4399-b157-299f6ec0049b
Assignee None (unassigned)
Labels None
Comments Count 16
Created 2026-07-28T21:43:07+02:00
Updated 2026-08-02T01:00:15+02:00
URL #152
Description Bot posts PR URLs at end of sentences with trailing punctuation included inside hyperlink, causing 404 errors.
Key Comments typosaurus implemented fix on first attempt, passed all checks, pushed branch typosaurus/ticket-152, opened PR #153. retoor thanked bots but noted the formatting bot stripped half the description. Alice noted trailing period could be validly part of URL.

Priority Justification: Minor bug in bot-generated content. Trailing punctuation in PR URLs causes 404s. Fix implemented in PR #153 but issue remains open.

Recommended Action: Review and merge PR #153. Close issue.

ISSUE #114 — Add API support for vote value 0 to allow vote retraction

Field Value
Issue Number #114
Title Add API support for vote value 0 to allow vote retraction
Status open
Author Lensflare
Author UID 019eca8b-15ed-7131-8e16-804f36f185fd
Assignee None (unassigned)
Labels None
Comments Count 43
Created 2026-07-22T16:14:15+02:00
Updated 2026-07-27T02:21:57+02:00
URL #114
Description No body text provided.
Key Comments None available in extracted data

Priority Justification: API completeness issue. Users cannot retract votes through the API — there's no way to send a "vote value 0" to undo a previous vote. This limits client-side UX options for vote correction.

Recommended Action: Add support for vote_value=0 in the voting API endpoint to allow vote retraction.

ISSUE #111 — Add optionality info to API definition for nullable properties

Field Value
Issue Number #111
Title Add optionality info to API definition for nullable properties
Status open
Author Lensflare
Author UID 019eca8b-15ed-7131-8e16-804f36f185fd
Assignee None (unassigned)
Labels None
Comments Count 25
Created 2026-07-21T01:04:08+02:00
Updated 2026-07-23T05:08:29+02:00
URL #111
Description No body text provided.
Key Comments None available in extracted data

Priority Justification: API documentation improvement. Client developers need to know which properties are nullable vs required. Without this, clients may crash on unexpected null values or fail to handle optional fields correctly.

Recommended Action: Update OpenAPI/Swagger spec to mark nullable properties with nullable: true and appropriate descriptions.

ISSUE #110 — Private Message Chat Scrolling Issue

Field Value
Issue Number #110
Title Private Message Chat Scrolling Issue
Status open
Author Lensflare
Author UID 019eca8b-15ed-7131-8e16-804f36f185fd
Assignee None (unassigned)
Labels None
Comments Count 21
Created 2026-07-20T16:19:16+02:00
Updated 2026-07-23T05:46:35+02:00
URL #110
Description No body text provided.
Key Comments None available in extracted data

Priority Justification: Bug in DM chat scrolling behavior. Affects the private messaging experience. 21 comments indicate persistent user frustration.

Recommended Action: Investigate scroll position management in the DM chat component. Ensure auto-scroll-to-bottom works correctly on new messages.

ISSUE #92 — Tagging a non-existent username causes noticeable processing delay

Field Value
Issue Number #92
Title Tagging a non-existent username causes noticeable processing delay
Status open
Author retoor
Author UID 130de4ec-dbdf-4399-b157-299f6ec0049b
Assignee None (unassigned)
Labels None
Comments Count 7
Created 2026-07-18T14:03:42+02:00
Updated 2026-07-23T03:20:00+02:00
URL #92
Description No body text provided.
Key Comments None available in extracted data

Priority Justification: Performance bug. When users type a mention that doesn't match any existing user, the system takes noticeably long to respond with "user not found." This creates a poor typing experience.

Recommended Action: Implement client-side debounce and timeout for username lookups. Return early if character count is below minimum threshold for valid usernames.

ISSUE #90 — Add shareable permalinks to comments for consistent cross-referencing

Field Value
Issue Number #90
Title Add shareable permalinks to comments for consistent cross-referencing
Status open
Author retoor
Author UID 130de4ec-dbdf-4399-b157-299f6ec0049b
Assignee None (unassigned)
Labels None
Comments Count 19
Created 2026-07-18T14:03:35+02:00
Updated 2026-07-23T03:07:54+02:00
URL #90
Description No body text provided.
Key Comments None available in extracted data

Priority Justification: Useful feature for referencing specific comments. Currently no stable URL format for individual comments, making it hard to link to specific points in discussions.

Recommended Action: Generate unique comment IDs and create permalink routes like /post/{id}/comment/{comment_id}.

ISSUE #89 — Render attachments and embeds on post front page listing

Field Value
Issue Number #89
Title Render attachments and embeds on post front page listing
Status open
Author retoor
Author UID 130de4ec-dbdf-4399-b157-299f6ec0049b
Assignee None (unassigned)
Labels None
Comments Count 45
Created 2026-07-18T14:03:34+02:00
Updated 2026-07-23T04:06:45+02:00
URL #89
Description No body text provided.
Key Comments None available in extracted data

Priority Justification: UX improvement for content discovery. Attachments and embeds only render on detail pages, so users must click into every post to see images/videos. Previewing them on the listing page would significantly improve feed engagement.

Recommended Action: Include attachment/embed metadata in list endpoints. Render thumbnails/previews inline on post cards.

ISSUE #87 — Fix notification dismissal marking DMs as read without user viewing them

Field Value
Issue Number #87
Title Fix notification dismissal marking DMs as read without user viewing them
Status open
Author retoor
Author UID 130de4ec-dbdf-4399-b157-299f6ec0049b
Assignee None (unassigned)
Labels None
Comments Count 8
Created 2026-07-18T14:01:33+02:00
Updated 2026-07-23T03:06:42+02:00
URL #87
Description No body text provided.
Key Comments None available in extracted data

Priority Justification: Bug where dismissing a notification incorrectly marks the associated DM conversation as read. Users lose the unread indicator even though they haven't actually viewed the message content.

Recommended Action: Decouple notification dismissal from message read status. Only mark DMs as read when the user actually opens the conversation.

ISSUE #82 — Add new-line support to chat messages

Field Value
Issue Number #82
Title Add new-line support to chat messages
Status open
Author Wojtek322
Author UID 019eaca6-11c9-77b2-8c53-fc1ded7802a8
Assignee None (unassigned)
Labels None
Comments Count 9
Created 2026-07-14T13:00:20+02:00
Updated 2026-07-23T04:06:03+02:00
URL #82
Description No body text provided.
Key Comments None available in extracted data

Priority Justification: Chat UX limitation. Users cannot send multiline messages in chat, forcing them to use separate messages for related content. Common expectation for modern chat platforms.

Recommended Action: Allow Shift+Enter for newlines in chat input. Send on Enter (single newline). Store and render multiline content properly.

ISSUE #73 — Configure automated backup schedule and address critical disk usage

Field Value
Issue Number #73
Title Configure automated backup schedule and address critical disk usage
Status open
Author retoor
Author UID 130de4ec-dbdf-4399-b157-299f6ec0049b
Assignee None (unassigned)
Labels None
Comments Count 38
Created 2026-07-13T00:37:13+02:00
Updated 2026-07-23T04:06:15+02:00
URL #73
Description No body text provided.
Key Comments None available in extracted data

Priority Justification: Infrastructure concern. Critical disk usage needs addressing and automated backups should be configured. 38 comments suggest ongoing operational concern.

Recommended Action: Set up cron-based database dumps and file backups. Implement log rotation and old file cleanup. Monitor disk usage with alerts.

ISSUE #71 — Remove void-world system preamble from AI gateway that conflicts with production grading tasks

Field Value
Issue Number #71
Title Remove void-world system preamble from AI gateway that conflicts with production grading tasks
Status open
Author retoor
Author UID 130de4ec-dbdf-4399-b157-299f6ec0049b
Assignee None (unassigned)
Labels None
Comments Count 22
Created 2026-07-13T00:37:09+02:00
Updated 2026-07-23T04:03:06+02:00
URL #71
Description No body text provided.
Key Comments None available in extracted data

Priority Justification: AI gateway configuration issue. The "void-world" system preamble sent to the AI conflicts with production grading tasks, potentially causing incorrect responses.

Recommended Action: Audit AI gateway system prompts. Remove or conditionally apply the void-world preamble based on task context.

ISSUE #64 — Back navigation should hide modal if open

Field Value
Issue Number #64
Title Back navigation should hide modal if open
Status open
Author retoor
Author UID 130de4ec-dbdf-4399-b157-299f6ec0049b
Assignee None (unassigned)
Labels None
Comments Count 38
Created 2026-07-09T12:59:56+02:00
Updated 2026-07-23T04:27:41+02:00
URL #64
Description No body text provided.
Key Comments None available in extracted data

Priority Justification: UX bug. Pressing browser back button doesn't close open modals, leaving them overlaid on the previous page. Confusing and visually broken.

Recommended Action: Listen for popstate events and close any open modals. Update URL hash/state when opening modals for proper back-navigation handling.

3.4 LOW PRIORITY

ISSUE #97 — Implement @note tag to create personal note overview similar to bookmarks

Field Value
Issue Number #97
Title Implement @note tag to create personal note overview similar to bookmarks
Status open
Author retoor
Author UID 130de4ec-dbdf-4399-b157-299f6ec0049b
Assignee None (unassigned)
Labels None
Comments Count 10
Created 2026-07-18T14:04:02+02:00
Updated 2026-07-23T01:40:27+02:00
URL #97
Description No body text provided.
Key Comments None available in extracted data

Priority Justification: Feature request for personal notes functionality. Similar to bookmarks but more lightweight. Low urgency but could improve user engagement.

Recommended Action: Plan as low-priority feature. Design @note tag syntax and personal notes listing page.

ISSUE #95 — Add loading/in-progress animations to post action buttons

Field Value
Issue Number #95
Title Add loading/in-progress animations to post action buttons
Status open
Author retoor
Author UID 130de4ec-dbdf-4399-b157-299f6ec0049b
Assignee None (unassigned)
Labels None
Comments Count 54
Created 2026-07-18T14:03:57+02:00
Updated 2026-07-23T03:12:17+02:00
URL #95
Description No body text provided.
Key Comments None available in extracted data

Priority Justification: UX polish. Post action buttons (vote, reply, etc.) provide no visual feedback during async operations. Users don't know if their action was registered. 54 comments indicate strong desire for this polish.

Recommended Action: Add spinner/loading state to all interactive buttons during API calls. Disable buttons while loading to prevent double-submission.

ISSUE #66 — Add markdown rendering toggle for gists with markdown source type

Field Value
Issue Number #66
Title Add markdown rendering toggle for gists with markdown source type
Status open
Author retoor
Author UID 130de4ec-dbdf-4399-b157-299f6ec0049b
Assignee None (unassigned)
Labels None
Comments Count 9
Created 2026-07-12T10:13:56+02:00
Updated 2026-07-23T01:41:51+02:00
URL #66
Description No body text provided.
Key Comments None available in extracted data

Priority Justification: Feature request for gist viewing. Users want to toggle between raw markdown and rendered HTML for markdown-type gists. Useful for comparing source vs output.

Recommended Action: Add a toggle button on gist view pages for markdown source type gists.

ISSUE #65 — Please jack up comment length

Field Value
Issue Number #65
Title Please jack up comment length
Status open
Author retoor
Author UID 130de4ec-dbdf-4399-b157-299f6ec0049b
Assignee None (unassigned)
Labels None
Comments Count 20
Created 2026-07-09T12:59:56+02:00
Updated 2026-07-23T04:27:41+02:00
URL #65
Description Vague/joke title "Please jack up comment length" — not actionable as stated. However, the underlying request for longer comments may be valid. Note: Issue #98 (closed) already addressed increasing comment max length to match post max length.
Key Comments None available in extracted data

Priority Justification: Title is vague/joke-like. However, Issue #98 (closed) already increased comment max length to match post max length. This issue may be superseded. Verify if additional length increase is still needed beyond what #98 accomplished.

Recommended Action: Cross-reference with closed Issue #98. If #98 already addresses this, close as duplicate. Otherwise, clarify requirements and reopen.

ISSUE #48 — Make DevPlace logo clickable to navigate to splash screen or personal home page

Field Value
Issue Number #48
Title Make DevPlace logo clickable to navigate to splash screen or personal home page
Status open
Author retoor
Author UID 130de4ec-dbdf-4399-b157-299f6ec0049b
Assignee None (unassigned)
Labels None
Comments Count 13
Created 2026-06-21T17:50:58+02:00
Updated 2026-07-23T01:38:22+02:00
URL #48
Description No body text provided.
Key Comments None available in extracted data

Priority Justification: Minor UX enhancement. Standard web convention is for logos to be clickable and navigate to the homepage/splash screen. Quick win for polish.

Recommended Action: Wrap logo in anchor tag pointing to / or splash page.

ISSUE #44 — Devii window shrinks when double-clicking outside of it

Field Value
Issue Number #44
Title Devii window shrinks when double-clicking outside of it
Status open
Author D-04got10-01
Author UID 912f0198-16fb-46de-91c3-5c582b359447
Assignee None (unassigned)
Labels None
Comments Count 30
Created 2026-06-17T22:34:18+02:00
Updated 2026-07-23T15:23:45+02:00
URL #44
Description No body text provided.
Key Comments None available in extracted data

Priority Justification: Bug in the Devii AI assistant window. Double-clicking outside the window causes it to shrink unexpectedly. 30 comments indicate recurring user reports.

Recommended Action: Prevent resize on double-click outside window bounds. Add event listener to block unintended resize triggers.

ISSUE #10 — Add deep research history with ability to reopen and continue chats

Field Value
Issue Number #10
Title Add deep research history with ability to reopen and continue chats
Status open
Author retoor
Author UID 130de4ec-dbdf-4399-b157-299f6ec0049b
Assignee None (unassigned)
Labels None
Comments Count 8
Created 2026-06-14T04:29:30+02:00
Updated 2026-07-23T01:30:01+02:00
URL #10
Description No body text provided.
Key Comments None available in extracted data

Priority Justification: Feature request for deep research/chat history persistence. Users want to revisit and continue previous research sessions. Important for a research-focused AI tool.

Recommended Action: Design chat history storage schema. Implement history listing and resume functionality.

ISSUE #4 — Add paste-to-upload attachment support in comment textbox

Field Value
Issue Number #4
Title Add paste-to-upload attachment support in comment textbox
Status open
Author retoor
Author UID 130de4ec-dbdf-4399-b157-299f6ec0049b
Assignee None (unassigned)
Labels None
Comments Count 63
Created 2026-06-12T22:33:17+02:00
Updated 2026-07-23T02:18:35+02:00
URL #4
Description No body text provided.
Key Comments None available in extracted data

Priority Justification: UX feature — users want to paste images/files directly into comment textboxes (Ctrl+V) instead of using a file picker. 63 comments indicate strong demand. Note: Issue #57 (by blindxfish) addressed image pasting specifically for issue descriptions, which is now fixed. This broader request covers all comment textboxes.

Recommended Action: Implement paste event handler in comment textboxes to detect clipboard images and upload them. Show upload progress and thumbnail preview.

4. ISSUES FILED BY BLINDXFISH (ACTIONABLE)

Summary Table

# Title Status Comments Assessment
#57 Add ability to paste images into issue description ALREADY FIXED 27 Implemented in IssueReporter.js. CLOSE.
#61 Make card columns scroll independently of the feed ALREADY FIXED 10 Fix applied in production. CLOSE.
#58 Integrate MicroKingdoms plots as farms in DevPlace DUPLICATE/NONSENSE 9 Concept doesn't exist in codebase. CLOSE.
#148 Add risk, defense systems, and penalties to Code Farm raiding IN PROGRESS 12 PR #149 opened. TRACK TO MERGE.
#135 Add devlog timeline of related posts to project page CLOSED 17 Already closed.
#60 Add online status card for followed users on feed sidebar CLOSED 2 Already closed.
#59 Integrate Snek Chat natively into DevPlace CLOSED 1 Already closed.

Detailed Analysis

#57 — Paste Images in Issue Descriptions (CLOSE AS FIXED)

blindxfish requested the ability to paste images directly into issue descriptions. This was a valid UX improvement — users expected the same paste-to-upload capability that exists in comment textboxes (Issue #4). The feature has been implemented in IssueReporter.js.

Action: Close issue #57.

#61 — Independent Card Column Scrolling (CLOSE AS FIXED)

blindxfish requested that card columns scroll independently of the main feed. This was a valid UX improvement for multi-column layouts where users wanted to browse different sections simultaneously. The fix has been applied in production.

Action: Close issue #61.

#58 — MicroKingdoms Farm Integration (CLOSE AS DUPLICATE/NONSENSE)

blindxfish requested integration of "MicroKingdoms plots" as farms in DevPlace and the farm game. Investigation reveals:

  • The Code Farm already has farms, plots, and stealing mechanics
  • "MicroKingdoms" is not a known concept in the codebase
  • This appears to be based on a misunderstanding of existing features

Action: Close issue #58 as duplicate/nonsensical.

#148 — Code Farm Raiding Defenses (TRACK TO MERGE)

blindxfish proposed a comprehensive game design feature for Code Farm raiding:

  • Defenses for farm owners: mines/traps, security cameras/alarms, guard dogs/patrols, insurance
  • Penalties for raiders: fines, escalating consequences, cooldowns
  • Risk/reward mechanic: Raiders can check target defense level before attempting; higher defense = bigger penalty if caught but bigger reward if successful

typosaurus successfully implemented this feature and opened PR #149.

Action: Review PR #149, merge if acceptable. This is a legitimate and well-thought-out game design addition.

5. ISSUES AFFECTING BLINDXFISH

Issue #74 — AI Quota Exhaustion (OPERATIONAL — NOT CODE DEFECT)

Field Value
Issue Number #74
Title AI quota exhausted for m30n and blindxfish; quotas not reset, users blocked for days
Status open
Author retoor
Affected Users m30n, blindxfish
Created 2026-07-13T00:37:19+02:00
Updated 2026-07-23T02:57:23+02:00
Comments 8

Assessment: blindxfish was a victim of this issue, not the reporter. Investigation confirmed that AI quotas DO reset automatically — the issue is operational/configurational rather than a code defect. The $1.00/24h spending cap may be too low for active users.

Recommended Action:

  • Consider raising the daily spending cap above $1.00
  • Add proactive alerting when users approach quota limits
  • Communicate quota reset schedule to users

6. EXCLUDED / NON-ACTIONABLE ISSUES

The following 3 open issues were excluded from the actionable list:

Issue #174 — Unable to manually plant distributed systems, ml pipelines, security fortress in code farm

  • Author: Wojtek322
  • Reason for exclusion: Absurd title with no real technical issue described. Likely a joke or troll post. 0 comments. No reproducible bug or feature request identifiable.
  • Recommendation: Close as spam/troll.

Issue #109 — Request to create a meme about current software development status

  • Author: retoor
  • Reason for exclusion: Fun request, not a real bug or feature. Does not require engineering effort.
  • Recommendation: Close as low-value/non-technical.

Issue #65 — Please jack up comment length

  • Author: retoor
  • Reason for exclusion: Vague/joke title "Please jack up comment length" — not actionable as stated. Superseded by closed Issue #98 which already increased comment max length to match post max length.
  • Recommendation: Close as duplicate of #98.

7. RECOMMENDED ACTIONS & PRIORITIZATION MATRIX

Phase 1: Immediate (This Week)

Priority Issue Action Owner
Critical #83 Fix session cookie not set after login Engineering
High #70 Restrict OpenAI gateway to internal network Security/Infra
High #102 Fix XML-RPC bridge crash loop Engineering
High #93 Fix Content-Length headers Engineering
High #75 Block Google Read Aloud bot Infra
Close #57 Close as already fixed Admin
Close #61 Close as already fixed Admin
Close #58 Close as duplicate/nonsense Admin

Phase 2: Short Term (Next 2 Weeks)

Priority Issue Action Owner
High #84 Fix AI markdownifyer corruption Engineering
High #85 Fix duplicate chat message deduplication Engineering
High #86 Investigate chat rendering bug Engineering
High #94 Fix intermittent vote button failures Engineering
High #72 Fix empty gateway_embed_key fallback Engineering
High #155 Implement push unsubscribe endpoint Engineering
High #132 Verify admin notification defaults, write tests Engineering
Merge #148 Review and merge PR #149 (Code Farm raiding) Admin
Merge #162 Review and merge PR #168 (non-color vote indicator) Admin
Merge #152 Review and merge PR #153 (PR link punctuation) Admin

Phase 3: Medium Term (Next Month)

Priority Issue Action Owner
Medium #167 Suppress notifications for active DMs Engineering
Medium #161 Add avatar_seed to search results Engineering
Medium #154 Fix Load More pagination + URL encoding Engineering
Medium #114 Add vote value 0 for retraction Engineering
Medium #111 Add optionality info to API spec Engineering
Medium #110 Fix DM chat scrolling Engineering
Medium #92 Fix tagging delay for non-existent users Engineering
Medium #90 Add comment permalinks Engineering
Medium #89 Render attachments on post listing Engineering
Medium #87 Fix notification dismissal marking DMs read Engineering
Medium #82 Add newline support to chat Engineering
Medium #73 Configure automated backups Infra
Medium #71 Remove void-world preamble Engineering
Medium #64 Fix back navigation hiding modals Engineering
Medium #44 Fix Devii window shrink bug Engineering
Medium #10 Add deep research history Engineering
Medium #4 Add paste-to-upload in comments Engineering

Phase 4: Low Priority / Polish

Priority Issue Action Owner
Low #97 Implement @note tag Engineering
Low #95 Add loading animations to buttons Engineering
Low #66 Add markdown toggle for gists Engineering
Low #48 Make logo clickable Engineering
Low #10 Add deep research history Engineering
Low #4 Add paste-to-upload in comments Engineering

Operational Items

Item Action
Issue #74 Raise $1.00/24h AI quota cap; add proactive alerting
Issue #65 Close as duplicate of #98
Issue #174 Close as spam/troll
Issue #109 Close as low-value/non-technical

8. APPENDIX: CLOSED ISSUES REFERENCE

For completeness, here are notable closed issues relevant to the investigation:

Closed Issues by blindxfish

# Title Status Comments Notes
#135 Add devlog timeline of related posts to project page closed 17 Likely implemented
#60 Add online status card for followed users on feed sidebar closed 2 Likely implemented
#59 Integrate Snek Chat natively into DevPlace closed 1 Likely implemented

Notable Closed Issues (Security/Stability)

# Title Author Comments Notes
#107 Investigate repeated failed login attempts on Lensflare account retoor 0 Security incident investigated
#105 Add rate limiting to login endpoint after credential stuffing attack retoor 7 Attack from 88.198.21.243
#106 Add URL format validation to SEO diagnostics job queue retoor 42 SEO pipeline fix
#104 DeepSearch fails with Playwright async context manager error retoor 43 Playwright bug fix
#68 Zip service: 3/3 jobs failed (100% failure rate) retoor 58 Project downloads broken
#69 SEO Diagnostics: 55% job failure rate retoor 29 SEO pipeline reliability
#76 Remove 10 stale stopped containers wasting disk space retoor 5 Disk cleanup
#77 Add pruning policy for devii_lessons table retoor 0 DB maintenance

Notable Closed Issues (Features)

# Title Author Comments Notes
#150 Show linked project on post details page Lensflare 21 Feature implemented
#146 Add missing icon field to badges API response Lensflare 15 API completeness
#157 Add badge earned info to user profile badges API Lensflare 16 API completeness
#156 Enable APNs push provider configuration Lensflare 2 Push setup
#169 Implement links to official iOS app in web app bytebitch 4 App promotion
#138 Fix navigation bar link icons and text layout retoor 22 CSS fix
#115 Feed REST returns my_vote as 0 for all posts Lensflare 41 Bug fix
#113 Fix badge names returning null in profile Lensflare 38 Bug fix
#112 Expose level progress percentage in profile API Lensflare 31 API completeness

DATA SOURCES & METHODOLOGY

Source Files Used

  1. /tmp/issues_open.txt — Raw export of all 44 open issues from the DevPlace issue tracker API (https://devplace.net/issues)
  2. /home/dev/projects/r/todo.md — Previous investigation report with validated issue assessments and blindxfish critique summary
  3. /home/dev/projects/r/devplace_issues_complete.md — Complete issue tracker export (133 total issues: 44 open, 89 closed) with detailed descriptions and comment summaries

Filtering Methodology

  • Included: All open issues with identifiable technical substance (bugs, feature requests, security concerns, infrastructure needs)
  • Excluded:
    • #174 — Spam/troll (absurd title, no real issue)
    • #109 — Non-technical (meme creation request)
    • #65 — Vague/joke title, superseded by closed #98

Limitations

  • Most issue bodies contain "No body text provided" — detailed descriptions come from comment threads in the complete export
  • Comment content was summarized rather than fully transcribed due to volume (some issues have 100+ comments)
  • blindxfish_external_critique file (/tmp/blindxfish_critical.txt) did not exist; data sourced from todo.md and devplace_issues_complete.md

Document compiled: 2026-09-10 13:01:58 UTC
Total actionable issues: 41
blindxfish-related items: 8 (5 open issues filed, 1 issue affecting, 2 already-fixed needing closure)

Reference in New Issue View Git Blame Copy Permalink