GNU social JP
  • FAQ
  • Login
GNU social JPは日本のGNU socialサーバーです。
Usage/ToS/admin/test/Pleroma FE

  • Public

    • Public
    • Network
    • Groups
    • Featured
    • Popular
    • People

Notices by Phantasm (phnt@fluffytail.org), page 21

  1. Embed this notice
    Phantasm (phnt@fluffytail.org)'s status on Wednesday, 04-Dec-2024 02:44:48 JST Phantasm Phantasm
    in reply to
    • prettygood
    @prettygood It can never survive the dystopian future where every freely available search engine just gives out crap results.
    It worked good enough for me before, but the last few months were a complete train wreck of bad results, broken updates and almost daily rate limiting from search engines, because SearxNG just gave up and never showed any results even though the query was successful according to the "query report" thingy in the sidebar.
    In conversation about 2 months ago from fluffytail.org permalink
  2. Embed this notice
    Phantasm (phnt@fluffytail.org)'s status on Wednesday, 04-Dec-2024 01:57:38 JST Phantasm Phantasm
    in reply to
    • eemmaa
    @eemmaa You in fact exist on multiple hard drives right now.
    In conversation about 2 months ago from fluffytail.org permalink
  3. Embed this notice
    Phantasm (phnt@fluffytail.org)'s status on Wednesday, 04-Dec-2024 01:53:10 JST Phantasm Phantasm
    Bought the Kagi $10 Professional plan just to try it out.
    I'm done with SearxNG for the time being as I just don't have the time nor interest to deal with badly interpreted search queries resulting in complete nonsense being returned back, dealing with crappy results from it's "meta" functionality that seems to be broken for months and only one search engine seems to be represented in the results (usually bing or ddg even though I also have brave and qwant enabled) and the frequent nonsense returned by ddg.
    A year ago it worked fine, but it seems that now every search engine is so polluted with shitty results that not even a supposedly "meta" search engine can sieve through the garbage to find something actually useful.
    In conversation about 2 months ago from fluffytail.org permalink
  4. Embed this notice
    Phantasm (phnt@fluffytail.org)'s status on Tuesday, 03-Dec-2024 21:08:27 JST Phantasm Phantasm
    in reply to
    • SuperDicq
    • white_male
    • Rusty Crab
    • Insane Eagle Sun
    • Nudhul
    @sun @RustyCrab @SuperDicq @white_male @Nudhul It also had an alternate frame rendering mode that suffered from inconsistent frame delivery if each frame took different times to render. So you always traded either noticeable stripes in different positions on screen (because the frame split was dynamic) or you had inconsistent frame pacing.
    In conversation about 2 months ago from fluffytail.org permalink
  5. Embed this notice
    Phantasm (phnt@fluffytail.org)'s status on Tuesday, 03-Dec-2024 20:47:00 JST Phantasm Phantasm
    in reply to
    • SuperDicq
    • white_male
    • Rusty Crab
    • Nudhul
    @Nudhul @RustyCrab @SuperDicq @white_male GPU overclocking is basically dead anyway. nVidia sets the maximum clocks, voltage and power consumption and does not allow any change made to those maximums without resorting to external hardware modifications outside of VBIOS that the manufacturer will no be able to sell anyway due to the licensing.

    In other words the "overclocked" cards are just cards with something better cooling than the stock FE cards with the default clocks slightly adjusted by the manufacturer. The BIOS itself will not allow anyone, even the manufacturer, to go above limits, which is why GPU overclocking has turned into maxing out the sliders in MSI Afterburn and that's it.

    Even though manufacturers modify the default nVidia VBIOS and are allowed to change some parts of it, the maximum limits cannot be changed without breaking licensing.
    In conversation about 2 months ago from fluffytail.org permalink
  6. Embed this notice
    Phantasm (phnt@fluffytail.org)'s status on Tuesday, 03-Dec-2024 19:37:33 JST Phantasm Phantasm
    in reply to
    • SuperDicq
    • :VD15_0::VD15_1::VD15_2::VD15_3::VD15_4::VD15_5::VD15_6::VD15_7:
    @SuperDicq @VD15 When you market at it children that don't have thousand dollars in wallets, it suddenly starts to make sense from a predatory business perspective. As a kid you could afford a $60 monthly subscription, but not a one time $1K investment.
    In conversation about 2 months ago from fluffytail.org permalink
  7. Embed this notice
    Phantasm (phnt@fluffytail.org)'s status on Tuesday, 03-Dec-2024 19:29:55 JST Phantasm Phantasm
    Wiki jannies hard at work about NZXT.
    obrazek.png
    In conversation about 2 months ago from fluffytail.org permalink

    Attachments


    1. https://upload.fluffytail.org/media/7b7aad2722b47c9cf994f6113b22bb58141d118de3741417ead124b66460dd01.png?name=obrazek.png
  8. Embed this notice
    Phantasm (phnt@fluffytail.org)'s status on Tuesday, 03-Dec-2024 06:37:12 JST Phantasm Phantasm
    in reply to
    • Insane Eagle Sun
    @sun Yeah, that has zero chance of getting actually implemented unless Mastodon somehow forces it on everyone. The plethora of AP extensions is already a mess similar to the one of XMPP and it looks like nobody has learned from it.
    In conversation about 2 months ago from fluffytail.org permalink
  9. Embed this notice
    Phantasm (phnt@fluffytail.org)'s status on Tuesday, 03-Dec-2024 06:32:28 JST Phantasm Phantasm
    in reply to
    • Insane Eagle Sun
    @sun I guess nobody thinking this would be a great idea has read lain's article about it from years ago.

    As for the objection: The resulting design will very likely not be compatible with multiple AP implementations and dealing with keys/trusting them will be broken (like XMPP) or overlooked and broken (Matrix). Due to the nature of Fedi DMs, you are essentially dealing with groupchats. The final product will be OMEMO, but instead of XML as the base protocol, JSON will be used.
    In conversation about 2 months ago from fluffytail.org permalink
  10. Embed this notice
    Phantasm (phnt@fluffytail.org)'s status on Tuesday, 03-Dec-2024 05:16:49 JST Phantasm Phantasm
    in reply to
    • Haelwenn /элвэн/ :triskell:
    @lanodan
    >Lack of library management so you can end up with pacman libraries being missing?

    That shouldn't normally happen. The library pacman uses to do most of the work (libalpm) is owned by the pacman package. I've seen AUR helpers break when used as "system updaters", because they aren't rebuilt against the new version of the library and the linker properly throws it's hands up when the helper tries to launch itself again and can't find the proper version shared library.
    I've never seen it fail this spectacularly and the only cause I can think of is that it only partially extracted the new pacman package or one of the dependencies (lack of free space, power outage, killed by user/system).

    Btw sending ctrl-c when pacman is running any kind of package transaction (include pre/post hooks) is the fastest way to innocently kill an Arch system. The internal package database isn't updated properly, which will lead to pacman confusing package versions and your initcpio very likely missing.

    >Package manager fails to update the signing keys? Urgh, this shouldn't happen.

    I've seen this happen only when it couldn't verify the signature of the new keyring package based on the old keys it had. Which is a common problem if the system is left sitting for a month or two without updates. And probably the reason why pacman doesn't enforce signatures for local package installs.
    In conversation about 2 months ago from fluffytail.org permalink
  11. Embed this notice
    Phantasm (phnt@fluffytail.org)'s status on Tuesday, 03-Dec-2024 04:17:09 JST Phantasm Phantasm
    in reply to
    • prettygood
    • eemmaa
    @eemmaa @prettygood Much better than zoomer and gen alpha speak.
    In conversation about 2 months ago from fluffytail.org permalink
  12. Embed this notice
    Phantasm (phnt@fluffytail.org)'s status on Tuesday, 03-Dec-2024 03:51:45 JST Phantasm Phantasm
    in reply to
    • Haelwenn /элвэн/ :triskell:
    • Dan (phrawzty)
    @lanodan @phrawzty I've seen pacman break a few times when using AUR helpers, that's fair.

    With Arch there's always some manual assembly required. Which to some extent is a good thing if you want to learn about how the whole Linux ecosystem works under the hood, but I understand it can be annoying.
    In conversation about 2 months ago from fluffytail.org permalink
  13. Embed this notice
    Phantasm (phnt@fluffytail.org)'s status on Tuesday, 03-Dec-2024 03:42:59 JST Phantasm Phantasm
    in reply to
    • Haelwenn /элвэн/ :triskell:
    • Dan (phrawzty)
    @lanodan @phrawzty I've migrated my Arch install to Artix OpenRC couple months ago and honestly I can't complain at all. Everything that isn't already broken upstream of Arch works perfectly.
    In conversation about 2 months ago from fluffytail.org permalink
  14. Embed this notice
    Phantasm (phnt@fluffytail.org)'s status on Tuesday, 03-Dec-2024 03:30:38 JST Phantasm Phantasm

    ghetto-welding.jpg
    In conversation about 2 months ago from fluffytail.org permalink

    Attachments


    1. https://upload.fluffytail.org/media/6e2a5280b2ab84edddf6b82e1ba236f29034711bd5be61017c794a8cc59b9275.jpg?name=ghetto-welding.jpg
  15. Embed this notice
    Phantasm (phnt@fluffytail.org)'s status on Tuesday, 03-Dec-2024 03:22:13 JST Phantasm Phantasm

    shopping-apps.png
    In conversation about 2 months ago from fluffytail.org permalink

    Attachments


    1. https://upload.fluffytail.org/media/fd47bf2e9e2c77cc68e2fc866bae60f4da1d495b99a0d50f1ccdad304d873204.png?name=shopping-apps.png
  16. Embed this notice
    Phantasm (phnt@fluffytail.org)'s status on Tuesday, 03-Dec-2024 00:23:40 JST Phantasm Phantasm
    >check out work Teams Advent of Code room
    >might as well be renamed to Advent of AI code.
    >close Teams
    In conversation about 2 months ago from fluffytail.org permalink
  17. Embed this notice
    Phantasm (phnt@fluffytail.org)'s status on Tuesday, 03-Dec-2024 00:19:58 JST Phantasm Phantasm
    in reply to
    • poggie ?️‍⚧️
    • prettygood
    @prettygood @kim @eris @mold I'm starting to take the "don't update unless needed pill" for basically every computer I own. Too many things just break randomly these days. The only reason why I run my own branch of develop is to catch these bugs before they get released, because I care about Pleroma and it being better than it is.
    In conversation about 2 months ago from fluffytail.org permalink
  18. Embed this notice
    Phantasm (phnt@fluffytail.org)'s status on Monday, 02-Dec-2024 23:50:11 JST Phantasm Phantasm
    in reply to
    • poggie ?️‍⚧️
    • prettygood
    @prettygood @kim @eris @mold Idk, run a Palermo instance like usual? There are much more knowledgeable instance owners than me on here.
    In conversation about 2 months ago from fluffytail.org permalink
  19. Embed this notice
    Phantasm (phnt@fluffytail.org)'s status on Monday, 02-Dec-2024 23:40:08 JST Phantasm Phantasm
    in reply to
    • poggie ?️‍⚧️
    • prettygood
    @prettygood @kim @eris @mold
    MR in question: https://git.pleroma.social/pleroma/pleroma/-/merge_requests/4208

    >Milestone 2.7.1
    >Changelog message not included in the 2.7.1 release notes
    >the prepared_one function change does not seem to be in the federator.ex file
    >prepared.ex does not exist

    That's the extent I look into it and at least according to this it wasn't merged into the stable release.
    In conversation about 2 months ago from fluffytail.org permalink

    Attachments

    1. Domain not in remote thumbnail source whitelist: git.pleroma.social
      Fix follow requests which get stuck pending (!4208) · Merge requests · Pleroma / pleroma · GitLab
      Recipients of the bad activity have Oban job failures that look like this: ** (Oban.PerformError)...
  20. Embed this notice
    Phantasm (phnt@fluffytail.org)'s status on Monday, 02-Dec-2024 22:07:22 JST Phantasm Phantasm
    in reply to
    • cassidyclown
    • :blank:
    • Rusty Crab
    • FrailLeaf
    • Insane Eagle Sun
    @i @RustyCrab @cassidyclown @FrailLeaf @sun The "device-level" approach seems like an easily doable one. Generally speaking everybody has a Google account anyway and they already require an ID/passport to verify your age in EU and probably also in the US. And websites can tie that in with "Sign in with Google" functionality.

    Of course this completely disregards vendor lock-in, but I think that's not something the Australian government cares about.
    In conversation about 2 months ago from fluffytail.org permalink
  • After
  • Before

User actions

    Phantasm

    Phantasm

    Owner of fluffytail.orgHobbyist programmer and mechanical engineer

    Tags
    • (None)

    Following 0

      Followers 0

        Groups 0

          Statistics

          User ID
          158739
          Member since
          8 Aug 2023
          Notices
          1395
          Daily average
          3

          Feeds

          • Atom
          • Help
          • About
          • FAQ
          • TOS
          • Privacy
          • Source
          • Version
          • Contact

          GNU social JP is a social network, courtesy of GNU social JP管理人. It runs on GNU social, version 2.0.2-dev, available under the GNU Affero General Public License.

          Creative Commons Attribution 3.0 All GNU social JP content and data are available under the Creative Commons Attribution 3.0 license.