California, US
My handle is “Seirdy” on most of the platforms I use.
Website, contact: https://seirdy.one
Gemini: gemini://seirdy.one
My preferred forge for personal projects is Sourcehut, but my repositories have remotes for GitHub and GitLab too.
From Rohan Kumar to ~sircmpwn/sr.ht-discuss
Yep, discovered the issue when builds wouldn't fire on push and submitting a manifest on the web interface resulted in a failed job due to the expired TLS cert: https://builds.sr.ht/~seirdy/job/996674 Appears to have expired today. Is renewal automated? -- Seirdy (https://seirdy.one)
From Rohan Kumar to ~sircmpwn/sr.ht-discuss
Seems like there's a Docker/OCI related issue with builds.sr.ht on my end, since three consecutive Alpine jobs failed to boot with OCI-related error messages: https://builds.sr.ht/~seirdy/job/842846 https://builds.sr.ht/~seirdy/job/842936 https://builds.sr.ht/~seirdy/job/842954 Curious if this is impacting anyone else too. -- Seirdy (https://seirdy.one)
From Rohan Kumar to ~sircmpwn/searchhut-discuss
On Mon, Jul 11, 2022 at 07:14:35PM +0200, Drew DeVault wrote: >On Mon Jul 11, 2022 at 6:30 PM CEST, Rohan Kumar wrote: >> Semi-agreed; I do think that providing multiple links rather than a >> single random one would be preferable, as it's a more established >> convention and will increase the probability of users discovering a new >> engine they like. I'll reach out to Daoud about progressive enhancement >> for mwmbl; I do think it's worth keeping an eye on. I especially like >> its distributed crawling of centrally-collected pages. > >How about: > ><div class="alert"> > Didn't find what you were looking for? Try one of these search engines: >
From Rohan Kumar to ~sircmpwn/searchhut-discuss
On Mon, Jul 11, 2022 at 11:50:52AM +0200, Drew DeVault wrote: >I'm open to this. I think we should pick one at random and stick a link >to it at the end of the search results (<div class="alert">didn't find >what you were looking for? Try this search on <whatever>). Only FOSS >providers and let's also avoid recommending mwmbl until they have a >javascript-optional frontend. Semi-agreed; I do think that providing multiple links rather than a single random one would be preferable, as it's a more established convention and will increase the probability of users discovering a new engine they like. I'll reach out to Daoud about progressive enhancement for mwmbl; I do think it's worth keeping an eye on. I especially like its distributed crawling of centrally-collected pages.
From Rohan Kumar to ~sircmpwn/searchhut-discuss
A rising tide lifts all boats; many alternative search engines have started appending links to other search engines at the bottom of their SERPs, to allow users to try their searches elsewhere if they're unhappy. This could be a good opportunity to promote other non-mainstream engines with their own indexes. Mojeek and Brave are two such examples of engines with these links. Marginalia, Teclis, Searchcode, Mwmbl, and Alexandria would be good options; all of those except Teclis are FOSS, and all except Mwmbl run without JS. -- Seirdy
From Rohan Kumar to ~sircmpwn/searchhut-devel
- Make search results an <ol> with an ARIA label. If more elements are erver present on the SERP (e.g. settings), the <ol> should be placed inside a <section> and its label should move to that section too. - Remove list-style and padding from the <ol> in the stylesheet - Add the "search" ARIA role to the search form. - Make search result titles headings. This is established convention that assistive-technology users are already familiar with from other engines. - Add an indicator for "N search results found". This is where the list label comes from. - Exclude the brand name from machine translation. --- static/main.css | 5 +++++ templates/form.html | 5 +++-- [message trimmed]
From Rohan Kumar to ~devinprater/fossability
On Mon, Jun 20, 2022 at 12:15:58PM +0500, Anna “CyberTailor” wrote: >I've read in guidelines for applications: > >> Provide an HTML version of all documentation. They are easier to >> navigate and better convertible. > >What are you thoughts on documentation converted to HTML from another >format? > >For example, there are lots of man-to-html converters. Which of them >(mandoc? man2html?) produce the most accessible HTML? Ooh, this is a good question. I'm not intimately familiar with the different man-to-html converters; I'll have to take a closer look and
From Rohan Kumar to ~seirdy/seirdy.one-comments
Sorry, this slipped my radar; sourcehut emails hadn't been delivered to me for a while. I happened to notice and fix the same problem. -- Seirdy
From Rohan Kumar to ~sircmpwn/public-inbox
I read your post "Framing accessibility in broader terms": => https://drewdevault.com/2022/02/13/Framing-accessibility-in-broader-terms.html It seems like what you're describing in the post isn't (just) accessibility, but inclusive design. Accessibility is just one part (arguably the biggest part) of inclusive design. The goal of inclusive design is to make things work for as many special needs (especially underrepresented needs) as possible throughout the design process, taking into account disability, available hardware, languages spoken, inclusive language, etc. => https://en.wikipedia.org/wiki/Inclusive_design
From Rohan Kumar to ~sircmpwn/public-inbox
Use efficient-compression-tool's Zopfli-based PNG compressor and jpegoptim to optimize PNG and JPEG inline image assets, respectively. --- static/DEC_VT100_terminal.jpg | Bin 2082914 -> 2063016 bytes static/avatar-148.png | Bin 41067 -> 40450 bytes static/avatar-512.png | Bin 363007 -> 357508 bytes static/avatar.png | Bin 21038 -> 9221 bytes 4 files changed, 0 insertions(+), 0 deletions(-) diff --git a/static/DEC_VT100_terminal.jpg b/static/DEC_VT100_terminal.jpg index 9bc744730b7a14b06db5908d8e04d461bfafde86..8a46d9d4ee60e66cc4f5345bffc5c07625da55a4 100644 GIT binary patch delta 137 zcmWN=w+Vni06<a9Ip;jlEhLDAh3$b$xPfEb4(?#@fAC(p-`^&yLy1!fjXDjQv}n_z [message trimmed]
