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

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

Conversation

Notices

  1. Embed this notice
    Fan of OpenBSD (puffy4life@snac.bsd.cafe)'s status on Wednesday, 30-Apr-2025 02:29:29 JST Fan of OpenBSD Fan of OpenBSD
    I am brand new to trying to setup a router firewall system, would people share their pf rules so I can have an idea what to put for ruleset? #openbsd
    In conversation about 2 months ago from snac.bsd.cafe permalink
    • Embed this notice
      feld (feld@friedcheese.us)'s status on Wednesday, 30-Apr-2025 02:31:04 JST feld feld
      in reply to
      • Jez Caudle :verified:
      @puffy4life @JezCaudle I agree that one of the hardest things in tech is learning the lingo, but once you get over that hurdle things become much easier (obviously). But I agree that it is a rather unnecessary barrier that could be removed with documentation that explains things more clearly to people who are less familiar with the technology.
      In conversation about 2 months ago permalink
    • Embed this notice
      Fan of OpenBSD (puffy4life@snac.bsd.cafe)'s status on Wednesday, 30-Apr-2025 02:31:06 JST Fan of OpenBSD Fan of OpenBSD
      in reply to
      • Jez Caudle :verified:
      @JezCaudle@infosec.exchange May issue is parching the linguistic formatting. That's my one long standing criticism of #openbsd FAQ and examples. There seems to be no consideration of cohesive phrasing. There are only seems to be an attitude of "It works, I explained it, if it doesn't calculate for you that's your problem".

      Maybe I'm alone in saying I would re-write a lot of OpenBSD's instructions to be articulate in a linear style so one connects to another rather so the user can zoom out and see the larger picture of how it all is intertwined and connects rather than written in a manner of isolated and separate bits of information with no sysinced perspective.
      In conversation about 2 months ago permalink
    • Embed this notice
      Jez Caudle :verified: (jezcaudle@infosec.exchange)'s status on Wednesday, 30-Apr-2025 02:31:07 JST Jez Caudle :verified: Jez Caudle :verified:
      in reply to
      • Jan

      @puffy4life @jan I understand. I’m a visual person so I draw diagrams and write out the rules in long hand and then implement what I think the rules should be in my lab - 20 year old Dell desktop and 4 Raspberry Pi’s - and then alter them until they work.

      In conversation about 2 months ago permalink
    • Embed this notice
      Fan of OpenBSD (puffy4life@snac.bsd.cafe)'s status on Wednesday, 30-Apr-2025 02:31:08 JST Fan of OpenBSD Fan of OpenBSD
      in reply to
      • Jan
      @jan@bsd.cafe Some of the phrasing or linguistic style doesn't be sense to be options in examples I have have questions of why it is written that why and why one setting or option isn't placed connected to something else given the phrasing.
      In conversation about 2 months ago permalink
    • Embed this notice
      Jan (jan@mastodon.bsd.cafe)'s status on Wednesday, 30-Apr-2025 02:31:10 JST Jan Jan
      in reply to

      @puffy4life look at the man page and the faq. These are good examples

      In conversation about 2 months ago permalink

Feeds

  • Activity Streams
  • RSS 2.0
  • 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.