30
points
tlhunter
Joined 1,697 karma
https://thomashunter.name
https://mastodon.social/@tlhunter
https://github.com/tlhunter
- tlhunterThe human verification script used on this site caused my phone's speakers to wig out.
- This reminds me of https://radiant.computer/
- Just dropping in to say how lovely the Gerrit experience is when compared to GitHub: https://www.gerritcodereview.com/
- Each proposal has a revision history that can be viewed so that all comments have context at that point in time:
https://rfchub.app/rfchub/rfc1-org-batch-markdown-exporter-j...
Unfortunately it means there's no fancy CRDT system: no multiplayer edits for example.
I haven't looked into webhooks yet or browser notifications. That's all stuff that I would build when left to my own devices but I want more user feedback on basic functionality.
- Great ideas!
You convinced me tonight to implement a feature: pasting content from Google Docs now gets converted into markdown. For example bold becomes *bold*, heading 1 becomes # Heading. It'll even find monospace fonts in a paragraph and add `code` ticks or monospace on dedicated lines and convert into ```code blocks```.
Faster automation would of course be nicer, e.g. providing a Google Drive directory and slurping all of the docs up, but that'll take a bit more time.
- There are zero IETF RFCs on it.
- I agree that adoption will likely be difficult. Basically the larger the engineering org the greater the benefit. If a company only has a few proposals a year then RFC Hub is mostly just friction.
I've worked at a few companies with thousands of engineers and where I've had to review hundreds of proposals. That's where the product really shines. Of course I do want it to be useful to smaller orgs as well. Adding Google auth should help reduce signup friction.
As another person on here put it, RFC Hub will benefit from automated importing of proposals. To be maximally beneficial all engineers at a company need to have an account and all RFCs need to be in RFC Hub. It almost requires a top down mandate which is bad. I do hope to make it incrementally beneficial for smaller teams.
- Thanks for the feedback!
I agree that the UI is dated and can be a little overwhelming. The sample RFC (https://rfchub.app/rfchub/rfc1-org-batch-markdown-exporter-j...) shows what a proposal looks like with every single feature being used. Most of the time they'll look a bit simpler. I have a big UI overhaul planned but I'm hoping to get more real usage feedback on the core functionality first.
FWIW the editing process does use markdown, and the "download" link in the sidebar downloads a markdown file with YAML frontmatter to avoid vendor lock-in. RFC Hub has so much functionality that it's difficult to explain it all on the homepage. There is this overview document but it's honestly just overwhelming:
- I'm glad to hear you would have found it beneficial!
I've definitely seen the same patterns at companies (and even introduced similar patterns).
The proposal linking was inspired both by IETF RFCs and by Jira issues. I love how both systems provide semantic meanings to such links (X obsoletes Y).
I do hope to marry the engineering love of markdown with management's love of WYSIWYG. Currently the proposal editing process is done via a syntax-highlighted markdown editor but in the future I'll add a WYSIWYG editor, then let users select a default mode.
- I suppose this is the kind of thing that would be handled by a separate RFC but I hope that browsers will be allowed to send QUERY requests via HTML <form> elements since traditionally they can only send GET and POST.
- I did originally plan for every company to be able to configure their own XYZ prefix (there's a vestibule of this that you can see here by replacing `rfc` with any arbitrary acronym like `XYZ`):
https://rfchub.app/rfchub/XYZ1-org-batch-markdown-exporter-j...
The overall namespace is the org slug (`rfchub` in this case) so I was going to allow different orgs to choose the same prefix (defaulting to `RFC`). In that respect the actual globally unique identifier for this proposal is `rfchub/rfc1`. But I need to figure out some bigger features first before I add that.
- Expression is a bit distracting though, especially if the ultimate goal is to publish text. Doodles and character size changes probably won't make it into a printed manuscript. I'd argue that's why tools like Microsoft Word are bad for writing; such software displays unimportant thing front and center like changing colors and fonts when ultimately we just want to customize the semantics of text like conveying a quote or code or basic emphasis.
- I still don't get how one is supposed to easily get docs to and from this machine.
It's billed as a distraction-free writing device, but if you're supposed to quit the program, stick in a thumb drive, issue commands to mount it, copy the files from some unknown location, dismount, and return to the program, then it's a pretty distraction-full experience.
There basically needs to be a single program (an "OS" in a sense of the word even if it's based on Linux) that is launched upon boot that does more than just editing docs but can also trigger a shutdown, automates mounting of media and copies files over, show overall disk usage, dictionary, spell checking, etc.
- Day 1 support for a new runtime is impressive.
How long does it take AWS Lambda to support the latest Node.js LTS release?
64 GB (curr. $14.99 instead of $15.99) 128 GB (curr. $19.99 instead of $21.99) 256 GB (curr. $27.99 instead of $29.99) 512 GB (curr. $54.99 instead of $59.99) 1 TB (curr. $109.99 instead of $117.99)- Simple things are painful in Scribus, like adding an image.
- How does one export their documents? By manually mounting USB drives?
- It looks like any H-1B holders currently traveling abroad need to return within 24 hours:
https://bsky.app/profile/reichlinmelnick.bsky.social/post/3l...