<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Hacker News: matrixagent</title><link>https://news.ycombinator.com/user?id=matrixagent</link><description>Hacker News RSS</description><docs>https://hnrss.org/</docs><generator>hnrss v2.1.1</generator><lastBuildDate>Mon, 25 May 2026 19:50:18 +0000</lastBuildDate><atom:link href="https://hnrss.org/user?id=matrixagent" rel="self" type="application/rss+xml"></atom:link><item><title><![CDATA[New comment by matrixagent in "Beautifying our UI: Giving Gitlab build features a fresh look"]]></title><description><![CDATA[
<p>Thanks, sorry for the late response – busy week. Good point, wasn't even aware that the inherited variable view is only shown in projects but not subgroups. On a quick glance I couldn't find an existing feature proposal to add it at the subgroup level as well… but that might be because the search terms aren't terribly unique.<p>I'll show your demo to the team handling CI secrets, thanks again for sharing! :)</p>
]]></description><pubDate>Fri, 14 Jul 2023 10:04:38 +0000</pubDate><link>https://news.ycombinator.com/item?id=36721803</link><dc:creator>matrixagent</dc:creator><comments>https://news.ycombinator.com/item?id=36721803</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=36721803</guid></item><item><title><![CDATA[New comment by matrixagent in "Beautifying our UI: Giving Gitlab build features a fresh look"]]></title><description><![CDATA[
<p>Do you have an example screenshot somewhere? I'm wondering what exactly this does that GitLab doesn't, because inherited variables are shown within GitLab UI directly – fairly barebones, though, so I'm curious to see your UI in action. (I work at GitLab, but not on this – just a big CI fan myself.)</p>
]]></description><pubDate>Thu, 06 Jul 2023 19:01:14 +0000</pubDate><link>https://news.ycombinator.com/item?id=36621081</link><dc:creator>matrixagent</dc:creator><comments>https://news.ycombinator.com/item?id=36621081</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=36621081</guid></item><item><title><![CDATA[New comment by matrixagent in "Tell HN: Gitlab Premium pricing increases incoming $19 to $29"]]></title><description><![CDATA[
<p>I'm a Support Engineer at GitLab, and based on my own experience that statement is definitely correct. There's entire classes of problems you simply don't have to deal with at all for SaaS customers.</p>
]]></description><pubDate>Thu, 02 Mar 2023 21:09:49 +0000</pubDate><link>https://news.ycombinator.com/item?id=35002116</link><dc:creator>matrixagent</dc:creator><comments>https://news.ycombinator.com/item?id=35002116</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=35002116</guid></item><item><title><![CDATA[The ever-increasing walled-gardeness of Twitter]]></title><description><![CDATA[
<p>Article URL: <a href="https://annoying.technology/posts/e6901c0ea272f57d/">https://annoying.technology/posts/e6901c0ea272f57d/</a></p>
<p>Comments URL: <a href="https://news.ycombinator.com/item?id=30949048">https://news.ycombinator.com/item?id=30949048</a></p>
<p>Points: 295</p>
<p># Comments: 206</p>
]]></description><pubDate>Thu, 07 Apr 2022 19:10:48 +0000</pubDate><link>https://annoying.technology/posts/e6901c0ea272f57d/</link><dc:creator>matrixagent</dc:creator><comments>https://news.ycombinator.com/item?id=30949048</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=30949048</guid></item><item><title><![CDATA[New comment by matrixagent in "OSHA to require employers with 100 employees vaccinate or test workforce"]]></title><description><![CDATA[
<p>> And no, you can’t read the minds of long dead people either.<p>And yet that is exactly what you are doing throughout multiple comments.</p>
]]></description><pubDate>Fri, 10 Sep 2021 14:24:30 +0000</pubDate><link>https://news.ycombinator.com/item?id=28481986</link><dc:creator>matrixagent</dc:creator><comments>https://news.ycombinator.com/item?id=28481986</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=28481986</guid></item><item><title><![CDATA[New comment by matrixagent in "PAM Duress – Alternate passwords for panic situations"]]></title><description><![CDATA[
<p>Thank you, that’s another good example, to which I wish I could relate less. ;)</p>
]]></description><pubDate>Mon, 23 Aug 2021 19:33:59 +0000</pubDate><link>https://news.ycombinator.com/item?id=28280842</link><dc:creator>matrixagent</dc:creator><comments>https://news.ycombinator.com/item?id=28280842</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=28280842</guid></item><item><title><![CDATA[New comment by matrixagent in "PAM Duress – Alternate passwords for panic situations"]]></title><description><![CDATA[
<p>Thanks, that's a great example. I've actually encountered this exact thing at my current employer as well.</p>
]]></description><pubDate>Mon, 23 Aug 2021 10:39:25 +0000</pubDate><link>https://news.ycombinator.com/item?id=28274072</link><dc:creator>matrixagent</dc:creator><comments>https://news.ycombinator.com/item?id=28274072</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=28274072</guid></item><item><title><![CDATA[New comment by matrixagent in "PAM Duress – Alternate passwords for panic situations"]]></title><description><![CDATA[
<p>> All orgs should consider locking out all employees for at least one uninterrupted week a year. Very easy way to shake out all sorts of problems.<p>Could you give some examples?</p>
]]></description><pubDate>Mon, 23 Aug 2021 10:08:55 +0000</pubDate><link>https://news.ycombinator.com/item?id=28273930</link><dc:creator>matrixagent</dc:creator><comments>https://news.ycombinator.com/item?id=28273930</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=28273930</guid></item><item><title><![CDATA[iOS update can't be installed while audio is playing]]></title><description><![CDATA[
<p>Article URL: <a href="https://annoying.technology/posts/7659e51d05d51105/">https://annoying.technology/posts/7659e51d05d51105/</a></p>
<p>Comments URL: <a href="https://news.ycombinator.com/item?id=27056226">https://news.ycombinator.com/item?id=27056226</a></p>
<p>Points: 2</p>
<p># Comments: 0</p>
]]></description><pubDate>Wed, 05 May 2021 21:46:05 +0000</pubDate><link>https://annoying.technology/posts/7659e51d05d51105/</link><dc:creator>matrixagent</dc:creator><comments>https://news.ycombinator.com/item?id=27056226</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=27056226</guid></item><item><title><![CDATA[New comment by matrixagent in "Twitter cut off the ability to read a tweet by fetching its URL with a HTTP GET"]]></title><description><![CDATA[
<p>I'm afraid that does not solve this particular problem, just happened again on the very first try. I still think this is intentional or at least happily accepted on part of Twitter, with the happy side effect to make it as shitty an experience as possible when you're not using their app.</p>
]]></description><pubDate>Sat, 19 Dec 2020 01:20:04 +0000</pubDate><link>https://news.ycombinator.com/item?id=25474087</link><dc:creator>matrixagent</dc:creator><comments>https://news.ycombinator.com/item?id=25474087</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=25474087</guid></item><item><title><![CDATA[New comment by matrixagent in "Twitter cut off the ability to read a tweet by fetching its URL with a HTTP GET"]]></title><description><![CDATA[
<p>Thanks, if that works that would be amazing. I'm most often getting it inside in-app browsers, e.g. when opening a Twitter link in Tweetbot, Apollo or similar apps. Not sure if they share the same central settings/service workers.</p>
]]></description><pubDate>Fri, 18 Dec 2020 16:50:35 +0000</pubDate><link>https://news.ycombinator.com/item?id=25468932</link><dc:creator>matrixagent</dc:creator><comments>https://news.ycombinator.com/item?id=25468932</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=25468932</guid></item><item><title><![CDATA[New comment by matrixagent in "Twitter cut off the ability to read a tweet by fetching its URL with a HTTP GET"]]></title><description><![CDATA[
<p><a href="https://www.danielhill.com.au/removing-service-workers-from-mac-safari/" rel="nofollow">https://www.danielhill.com.au/removing-service-workers-from-...</a><p>Now I'm trying to figure out how to do it on Mobile Safari, where this bug always hits me.</p>
]]></description><pubDate>Fri, 18 Dec 2020 12:21:30 +0000</pubDate><link>https://news.ycombinator.com/item?id=25466383</link><dc:creator>matrixagent</dc:creator><comments>https://news.ycombinator.com/item?id=25466383</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=25466383</guid></item><item><title><![CDATA[New comment by matrixagent in "Preview in macOS Big Sur is destroying PDFs"]]></title><description><![CDATA[
<p>That's exactly what I'm planning to explore as a workaround to remove the blank pages until ABBYY and/or Apple sort this out. :)</p>
]]></description><pubDate>Thu, 17 Dec 2020 12:02:50 +0000</pubDate><link>https://news.ycombinator.com/item?id=25454805</link><dc:creator>matrixagent</dc:creator><comments>https://news.ycombinator.com/item?id=25454805</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=25454805</guid></item><item><title><![CDATA[New comment by matrixagent in "Preview in macOS Big Sur is destroying PDFs"]]></title><description><![CDATA[
<p>I think you might interpret the word more harshly than I intend it to be. Something that worked before Big Sur is not working in Big Sur. It's broken. That's all there is to it for me as an end user. Of course there is a difference in reasons for things breaking, and I'm not denying that Apple might have "improved" Preview.app when you judge it by how well it adheres to a PDF spec. But it still "broke" a very common and normal workflow by doing so, and I would at least expect them to acknowledge that. If they decide breaking this is worth it, that's absolutely fine with me. But I don't think they are even aware of it, and <i>that</i> is not something I'm willing accept from a company with the reach and resources of Apple.</p>
]]></description><pubDate>Thu, 17 Dec 2020 12:01:07 +0000</pubDate><link>https://news.ycombinator.com/item?id=25454794</link><dc:creator>matrixagent</dc:creator><comments>https://news.ycombinator.com/item?id=25454794</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=25454794</guid></item><item><title><![CDATA[New comment by matrixagent in "Preview in macOS Big Sur is destroying PDFs"]]></title><description><![CDATA[
<p>This is at least the second time that Apple breaks Preview in this way. I outlined why this bug is something a lot of users could run into, and I even mention that I'm not necessarily holding it against them that it breaks, but specifically that they don't even care to mention it breaking. After the first time, which was a big deal at the time, they should have put safeguards in place so that they could <i>notice</i> it happening. If the fault is with ABBYY, then I'm okay with Apple breaking it for the sake of internally improving Preview, and blame for the breakage lies with ABBYY. But I expect Apple to tell me – because it happened before. That blame lies with Apple.<p>That is my reasoning, and I don't think that's too high a bar for one of the richest companies on the planet, priding themselves in the details and "it just works". You don't have to agree with that, obviously. Calling me an ass for that is extremely rude and uncalled for, though. I was under the impression that this tone was actually not acceptable here.</p>
]]></description><pubDate>Thu, 17 Dec 2020 00:30:51 +0000</pubDate><link>https://news.ycombinator.com/item?id=25450765</link><dc:creator>matrixagent</dc:creator><comments>https://news.ycombinator.com/item?id=25450765</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=25450765</guid></item><item><title><![CDATA[New comment by matrixagent in "Preview in macOS Big Sur is destroying PDFs"]]></title><description><![CDATA[
<p>Yes.</p>
]]></description><pubDate>Wed, 16 Dec 2020 22:07:48 +0000</pubDate><link>https://news.ycombinator.com/item?id=25449442</link><dc:creator>matrixagent</dc:creator><comments>https://news.ycombinator.com/item?id=25449442</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=25449442</guid></item><item><title><![CDATA[New comment by matrixagent in "Preview in macOS Big Sur is destroying PDFs"]]></title><description><![CDATA[
<p>Fair enough, though I'd still argue that a public write-up that might warn a few people and save them the trouble is well worth writing on its own. As this blog is just a hobby, my time for it is limited and it's not like a write-up like this doesn't already take up some time. I did provide plenty of resources in the links, to which I don't think sample PDFs from me would add much value. But point taken, I'll try to attach sample data where applicable in the future.</p>
]]></description><pubDate>Wed, 16 Dec 2020 22:03:28 +0000</pubDate><link>https://news.ycombinator.com/item?id=25449407</link><dc:creator>matrixagent</dc:creator><comments>https://news.ycombinator.com/item?id=25449407</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=25449407</guid></item><item><title><![CDATA[New comment by matrixagent in "Preview in macOS Big Sur is destroying PDFs"]]></title><description><![CDATA[
<p>In theory that is probably true – in my actual scenario I can't run them through ABBYY again because of the limitations of the bundled version. It only accepts PDFs coming from the scanner software, so running these through ABBYY again would give me an error message. I'd have to buy the full version to be able to try out that workaround.</p>
]]></description><pubDate>Wed, 16 Dec 2020 21:57:02 +0000</pubDate><link>https://news.ycombinator.com/item?id=25449337</link><dc:creator>matrixagent</dc:creator><comments>https://news.ycombinator.com/item?id=25449337</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=25449337</guid></item><item><title><![CDATA[New comment by matrixagent in "Preview in macOS Big Sur is destroying PDFs"]]></title><description><![CDATA[
<p>Could you explain why or how exactly I'm an ass?</p>
]]></description><pubDate>Wed, 16 Dec 2020 21:48:01 +0000</pubDate><link>https://news.ycombinator.com/item?id=25449226</link><dc:creator>matrixagent</dc:creator><comments>https://news.ycombinator.com/item?id=25449226</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=25449226</guid></item><item><title><![CDATA[New comment by matrixagent in "Preview in macOS Big Sur is destroying PDFs"]]></title><description><![CDATA[
<p>> If you're not going to do the work to figure out what the corruption is …<p>I'm sorry, but last time I checked neither Apple nor ABBYY pay my salary. I really don't understand these takes. If Apple or ABBYY want my PDFs, they should be able to find my email address rather easily. Your tl;dr version of the post is completely unfair. I publicly criticize Apple because they are breaking something that potentially affects a lot of people who are unlikely to even know about it, and they are doing it for at least the second time now. If you don't think that's worthy of criticism, I don't know what is.<p>I also love how so many people assume I didn't already talk to support and file radars. I guess you had better luck in the past than me, but I can assure you, these options aren't always as useful as you might think they are.</p>
]]></description><pubDate>Wed, 16 Dec 2020 21:40:28 +0000</pubDate><link>https://news.ycombinator.com/item?id=25449127</link><dc:creator>matrixagent</dc:creator><comments>https://news.ycombinator.com/item?id=25449127</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=25449127</guid></item></channel></rss>