Posts by phnt@pl.borked.technology
(DIR) Post #B3ynhfxh8St9IZm0ie by phnt@pl.borked.technology
2026-03-06T11:48:55.499058Z
0 likes, 0 repeats
@SuperDicq @hj @sun Still ruins your life since that's barely possible to be proven otherwise. Like how will you prove that wasn't the case, film every act on camera?
(DIR) Post #B3yoWjq2Txwk5eXbKy by phnt@pl.borked.technology
2026-03-06T11:58:10.390058Z
1 likes, 0 repeats
@SuperDicq @hj @sun No idea what is "bigoted" about being cautious and thinking about risks.Still no idea what that word even means after years of seeing it, and I don't want to know.
(DIR) Post #B3yod4vH0IeBDh0pYe by phnt@pl.borked.technology
2026-03-06T11:59:19.189944Z
0 likes, 0 repeats
@SuperDicq @hj @sun I've seen only people with severe labelism used it, so probably means literally nothing and everything at the same time.
(DIR) Post #B3z6UZYlWdBUo7Zv4C by phnt@pl.borked.technology
2026-03-06T15:19:28.342358Z
0 likes, 0 repeats
@yonle @cell Also when you are into optimizing media, serving upload media directly from nginx is a good optimization as well.But be warned that on Pleroma, if you enable the ?name= query parameter for uploads and in nginx construct a content-disposition header from that query parameter for preserving filenames, filenames with space will suddenly now have pluses everywhere, because that's how it is supposed to be in the query. There's no way around that besides writing your own njs filter.Akkoma does not have this specific issue (it has different ones), because Akkoma has not pulled the URI encoding fixes from Pleroma.
(DIR) Post #B3z7WQBxQSJCHqM6fA by phnt@pl.borked.technology
2026-03-06T15:31:00.059780Z
0 likes, 1 repeats
@SuperDicq @sun @mischievoustomato You're not going to fix flaws if you let the GNU maintain a package. GNU will always say that its own code is perfect or that you feature is unneeded. You have to actually maintain your own patch sets of GNU software to have an less broken experience, no way around that.
(DIR) Post #B3z7imkVNt5TioPVrM by phnt@pl.borked.technology
2026-03-06T15:33:14.644692Z
0 likes, 0 repeats
@yonle @cell >because Akkoma has not pulled the URI encoding fixes from Pleroma.As an example, the emojis on my profile will not work correctly when used in Akkoma.
(DIR) Post #B3z7tAmCuD6P8a9xvE by phnt@pl.borked.technology
2026-03-06T15:35:06.124332Z
0 likes, 0 repeats
@yonle @cell That's because they are correctly encoded from Pleroma. If you use those emojis with the same filenames on Akkoma as emoji reactions or put them in your profile, they will be broken.
(DIR) Post #B3z87dbaWAacbP5ePA by phnt@pl.borked.technology
2026-03-06T15:37:42.777408Z
0 likes, 0 repeats
@yonle @cell That is partially it, yes. But you won't fix it fully even with plain URI.encode either. I've asked silverpill to include the Pleroma module for it in the bug report to Akkoma, but for reasons Oneric completely disregarded it.
(DIR) Post #B3z8geoQ1Rp6Tsn3JY by phnt@pl.borked.technology
2026-03-06T15:44:02.495593Z
0 likes, 0 repeats
@yonle @cell Here's one of the fixes for the emojis specifically. https://git.pleroma.social/pleroma/pleroma/pulls/7794And this for the resthttps://git.pleroma.social/pleroma/pleroma/pulls/7741 (this won't apply cleanly as it is built on an MR that was lost in a data loss, you'll have to dig through the commit history of lib/pleroma/http.ex)
(DIR) Post #B3zAxHSEJrkerwSwjI by phnt@pl.borked.technology
2026-03-06T16:09:28.970365Z
0 likes, 0 repeats
Firefox will be enshittified even more: https://www.omgubuntu.co.uk/2026/03/firefox-nova-redesign
(DIR) Post #B3zAzewnwYYMJKtwIK by phnt@pl.borked.technology
2026-03-06T16:09:54.774916Z
0 likes, 0 repeats
Unironically looks like an LLM chat app.
(DIR) Post #B3zD3wnxgxbilFwBns by phnt@pl.borked.technology
2026-03-06T16:33:05.596265Z
1 likes, 0 repeats
@graf @i When I still used Firefox (~6 months ago), I used the Photon UI userChrome.css with a couple addition, because I cannot stand Proton, but this is somehow much much worse.
(DIR) Post #B3zE67LrYANo0MOQvg by phnt@pl.borked.technology
2026-03-06T16:44:38.423439Z
0 likes, 0 repeats
@yonle @cell Here are the corrected links (forgot that commits and files changed are broken after migration to forgejo):https://old.git.pleroma.social/pleroma/pleroma/-/merge_requests/4364 (uri encoding part 2)https://old.git.pleroma.social/pleroma/pleroma/-/merge_requests/4417 (emoji reacts/invalid emoji encoding)Here's the Akkoma emoji encoding issue: https://akkoma.dev/AkkomaGang/akkoma/issues/1042It got merged before a fix landed in Pleroma and I then forgot about it. I might chime in later that it is incorrect.
(DIR) Post #B3zMKoWcczadanwc7s by phnt@pl.borked.technology
2026-03-06T18:16:58.694229Z
0 likes, 0 repeats
@lizzy I'm sorry to tell you, it has already happened. At least since June of last year. That author is a stable release maintainer and already committed patches written by claude months ago.One such example: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=78d979db6cef557c171d6059cbce06c3db89c7ee
(DIR) Post #B3zNikiYXGwMgiVNRI by phnt@pl.borked.technology
2026-03-06T18:32:31.425895Z
1 likes, 0 repeats
@mirq @lizzy Only if certain browsers had a very nice feature that bypassed Anubis in most config...#ANUBISfuck_this_shit = [ '*://kernel.org/*', '*://*.kernel.org/*', '*://codeberg.org/*', '*://archlinux.org/*', '*://*.archlinux.org/*', '*://*.gnome.org/*', '*://openwrt.org/*', '*://*.gentoo.org/*', '*://*.freedesktop.org/*' '*://rpmfusion.org/*', '*://*.pussthecat.org/*', '*://*.debian.org/*', '*://*.ffmpeg.org/*', '*://*.fedoraproject.org/*', '*://*.luanti.org/*', ]for url in fuck_this_shit: with config.pattern(url) as p: p.content.headers.user_agent = "<not telling because someone from gnome will block it.>"
(DIR) Post #B3zOEm5CzjVqBnMzpo by phnt@pl.borked.technology
2026-03-06T18:38:18.550265Z
1 likes, 0 repeats
@mirq @lizzy Anubis in the default config checks whether the user agent contains Mozilla/5.0 and if not lets it go through without any checks. That's literally all it takes and it is by design so it doesn't break tools like curl.I've already seen scrapers abusing this.
(DIR) Post #B3zQ9noNLB7A0iFlCK by phnt@pl.borked.technology
2026-03-06T18:59:48.759789Z
1 likes, 0 repeats
@mirq @lizzy qutebrowser
(DIR) Post #B3zRkVaU9yOu9sp5DU by phnt@pl.borked.technology
2026-03-06T19:17:39.582248Z
0 likes, 0 repeats
Vanilla pudding is turning me into a Misskey user.
(DIR) Post #B5HN8Psz8iDc1NzhKK by phnt@pl.borked.technology
2026-04-14T08:42:46.460795Z
0 likes, 0 repeats
@shia Check btrfs filesystem usage <mountpoint> says "Device unallocated" is a few gigabytes. If so after deleting snapshots, you have to probably rebalance the filesystem.Start with something like sudo btrfs balance start -dusage=50 <mountpoint>and increase the integer step by step up to something like 90. Then repeat the same with metadata (replace dusage with musage).It will rewrite allocated chunks that aren't fully utilized and that usually fixes the no free space issue.
(DIR) Post #B5HNdc3TwblQjzmOC8 by phnt@pl.borked.technology
2026-04-14T08:48:29.707495Z
0 likes, 0 repeats
@shia You need to have gigabytes of "Device unallocated" space to do this though, otherwise it will fail while rebalancing complaining about no free space and you are stuck. If that happens and lowering the integer substantially does not help, adding another storage device to the filesystem is the only way. So first start with something conservative and then go up slowly. Maximum is 100, which is almost unachievable (The integer is actually a percentage).