Spiders are the only web developers that enjoy finding bugs.
#2oryhgq
Spiders are the only web developers that enjoy finding bugs.
(#pnhhnxa) @eldersnake@we.loveprivacy.club Yeah, itâs really the last thing we need. Iâd love to see X11 getting more attention â but not like this âŚ
In case you were blissfully unaware: https://utcc.utoronto.ca/~cks/space/blog/unix/XLibreIsExplicitlyPolitical
(#gixfeuq) @bender@twtxt.net This should be a core feature, no configuration required. đ¤
(#rj7o6zq) @kat@yarn.girlonthemoon.xyz On the one hand, all these programs have a very long history and the technology behind manpages is actually very powerful â you can use it to write books:
https://www.troff.org/pubs.html
I have two books from that list, for example âThe UNIX programming environmentâ:
https://movq.de/v/c3dab75c97/upe.jpg
Itâs a bit older, of course, but it looks and feels like a normal book, and it uses the same tech as manpages â which I think is really cool. đ
Itâs comparable to LaTeX (just harder/different to use) but much faster than LaTeX. You can also do stuff like render manpages as a PDF (man -Tpdf cp >cp.pdf
) or as an HTML file (man -Thtml cp >cp.html
). I think I once made slides for a talk this way.
On the other hand, traditional manpages (i.e., ones that are not written in mandoc) do not use semantic markup. They literally say, âthis text is bold, that text over here is italicsâ, and so on.
So when you run man foo
, it has no other choice but to show it in black, white, bold, underline â showing it in color would be wrong, because thatâs not what the source code of that manpage says.
Colorizing them is a hack, to be honest. Youâre not meant to do this. (The devs actually broke this by accident recently. They themselves arenât really aware that people use colors.)
If mandoc and semantic markup was more commonly used, I think it would be easier to convince the devs to add proper customizable colors.
(#ggoy7ya) @kat@yarn.girlonthemoon.xyz Any time đ
(#ggoy7ya) @kat@yarn.girlonthemoon.xyz Hereâs the full config I use.
(#c3afgma) @kat@yarn.girlonthemoon.xyz Cool! đ Yeah Iâll add that soonâ˘
(#ggoy7ya) @kat@yarn.girlonthemoon.xyz Oh sweet! I was gonna say, setting up those rules is a bit âcomplicatedâ 𤣠But Iâm glad you worked it out! đ
Hello @jassim@twtxt.net đ
(#c3afgma) There is a missing feature Iâve been intending to add to though, which is that any link that looks like a URL that might be an image, for example, ends with .png
or .jpg
or whatever, we should just render that as an image and not expect users to wrap it in Markdown image links 
(#c3afgma) @kat@yarn.girlonthemoon.xyz Ahh what do you mean by images donât embed? They definitely should! By default however all domains are blocked, so you might want to either allow some domains or just put in a .*
entry to allow all/any domsins. Screenshot attached
(#yxdhota) @arne@uplegger.eu lol đ
(#gixfeuq) (Just for fun, SuSE Linux 6.4 from ~25 years ago: https://movq.de/v/dc62d0256c/s.png )
(#yxdhota) @arne@uplegger.eu LOl thatâs hilarious đ
(#rj7o6zq) @lyse@lyse.isobeef.org @kat@yarn.girlonthemoon.xyz Colorized manpages have been a thing for a very long time:
https://movq.de/v/81219d7f7a/s.png
Problem is, hardly anybody knows this, because you configure this by ⌠drumroll ⌠overwriting TERMCAP entries of less
in your ~/.bashrc
:
export LESS_TERMCAP_md=$'\e[38;5;3m' # Bold⨠export LESS_TERMCAP_me=$'\e[0m' # End Bold
export LESS_TERMCAP_us=$'\e[4;38;5;6m' # Underline⨠export LESS_TERMCAP_ue=$'\e[0m' # End Underline
export GROFF_NO_SGR=1 # Needed since groff 1.23
Vibe code is legacy code
https://blog.val.town/vibe-code
Our $100M Series B
https://oxide.computer/blog/our-100m-series-b
(#6u6yutq) @kat@yarn.girlonthemoon.xyz @movq@www.uninformativ.de Sorry, I neither finished it nor in time. :-( Thatâs as good as itâs gonna get for the moment: https://git.isobeef.org/lyse/gelbariab/-/tree/master/rss-proxys?ref_type=heads
The README should hopefully provide a crude introduction. The example configuration file is documented fairly well, I believe (but maybe not). You probably still have to consult and maybe also modify the source code to fit your needs.
Let me know if you run into issues, have questions, wishes etc.
Oscar-Winning âNo Other Landâ Awdah Hathaleen Killed by Israeli Settler
https://www.latimes.com/entertainment-arts/story/2025-07-29/awdah-hathaleen-killed-no-other-land-palestinian-activist-israeli-settler
(#25gytiq) Hahaha, I first thought of https://www.youtube.com/watch?v=zA52uNzx7Y4 when I read @kat@yarn.girlonthemoon.xyzâs âlyricsâ. ;-)
Doesnât sound bad, I like it. The synth reminded me of some song by Beast in Black.
(#rj7o6zq) @movq@www.uninformativ.de @kat@yarn.girlonthemoon.xyz I also wondered for a very long time why nobody improved the man experience in the terminal. Iâd love to see links and more colors.
Speaking of manpages:
âMan pages are great, man readers are the problemâ
https://whynothugo.nl/journal/2025/04/09/man-pages-are-great-man-readers-are-the-problem/
mandoc is nicer to read/write than the man
macro package and, most importantly, itâs semantic markup.
HTML output is a bit broken in GNU groff, though (OpenBSD on the left, GNU on the right):
https://movq.de/v/f1898e648f/s.png
đ¤
Still, Iâm inclined to convert my manpages to mandoc.
(#qbiclia) @kat@yarn.girlonthemoon.xyz I still havenât tried it. đ¤ Some day, perhaps âŚ
(#jqzgbha) @kiwu@twtxt.net Hello. đ
Why is it that I hate packing so badly? I gotta have to brace myself up to start that now.
The outlook is poor, rain all the way until maybe the last day of summer camp. Definitely bringing my gummies, they are well needed, the weather report announces several days with up to 14 liters per square meter.
(#jqzgbha) Welcome to the club, @kiwu@twtxt.net!
(#7rb6psa) @kat@yarn.girlonthemoon.xyz Ta, very catchy indeed! :-) Their polyphony is great.
(#6wo52rq) @kingdomcome@yarn.girlonthemoon.xyz Yeah, itâs all about simplicity. Thatâs what got me hooked. In its original form without the extensions, you can even read the raw feed and it doesnât feel all that bad.
M8.7 Earthquake in Western Pacific, Tsunami Warning Issued
https://earthquake.usgs.gov/earthquakes/eventpage/us6000qw60/executive
(#jqzgbha) @kiwu@twtxt.net Hi!!!!!!!!! đ Welxome! đââď¸
Study Mode
https://openai.com/index/chatgpt-study-mode/
(#xfblnda) @kat@yarn.girlonthemoon.xyz WAHHHHHHđŁ
(#3yuvn7a) @kat@yarn.girlonthemoon.xyz we love u too đ¤
(#jqzgbha) @kat@yarn.girlonthemoon.xyz hii!!!!!!!!!
(#uwjf4uq) @kat@yarn.girlonthemoon.xyz ok! its kinda buggy here cuz my replys arenât coming in!
(#xfblnda) my theme song :)
first post đ¤
In 1996, they came up with the X11 âSECURITYâ extension:
https://www.reddit.com/r/linux/comments/4w548u/what_is_up_with_the_x11_security_extension/
This is what could have (eventually) solved the security issues that weâre currently seeing with X11. Those issues are cited as one of the reasons for switching to Wayland.
That extension never took off. The person on reddit wonders why â I think itâs simple: Containers and sandboxes werenât a thing in 1996. It hardly mattered if X11 was âinsecureâ. If you could run an X11 client, you probably already had access to the machine and could just do all kinds of other nasty things.
Today, sandboxing is a thing. Today, this matters.
Iâve heard so many times that âX11 is beyond fixable, itâs hopeless.â I donât believe that. I believe that these problems are solveable with X11 and some devs have said âyeah, we could have kept working on itâ. Itâs that people donât want to do it:
Why not extend the X server?
Because for the first time we have a realistic chance of not having to do that.
https://wayland.freedesktop.org/faq.html
Iâm not in a position to judge the devs. Maybe the X.Org code really is so bad that you want to run away, screaming in horror. I donât know.
But all this was a choice. I donât buy the argument that we never would have gotten rid of things like core fonts.
All the toolkits and programs had to be ported to Wayland. A huge, still unfinished effort. If that was an acceptable thing to do, then it would have been acceptable to make an âX12â that keeps all the good things about X11, remains compatible where feasible, eliminates the problems, and requires some clients to be adjusted. (You could have still made âX11X12â like âXWaylandâ for actual legacy programs.)
Show HN: Use Their ID â Use Your Local UK MPâs ID for the Online Safety Act
https://use-their-id.com/
âI witnessed war crimesâ in Gaza â former worker at GHF aid site [video]â¨https://www.bbc.com/news/videos/cy8k8045nx9o
Copyparty, turn almost any device into a file server
https://github.com/9001/copyparty
VPN use surges in UK as new online safety rules kick in
https://www.ft.com/content/356674b0-9f1d-4f95-b1d5-f27570379a9b
(#7rb6psa) @kat@yarn.girlonthemoon.xyz Thank you! I have to check out more of their stuff.
(#bjsafpq) @movq@www.uninformativ.de Holy cow! O_o
Reducing the overall screen time is desireable, thatâs right. I should do the same.
(#u53cqtq) I wasnât really aware until recently that programs canât choose their own windowâs position on Wayland. This is very weird to me, because this was not an issue on X11 to begin with: X11 programs can request a certain position and size, but the X11 WM ultimately decides if that request is being honored or not. And users can configure that.
But apparently, this whole thing is a heated debate in the Wayland world. đ¤