tailscale / tailscale/tmemes

Tracking list of tmemes improvements

Open
#4 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Go
Stars
49
Forks
0
Avg merge
13d 23h
Merged PRs (30d)
1

Description

This issue is a copy of the original TODO list we wrote during development.

Add anything you think should be done, even if you don't want to do it yourself.

  • (mjf) See about writing some kind of blog post about this experience. We
    agreed this was like a really fun hackathon or "LAN party programming".
    Maybe something for .dev or a culture post on the main blog?
  • (maisem) show macros by user
  • (maisem) add slack integration [partly done?]
  • (mjf) add a "viewed" counter?
  • (jenny) add up/down vote
  • (mjf) clean up the macro cache periodically in the background
  • (mjf) downsize big templates when they're uploaded
  • (mjf) self-updating timeline on the macros view or maybe a new view?
  • (mjf) allow text colour and scale to be adjusted in the UI
  • (mjf) more flexible text placement in the UI (more lines, locations)
  • (mjf) support pagination for /api/templates too
  • (mjf) paint text with a contrast-colour outline
  • (jenny) support pagination in the frontend
  • (jenny) support toggling sort order in the frontend
  • (jenny) support showing memes per creator
  • (mjf) support long polling to refresh the UI, like a websocket or SSE
  • (mjf) render timestamps on the browser so they show the user's local time.
  • (mjf) support cache control headers for image data
  • (s) generate macro preview in go (wasm)
  • (s) allow arbitrary number of overlays in the UI
  • (s) handle multiple files dropped for upload
  • (s) move upload form to top of templates page?
  • (mjf) allow captions to have timed visibility (suggested by Brad)
  • (mjf) allow specifying/adding context links to macros

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

This issue is a broad TODO list rather than a scoped task, and it names no files, tests, or entry points. Choose one unchecked improvement, inspect the relevant Go or web UI entry point, and define completion criteria for that item before starting; the issue needs to be split into focused tasks.

Written by the indexing model from the issue text.

Assessment

Tech stack
go, wasm
Domain
full-stack, web-dev
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
15/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.