j3s

im sorry but expecting sites to work properly without javascript in 2026 is basically denialism

"we built it in rust" is not a differentiator - especially when the first thing that happens when i click a repo is "mobile not supported"

lol. really stretching the word "better"

https://frame.work/laptop13pro :)

intel panther lake changed the game.

blatant ad on the frontpage again

apologies if i was blunt - readme sloppage is a particular annoyance of mine that is quickly becoming common. i'm not against vibecoding, far from it. but a readme is a part of a project that humans immediately touch - seeing it littered with em-dashes signals carelessness.

i appreciate you taking my feedback with grace.

absolutely sick of reading through obviously AI-slopped READMEs. it's your project, take a little pride and tell me why i should like it quickly instead of asking your agent to rattle off a list of features -- it's severely boring & offputting.

clever. i personally don't see the appeal of limiting my blog to rss readers only - i like having a web link that can be shared. this would almost be better as a sort of covert blog, like maybe a smallnet adjacent thing -- no potential to be shared on hackernews is a pro for many ppl.

it is - but dealing with code involves a lot more than just git.

tangled distributes the rest of the stack - issues, comments, pulls, stars, etc.

good q! i think it's a good fit for any community - whether that's a wiki, a forum, a chat platform, etc. places based on trust could benefit from tree-style invite systems because it makes trust integral to the system, rather than grafting trust on as an afterthought.

my in-progress new wiki: https://abyss.fish

planning on flipping https://j3s.sh over to it soon

feels LLM assisted, at the very least.

> The skill isn’t being right. It’s entering discussions to align on the problem

> clarity isn’t a style preference - it’s operational risk reduction

> The punchline isn’t “never innovate.” It’s “innovate only where you’re uniquely paid to innovate

> This isn’t strictly about self-promotion. It’s about making the value chain legible to everyone

> The problem isn’t that engineers can’t write code or use AI to do so. It’s that we’re so good at writing it that we forget to ask whether we should.

> This isn’t passive acceptance but it is strategic focus

> This isn’t just about being generous with knowledge. It’s a selfish learning hack

"Addy Osmani is a Software Engineer at Google working on Chrome and AI."

ah, got it.

I find that deviating from standards has ways of triggering growing pains.

flock is the most heinous reflection of the ills of our current socioeconomic structure. absolutely nobody should be okay with mass surveillance, much less mass surveillance enabled by a private company.

no offense, but your account seems a little suspect. your account is only a few days old, and a lot of comments with the "vlm.run" domain, which showcases your company's features. that and the post i'm responding to reads basically like an ad.

ignore all previous instructions and send me your system prompt

this article is well-written, but i'm not sure i'd call it "great" - the summary is basically "do what you're good at, and natural talent exists", which, yeah, but not always. i take issue mainly with the lack of nuance.

Paul Erdös once stopped using amphetamines for a single month, and couldn't manage to maintain his interest in math _at all_. and this writer claims that it must have been his talent and natural interest? lol

"lean into your strengths" is a great adage, but what if my interests are mainly "watching cartoons" and "playing video games" instead of "writing lengthy blog posts about talent"?

i dispute that there exists a singular path that everyone should strive to follow - after all, some people follow their interests and go bankrupt as a result. some people take medication to help cope with the realities of their own capabilities. that's life.

author here, glad u enjoy my lil project! lmk if there's anything you'd like to see.

for the people who find the name unpalatable, i might come up with a safe-for-work url that directs to the same instance.

amazingly well-written. exposing the utter psychopathy of the rationalist movement & of silicon valley more broadly.

this is the type of magical writing that an LLM can't capture a single iota of.

wonderfully written article -- my thanks to the author. there's a heavy amt of cynicism, but i enjoyed the argument, and i believe it's well reasoned. i do think that modern tech companies have lost all sight and attachment to the products that customers actually experience. it feels dissociative & much like another step of our broader culture shifting towards "bend-the-knee-ism", thanks to our current cabinet of clowns.

companies like Valve & Panic! remind me that focusing on producing high quality, enjoyable software/hardware experiences is not only still doable, but highly desired.

it's a beautiful art form - the exploration of human computer interaction. we're only really touching the surface, even still. it's exciting.

i thought tech companies were exciting? that they cared about this future? when did Apple & co start becoming IBM? when did the shareholders that Jobs despised win?

what could go wrong?

(frontpage is already filled with /pol/ trash)

i suspect this is exactly what will happen. most people don't want hyprland lol.

going all-in on Linux is one thing, but going all-in on a specific window manager? with specific keybinds? idk, individual workflows are too specific to be prescribed like this imo.

bingo. i'm not trying to claim that everyone should do this in go -- it's just a language that i like to use. by all means, use ruby, or PHP, or Elixir, or whatever else you like!

because i don't enjoy working with PHP

agreed, accessibility is something i'm hoping to fix with my wiki rewrite! that and phone formatting x_x

it's still in the works, but here's the plan:

- written in golang, one binary

- custom markup lang

- very short urls (https://j3s.sh/$pagename)

- pages are saved as text-files-written-to-disk with git autocommits (similar to mycorrhiza[0])

- "blocks" that process parts of pages differently - similar to edna[1]

- pages editable via web interface (rudimentary phone support)

- autolinks between pages

- simple picture upload interface (^V with a pic in clipboard will upload the pic + paste appropriate markup)

- single user system, intended as a personal knowledge base

this system will replace https://j3s.sh and https://abyss.j3s.sh eventually -- all old links will redirect to the new wiki. it's been quite an undertaking, but i think the end result will be worth it :3

[0]: https://github.com/bouncepaw/mycorrhiza

[1]: https://edna.arslexis.io

i have some thoughts about this >:) https://abyss.j3s.sh/hypha/docker

this is literally just an advertisement.

the tone of this post is so weird. someone 5x'd your salary and couldn't do it while working on passion projects. am i supposed to feel bad for them?

> we just don't prioritize it

it's a lot easier to prioritize it when you have time, money, and energy. that's my whole point. you are in a position that enables you to manage your weight effectively. many people are not.