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 feld (feld@bikeshed.party), page 3

  1. Embed this notice
    feld (feld@bikeshed.party)'s status on Saturday, 24-Aug-2024 03:18:44 JST feld feld
    in reply to
    • 
    @mint oh god that was not intentional haha O_O
    In conversation about 3 months ago from bikeshed.party permalink
  2. Embed this notice
    feld (feld@bikeshed.party)'s status on Saturday, 24-Aug-2024 03:18:43 JST feld feld
    in reply to
    • 
    • feld
    @mint it's still essentially the same functionality as we don't use that value but whewwww didn't notice that :doh:
    In conversation about 3 months ago from gnusocial.jp permalink
  3. Embed this notice
    feld (feld@bikeshed.party)'s status on Saturday, 24-Aug-2024 03:12:12 JST feld feld
    in reply to
    • 
    @mint this was my approach that I'm testing

    https://git.pleroma.social/pleroma/pleroma/-/merge_requests/4236
    In conversation about 3 months ago from bikeshed.party permalink

    Attachments

    1. Domain not in remote thumbnail source whitelist: git.pleroma.social
      Draft: Drop incoming Delete activities from unknown actors (!4236) · Merge requests · Pleroma / pleroma · GitLab
      #3311
  4. Embed this notice
    feld (feld@bikeshed.party)'s status on Friday, 23-Aug-2024 17:59:44 JST feld feld
    in reply to
    • 
    @mint We should be able to capture the domain in the json and ip it's being sent from and have two Hammer rate limit queues or something similar in a Plug filter on the inbox, right? We don't have to do any validation or anything at this step. If either hits a threshold we can start erroring there and come up with a way to exfiltrate useful metadata so people can automate firewalls or something too. Lots of options here
    In conversation about 3 months ago from bikeshed.party permalink
  5. Embed this notice
    feld (feld@bikeshed.party)'s status on Friday, 23-Aug-2024 09:38:51 JST feld feld
    in reply to
    • 
    @mint Ahh that sounds correct, dang. I'll keep thinking about this. There has to be a way we can stop people from being able to fill the database with entries. This is a bug and will be treated as such
    In conversation about 3 months ago from bikeshed.party permalink
  6. Embed this notice
    feld (feld@bikeshed.party)'s status on Friday, 23-Aug-2024 09:35:10 JST feld feld
    in reply to
    • 
    • feld
    @mint However, this means that if there are any side effects of the failure we need to keep in the database like tracking reachability of the instance we would need to change that side effect to a process we can message so that database work doesn't get rolled back. This is super easy to do and I'll help with it.
    In conversation about 3 months ago from gnusocial.jp permalink
  7. Embed this notice
    feld (feld@bikeshed.party)'s status on Friday, 23-Aug-2024 09:30:14 JST feld feld
    in reply to
    • 
    @mint Actually this could be easier than you think.

    https://git.pleroma.social/pleroma/pleroma/-/blob/develop/lib/pleroma/web/federator.ex?ref_type=heads#L105

    You just wrap this entire with statement in Pleroma.Repo.transaction() and if it exits with an error none of the database changes are committed.

    https://hexdocs.pm/ecto/Ecto.Repo.html#c:transaction/2
    In conversation about 3 months ago from bikeshed.party permalink

    Attachments

    1. Domain not in remote thumbnail source whitelist: git.pleroma.social
      lib/pleroma/web/federator.ex · develop · Pleroma / pleroma · GitLab
      Pleroma backend
    2. No result found on File_thumbnail lookup.
      Ecto.Repo — Ecto v3.12.1
  8. Embed this notice
    feld (feld@bikeshed.party)'s status on Friday, 23-Aug-2024 09:15:09 JST feld feld
    in reply to
    • 
    @mint I don't know how much work it would be to refactor things but you could wrap a stage in a Repo.Transaction and then you could error and rollback would happen automatically
    In conversation about 3 months ago from bikeshed.party permalink
  9. Embed this notice
    feld (feld@bikeshed.party)'s status on Friday, 23-Aug-2024 09:14:07 JST feld feld
    in reply to
    • 
    @mint Try cleaning out ~/.rebar and ~/.mix, I think that was part of the cause of that syslog error
    In conversation about 3 months ago from bikeshed.party permalink
  10. Embed this notice
    feld (feld@bikeshed.party)'s status on Friday, 23-Aug-2024 08:21:09 JST feld feld
    in reply to
    • 
    @mint oh yeah I opened an issue for it. Now that we can easily see it's happening... :sigh: like wtf man 🇸🇬
    In conversation about 3 months ago from bikeshed.party permalink
  11. Embed this notice
    feld (feld@bikeshed.party)'s status on Wednesday, 21-Aug-2024 23:54:49 JST feld feld
    in reply to
    • on-lain ✔ᵛᵉʳᶦᶠᶦᵉᵈ
    • feld
    @lain I mean okay, I get Rock The Vote and other "use pop culture to engage voters" strategies, but I don't know why we're turning the DNC into a giant entertainment event. It's just weird to me.

    Are they gonna bring Lil Jon out to the Senate Floor when they're voting for the next major funding bill?
    In conversation about 3 months ago from gnusocial.jp permalink
  12. Embed this notice
    feld (feld@bikeshed.party)'s status on Wednesday, 21-Aug-2024 23:53:38 JST feld feld
    in reply to
    • on-lain ✔ᵛᵉʳᶦᶠᶦᵉᵈ
    @lain no way what is wrong with people why is this a thing?
    In conversation about 3 months ago from bikeshed.party permalink
  13. Embed this notice
    feld (feld@bikeshed.party)'s status on Wednesday, 21-Aug-2024 11:40:00 JST feld feld
    in reply to
    • on-lain ✔ᵛᵉʳᶦᶠᶦᵉᵈ
    • :blobcatflower:
    @lain @lucy nobody's making Max Wright memes. and he also missed out on being included in amazing cultural references like this
    In conversation about 3 months ago from bikeshed.party permalink

    Attachments


    1. https://media.bikeshed.party/pleroma/0c09f574493eb7273b24f4f4344966448be5bddede99afd79e328b694408d28b.png
  14. Embed this notice
    feld (feld@bikeshed.party)'s status on Wednesday, 21-Aug-2024 03:20:00 JST feld feld
    in reply to
    • :apa: スプリットショックウイルス †
    • 
    @mint @splitshockvirus btw on any of your servers that did the Oban downgrade in feld/debugging branch will need to run the latest feld/debugging branch from when I re-upgraded it or else when you go back to stable releases it will still have the Oban v12 schema reverted. It can be fixed manually but running latest feld/debugging (a4293a8e) will fix it

    and on that note I'm going to push my telemetry/logging changes into that branch which will help people monitor the health better just by looking at the logs
    In conversation about 3 months ago from bikeshed.party permalink
  15. Embed this notice
    feld (feld@bikeshed.party)'s status on Wednesday, 21-Aug-2024 00:17:34 JST feld feld
    in reply to
    • @990000@mstdn.social
    @990000 I haven't read a JKR tweet in years. If people just stop reading her tweets it's the same result as her not tweeting at all
    In conversation about 3 months ago from bikeshed.party permalink
  16. Embed this notice
    feld (feld@bikeshed.party)'s status on Tuesday, 20-Aug-2024 12:01:02 JST feld feld
    LLM prompt:

    You do not know how baby is formed. They need to do way instain mother> who kill thier babbys, becuse these babby cant fright back? It was on the news this mroing a mother in ar who had kill her three kids, they are taking the three babby back to new york too lady to rest. my pary are with the father who lost his chrilden ; i am truley sorry for your lots
    In conversation about 3 months ago from bikeshed.party permalink
  17. Embed this notice
    feld (feld@bikeshed.party)'s status on Tuesday, 20-Aug-2024 11:55:26 JST feld feld
    Name of my new ska band is "Dog Piss In The Elevator"
    In conversation about 3 months ago from bikeshed.party permalink
  18. Embed this notice
    feld (feld@bikeshed.party)'s status on Tuesday, 20-Aug-2024 10:33:02 JST feld feld
    • Mike, First of His Name
    @mike I wrote a script using openssl at previous job that used a combination of hostname, service tag, and some salt known by the team to generate a long password for full disk encryption so it couldn't really be "lost" and anyone who needed to reboot a server could get it but it's still major yikes territory. These things are hard to do at scale without involving more technology that can't be offline at the wrong time
    In conversation about 3 months ago from bikeshed.party permalink
  19. Embed this notice
    feld (feld@bikeshed.party)'s status on Tuesday, 20-Aug-2024 05:14:32 JST feld feld
    in reply to
    • georgia
    @georgia this is nuts
    In conversation about 3 months ago from bikeshed.party permalink
  20. Embed this notice
    feld (feld@bikeshed.party)'s status on Tuesday, 20-Aug-2024 04:46:05 JST feld feld
    in reply to
    • Haelwenn /элвэн/ :triskell:
    • Phantasm
    @phnt @lanodan this is essentially what I was thinking about too. You can do it two ways:

    Logger.error("message here", reason: error)

    or simply

    # attach this error metadata to ALL logs emitted by this process
    Logger.metadata([reason: error])
    Logger.error("message here")


    the nice part about using Logger.metadata is that we could probably write a helper function that will just keep appending errors to a list so we can accumulate them
    In conversation about 3 months ago from bikeshed.party permalink
  • After
  • Before

User actions

    feld

    feld

    Live, Laugh, Like and SubscribeFastmail referral link -- get 10% off your first year https://ref.fm/u12606493

    Tags
    • (None)

    Following 0

      Followers 1

      • GNU Too

      Groups 0

        Statistics

        User ID
        4193
        Member since
        9 Aug 2022
        Notices
        10271
        Daily average
        12

        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.