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

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

Untitled attachment

Download link

Notices where this attachment appears

  1. Embed this notice
    David Chisnall (*Now with 50% more sarcasm!*) (david_chisnall@infosec.exchange)'s status on Monday, 28-Apr-2025 19:53:43 JST David Chisnall (*Now with 50% more sarcasm!*) David Chisnall (*Now with 50% more sarcasm!*)
    in reply to

    @amy I learned that accidentally. I was discussing how to adopt a security feature in NT and someone on that team casually mentioned third-party drivers (including antivirus) running things in interrupt handlers. The more I learned, the more horrified I was. On FreeBSD and XNU, interrupt handlers do one thing: wake a thread (or some work-queue equivalent). The thread is then preemptive. A small number of things run with interrupts disabled but it’s very rare in drivers or subsystems outside the very core parts of the OS. In Windows, the driver model seems to encourage people to just do the real work in interrupt handlers. So your USB camera is stalling a core (and whatever thread is currently trying to run there) for ms at a time, and so are a load of other kernel things.

    Even FreeRTOS discourages this kind of thing, and it’s designed for a use case where it isn’t a terrible idea.

    In CHERIoT RTOS we formalise it and bind interrupts to futexes, so the only thing that happens in an interrupt handler is that one or more futexes get woken and then we may make a scheduling decision if any of the woken threads are higher priority than the one that woke (on our chips, we have designed the interrupt controller so that it can avoid raising an interrupt if it wouldn’t result in a scheduling decision).

    In conversation about a month ago from infosec.exchange permalink
  2. Embed this notice
    LautreG (lautreg@pouet.chapril.org)'s status on Wednesday, 15-Jan-2025 07:34:40 JST LautreG LautreG
    in reply to

    @jimcarroll
    I don't have the answers, but you should look how it's done in Yunohost.
    May be this can give you some idea.

    In case you are in emergency, may be it's quicker to install Yunohost first.

    Take care

    In conversation about 5 months ago from pouet.chapril.org permalink
  3. Embed this notice
    Kelvin n0mql EN35ld (kelvin0mql@mastodon.hams.social)'s status on Thursday, 21-Sep-2023 17:51:33 JST Kelvin n0mql EN35ld Kelvin n0mql EN35ld

    In THEORY, the #ActivityPub #Plugin for #WordPress is a wonderful idea.

    In practice, I have not seen it actually work even once.

    I'm able to find my WP user from here in the mastodon.hams.social web UI, and can "Follow". But it doesn't show my headshot AVI - a plain WP logo instead.

    Then, after doing said follow, I switch to WP and make a post. Come back here - do I see that post? Hell no.

    So I DM from masto to WP. Does that DM show UP anywhere? Nope.

    It dances around the edge of working.

    In conversation Thursday, 21-Sep-2023 17:51:33 JST from mastodon.hams.social permalink
  • 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.