Developer Spotlight: Cody Tseng, Jumble.Social #791
Draft
Kokkomaki wants to merge 41 commits into
Draft
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
dergigi
reviewed
May 25, 2026
Reformat the article body to match the hard-wrapped line style used in other spotlight posts for easier source editing.
Continuation lines lost their `>` prefix during prose wrapping, breaking multi-line blockquotes in the rendered post.
Convert and resize dropped PNGs to featured.jpg (1200×675) and hero.jpg (1916×821) to match existing spotlight image specs.
Re-convert featured and hero JPGs at quality 95 instead of 85.
…github.com/OpenSats/website into developer-spotlight-codytseng-jumblesocial
Link Jumble, General Fund, and OpenSats spotlight in the closing paragraphs to match the Kurt Unger spotlight format.
Use the canonical /spotlight path instead of /tags/spotlight in both developer spotlight posts.
Change "about this OpenSats spotlight piece" to "about our Spotlight series".
Replace absolute opensats.org URL with /projects/damus to match other project references in the post.
Embed the UI screenshot after the paragraph that introduces what readers see when they open Jumble.
Use the existing Image component with darkSrc so the light UI shows in light mode and the dark UI in dark mode.
Use jumble-screenshot.png for light mode and jumble-screenshot-dark.png for dark mode.
* fix(blog): reposition spotlight pull quotes below sidebar nav Move quotes below tags and back link, remove sticky stacking, and spread them with larger vertical gaps. * style(blog): use opening quote mark for spotlight pull quotes Replace the primary-colored left border with a large decorative opening quote. * style(blog): spread spotlight pull quotes by percentage offset Position quotes at 10%, 30%, 50%, etc. within a flex-grow sidebar area below the nav. * style(blog): set spotlight pull quotes in Lora italic Use a serif italic face for sidebar quotes with relaxed sizing and softer contrast. * style(blog): stack opening quote mark above spotlight pull quotes Move the decorative quote mark above the text so the sidebar quotes use full width. * style(blog): increase spotlight pull quote font size * style(blog): tighten quote mark overlap on spotlight pull quotes Enlarge the opening mark and pull quote text up so they sit closer together. * content(blog): add fourth Cody Tseng pull quote with even spacing Reorder quotes to follow the article and distribute four sidebar quotes evenly from 10% to 90%. * content(blog): tighten Cody Tseng sidebar pull quote excerpts Shorten pull quotes for the sidebar and swap in the Nostr-as-option line. Add pullQuotes to the contentlayer schema. * style(blog): adjust spotlight pull quote range to 21–79% * style(blog): use text-pretty on spotlight pull quotes * refactor(blog): derive spotlight pull quote spacing from quote count Compute top positions and container min-height from the number of quotes in frontmatter. * style(blog): scale spotlight pull quotes down on narrower desktops Use smaller type and quote marks from 1000px until xl, where full size kicks in. * content(blog): add sidebar pull quotes to Kurt Unger spotlight Curate four shortened quotes in article order for the spotlight sidebar. * style(blog): add xl right padding to spotlight pull quotes * content(blog): revise Kurt Unger sidebar pull quote selections Swap in quotes on technology tradeoffs, rural electrification, ASIC milestones, and hardware in Africa. * style(blog): try justified text on spotlight pull quotes * Revert "style(blog): try justified text on spotlight pull quotes" This reverts commit c5464b1. * content(blog): add fifth pull quote to Cody Tseng spotlight Include the closing 随心而动 line with its English translation in the sidebar quotes. * style(blog): widen spotlight pull quote range to 20–90% * content(blog): punctuate Cody Tseng closing pull quote with em dash * fix(blog): resolve TypeScript error on spotlight sidebar class * style(blog): reduce spotlight pull quote font size
dergigi
reviewed
May 28, 2026
dergigi
reviewed
May 28, 2026
dergigi
reviewed
May 28, 2026
dergigi
requested changes
May 28, 2026
Member
dergigi
left a comment
There was a problem hiding this comment.
I like it! Please address my two minor comments @Kokkomaki 🙏
Kokkomaki
commented
May 29, 2026
| > things. I think many Nostr users feel similarly. They want to truly own their | ||
| > data instead of having it locked inside the databases of large companies. | ||
|
|
||
| Bitcoin has a four-word phrase for this conviction: your keys, your coins. An |
Contributor
Author
There was a problem hiding this comment.
Suggested change
| Bitcoin has a four-word phrase for this conviction: your keys, your coins. An | |
| Bitcoin has a six-word phrase for this conviction: not your keys, not your coins. An |
|
|
||
| He doesn't talk like a rebel, but his work tells a different story. After all, | ||
| Jumble follows an older cypherpunk tradition: don't ask permission, write code. | ||
| He chafed exams he found meaningless, imagined a social network nobody owned |
Contributor
Author
There was a problem hiding this comment.
Suggested change
| He chafed exams he found meaningless, imagined a social network nobody owned | |
| He chafed at exams he found meaningless, imagined a social network nobody owned |
| them. No company can silence your account because no company owns it, or Nostr | ||
| itself. | ||
|
|
||
| Other contenders include [Amethyst][amethyst], [Coracle][coracle], and |
Contributor
Author
There was a problem hiding this comment.
Suggested change
| Other contenders include [Amethyst][amethyst], [Coracle][coracle], and | |
| Other clients include [Amethyst][amethyst], [Coracle][coracle], and |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Build preview:
Image preview: