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, Codeberg, and GitLab too.
From Seirdy to ~hedy/inbox
--- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 60e4efa..ed4863f 100644 --- a/README.md +++ b/README.md @@ -6,7 +6,7 @@ page](https://meta-ring.hedy.dev/). ## How do I join? First read the [guidelines and requirements on the website](https://meta-ring-hedy.dev/), make sure you've added the website](https://meta-ring.hedy.dev/), make sure you've added the [message trimmed]
From Seirdy to ~hedy/inbox
--- _data/members.json | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/_data/members.json b/_data/members.json index fcdeca3..d9e4b33 100644 --- a/_data/members.json +++ b/_data/members.json @@ -8,5 +8,10 @@ "name": "eugodr", "colophon": "https://eugodr.net/meta/", "url": "https://eugodr.net/" }, { [message trimmed]
From Rohan Kumar to ~sircmpwn/sr.ht-discuss
On Fri, Apr 19, 2024 at 11:44:22PM -0400, Rohan Kumar wrote: >I set my browser's font-family to IBM Plex Sans (an excellent >proportional serif font and a terrible choice for a logo, as it's >already attached to an existing brand) Typo: s/proportional serif/proportional sans-serif/. Oops. Suggestions for fonts with good Unicode coverage and licensing, which don't look radically different from existing merchandise: - Noto Sans - Public Sans - Source Sans 3 - Nunito Sans
From Rohan Kumar to ~sircmpwn/sr.ht-discuss
Hi, I was looking at the "Logo and media resources" page on sourcehut.org today: <https://sourcehut.org/logo> I noticed that the provided logos specify a font-family of "sans-serif". This is an excellent choice for a webpage, but doesn't seem to be the right choice for a brand's official reference media. I set my browser's font-family to IBM Plex Sans (an excellent proportional serif font and a terrible choice for a logo, as it's already attached to an existing brand); however, the font face of the official merchandise looks different:
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]