sheffield, england
From Oliver Leaver-Smith to ~sircmpwn/free-writers-club
I really dig your writing style! Styling point, I read mostly on mobile and there’s too much outer padding and I find the font is a touch too large
From Oliver Leaver-Smith to ~sircmpwn/sr.ht-discuss
May 3, 2023 3:18 PM, "Ivan Nikitin" <ivan@niktivan.org> wrote: > Hi, > > I published twice and everything works now. > Thank you everyone for the help! > > The HTML redirect also works, thanks for that info. > -- Ivan Nikitin > https://niktivan.org You want to remove this line from the non-www. domain as it's refreshing the page every second :)
From Oliver Leaver-Smith to ~sircmpwn/free-writers-club
I love articles of this nature, it’s great to see what people use to make their lives better. I can also recommend miniflux as an RSS reader -- Oliver Leaver-Smith +44 (0) 7450 217 558 | +44 (0) 114 360 1337 oliver@leaversmith.com TZ=Europe/London BD3C 73DF 33FF 729A B4B7 2C0B E7BF 2699 1650 3BFB
From Oliver Leaver-Smith to ~sircmpwn/sr.ht-discuss
February 6, 2023 9:28 AM, "Xnuk Shuman" <admin@xnu.kr> wrote: > Can be found in: https://meta.sr.ht/billing > > I inspected it with web developer tool but there's nothing useful: > <div class="goal" style="left: 13.37%" title="Presented without > comment">13.37%</div> The goal or target % of subscribers who have a paid subscription In terms of the relevance of 13.37%, it's more than likely a reference to leetspeak, https://en.wikipedia.org/wiki/Leet ols
From Oliver Leaver-Smith to ~sircmpwn/sr.ht-discuss
There’s already a ticket I believe. I built a noddy service that does just that with an mbox at https://sm2r.ols.wtf/ Let me know if it doesn’t work/fit your means
From Oliver Leaver-Smith to ~sircmpwn/sr.ht-discuss
October 30, 2022 12:17 PM, "Drew DeVault" <sir@cmpwn.com> wrote: > Are you sure that this goes in transport? As far as I can tell this is > not appropriate for this file. Yes, my understanding of transport is that it is for address => destination mapping. The destination in this case being discard https://www.postfix.org/transport.5.html
From Oliver Leaver-Smith to ~sircmpwn/sr.ht-discuss
Apologies, sent this off list: I believe you add a line like this per address to /etc/postfix/transport git@sr.ht discard: And reference the file as transport_maps in your main config -- Oliver Leaver-Smith +44 (0) 7450 217 558 | +44 (0) 114 360 1337 oliver@leaversmith.com TZ=Europe/London BD3C 73DF 33FF 729A B4B7 2C0B E7BF 2699 1650 3BFB
From Oliver Leaver-Smith to ~afontaine/blog-discuss
Fantastic blog post, I used it as the final push to finish my own albeit it slightly clunkier: https://ols.wtf/blog/meta-a-blog-post-about-this-blog.html You will have to let us know how you get on embedding comments, as I am still in two minds whether to do this or not! -- Oliver Leaver-Smith +44 (0) 7450 217 558 | +44 (0) 114 360 1337 oliver@leaversmith.com TZ=Europe/London BD3C 73DF 33FF 729A B4B7 2C0B E7BF 2699 1650 3BFB
From Oliver Leaver-Smith to ~sircmpwn/sr.ht-discuss
October 22, 2022 11:51 AM, "Oliver Lowe" <o@olowe.co> wrote: > On Sat, Oct 22, 2022 at 10:06:01AM +0200, Bastien wrote: > > Yes! I thought about this recently. But not just for sr.ht; any > mailing list! My idea was a utility I called mbox2atom. > I too wrote my own mbox2rss which would be ideal for this purpose _if_ there was a programmatic way to get the mbox of a mailing list. Currently I think it requires JS (could be wrong) and is handled by a POST request which you can't make with a standard Personal Access Token. I'm not clear whether the "legacy" API or GraphQL allow downloading of the mbox either
From Oliver Leaver-Smith to ~sircmpwn/sr.ht-discuss
October 21, 2022 3:00 PM, "Tanguy Fardet" <tanguyfardet@protonmail.com> wrote: >> HTML emails are now supported but it is opt in for the list admin > > There seem to have been a misundeerstanding: html email are not (and > will not be) supported. No misunderstanding, possibly just my brevity causing confusion > I merely added the possibility to "support" mixed html/plaintext emails > in the sense that the html part would be discarded to keep only the > plaintext instead of replying with an error to the sender. This was my understanding, but what it means is that your average user doesn't need to configure their client for plain text sending as it _should_ send as multipart anyway; accessibility for non-technical appearing to be one of OP's primary concerns