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
    Ademan (ademan@thebag.social)'s status on Wednesday, 01-Mar-2023 16:36:04 JST Ademan Ademan
    in reply to
    • Sexy Moon
    • Sebastian Rieger
    • :pci: Benjamin Bellamy 🇺🇸

    128 bits is an awful lot, you’re not really saving any bytes vs string names at that point

    In conversation Wednesday, 01-Mar-2023 16:36:04 JST from thebag.social permalink
    • Embed this notice
      Sexy Moon (moon@shitposter.club)'s status on Wednesday, 01-Mar-2023 16:36:04 JST Sexy Moon Sexy Moon
      in reply to
      • Sebastian Rieger
      • :pci: Benjamin Bellamy 🇺🇸
      @ademan @rieger_san @benjaminbellamy yeah. my first version was actually just a 16 bit integer id, if we exceed 65k activity types lets just change the protocol then and not worry about it now
      In conversation Wednesday, 01-Mar-2023 16:36:04 JST permalink
      lainy likes this.
    • Embed this notice
      Ademan (ademan@thebag.social)'s status on Wednesday, 01-Mar-2023 16:36:05 JST Ademan Ademan
      in reply to
      • Sexy Moon
      • Sebastian Rieger
      • :pci: Benjamin Bellamy 🇺🇸

      At least with names you probably need to be engaging with similar problems to run into a name collision

      In conversation Wednesday, 01-Mar-2023 16:36:05 JST permalink
    • Embed this notice
      Sexy Moon (moon@shitposter.club)'s status on Wednesday, 01-Mar-2023 16:36:05 JST Sexy Moon Sexy Moon
      in reply to
      • Sebastian Rieger
      • :pci: Benjamin Bellamy 🇺🇸
      @ademan @rieger_san @benjaminbellamy yeah true. i was experimenting last year a bit and also settled on numbers but what i did was hash a name+versionid to 128 bits if i revisit it i will revise it to also hash your author id into it so there's not likely to ever be a collision. 128 bits is a lot though
      In conversation Wednesday, 01-Mar-2023 16:36:05 JST permalink
    • Embed this notice
      Sexy Moon (moon@shitposter.club)'s status on Wednesday, 01-Mar-2023 16:36:06 JST Sexy Moon Sexy Moon
      in reply to
      • Sebastian Rieger
      • :pci: Benjamin Bellamy 🇺🇸
      @ademan @rieger_san @benjaminbellamy yeah it rubs me the wrong way even though theres nothing stopping two implementors on fedi from giving their new activity the same name and confusing servers
      In conversation Wednesday, 01-Mar-2023 16:36:06 JST permalink
    • Embed this notice
      Sexy Moon (moon@shitposter.club)'s status on Wednesday, 01-Mar-2023 16:36:07 JST Sexy Moon Sexy Moon
      in reply to
      • Sebastian Rieger
      • :pci: Benjamin Bellamy 🇺🇸
      @ademan @rieger_san @benjaminbellamy i got a little hung up over evend kind ids being seemingly centrally defined unless you literally can just pick a number and start coding a new event
      In conversation Wednesday, 01-Mar-2023 16:36:07 JST permalink
    • Embed this notice
      Ademan (ademan@thebag.social)'s status on Wednesday, 01-Mar-2023 16:36:07 JST Ademan Ademan
      in reply to
      • Sexy Moon
      • Sebastian Rieger
      • :pci: Benjamin Bellamy 🇺🇸

      Since it’s opaque to relays you can do whatever, but I don’t like kind ids being numeric because collisions are going to be common between people experimenting. You need to coordinate it somehow.

      (Also encoding persistence behavior into numeric ranges is super dumb)

      In conversation Wednesday, 01-Mar-2023 16:36:07 JST permalink
    • Embed this notice
      Ademan (ademan@thebag.social)'s status on Wednesday, 01-Mar-2023 16:36:08 JST Ademan Ademan
      in reply to
      • Sexy Moon
      • Sebastian Rieger
      • :pci: Benjamin Bellamy 🇺🇸

      or if they want to implement it out of spec…

      In conversation Wednesday, 01-Mar-2023 16:36:08 JST permalink
    • Embed this notice
      Sebastian Rieger (rieger_san@mastodontech.de)'s status on Wednesday, 01-Mar-2023 16:36:16 JST Sebastian Rieger Sebastian Rieger
      in reply to
      • Sexy Moon
      • :pci: Benjamin Bellamy 🇺🇸

      @Moon @benjaminbellamy @ademan that’s true! Everyone can create a NIP and the community then discuss the pros and cons.

      There is no roadmap or something like this.

      When a NIP is finalized everyone can decide if he want to implement it or noy

      In conversation Wednesday, 01-Mar-2023 16:36:16 JST permalink
    • Embed this notice
      Sexy Moon (moon@shitposter.club)'s status on Wednesday, 01-Mar-2023 16:36:17 JST Sexy Moon Sexy Moon
      in reply to
      • Sebastian Rieger
      • :pci: Benjamin Bellamy 🇺🇸
      @rieger_san @ademan @benjaminbellamy but a random guy on nostr insisted to me that nostr development is not centrally controlled
      In conversation Wednesday, 01-Mar-2023 16:36:17 JST permalink
    • Embed this notice
      Sebastian Rieger (rieger_san@mastodontech.de)'s status on Wednesday, 01-Mar-2023 16:36:18 JST Sebastian Rieger Sebastian Rieger
      in reply to
      • Sexy Moon
      • :pci: Benjamin Bellamy 🇺🇸

      @ademan @benjaminbellamy @Moon
      Nostr is an open protocol that only exists because of the nips.
      There is reference implementation, which means the specs are the only source of truth

      In conversation Wednesday, 01-Mar-2023 16:36:18 JST permalink
    • Embed this notice
      Ademan (ademan@thebag.social)'s status on Wednesday, 01-Mar-2023 16:36:19 JST Ademan Ademan
      in reply to
      • Sexy Moon
      • Sebastian Rieger
      • :pci: Benjamin Bellamy 🇺🇸

      specs aren’t always followed in practice, especially when things are rapidly changing, and that seemed to be what was happening from what @Moon said, but it turned out not to be the case.

      In conversation Wednesday, 01-Mar-2023 16:36:19 JST permalink
    • Embed this notice
      Sebastian Rieger (rieger_san@mastodontech.de)'s status on Wednesday, 01-Mar-2023 16:36:20 JST Sebastian Rieger Sebastian Rieger
      in reply to
      • Sexy Moon
      • :pci: Benjamin Bellamy 🇺🇸

      @ademan @benjaminbellamy @Moon nips are the protocol spec’s! They are up to date ?

      In conversation Wednesday, 01-Mar-2023 16:36:20 JST permalink
    • Embed this notice
      Ademan (ademan@thebag.social)'s status on Wednesday, 01-Mar-2023 16:36:21 JST Ademan Ademan
      in reply to
      • Sexy Moon
      • Sebastian Rieger
      • :pci: Benjamin Bellamy 🇺🇸

      I wonder how horribly out of date the NIPs are then https://github.com/nostr-protocol/nips/blob/master/57.md Granted I just skimmed it but it looked like lnurl was integral to the process

      In conversation Wednesday, 01-Mar-2023 16:36:21 JST permalink

      Attachments

      1. Domain not in remote thumbnail source whitelist: opengraph.githubassets.com
        nips/57.md at master · nostr-protocol/nips
        Nostr Implementation Possibilities. Contribute to nostr-protocol/nips development by creating an account on GitHub.
    • Embed this notice
      Ademan (ademan@thebag.social)'s status on Wednesday, 01-Mar-2023 16:36:22 JST Ademan Ademan
      in reply to
      • Sebastian Rieger
      • :pci: Benjamin Bellamy 🇺🇸

      zaps require lnurl? gross

      In conversation Wednesday, 01-Mar-2023 16:36:22 JST permalink
    • Embed this notice
      Sexy Moon (moon@shitposter.club)'s status on Wednesday, 01-Mar-2023 16:36:22 JST Sexy Moon Sexy Moon
      in reply to
      • Sebastian Rieger
      • :pci: Benjamin Bellamy 🇺🇸
      @ademan @rieger_san @benjaminbellamy i've received sats using plain old ln address
      In conversation Wednesday, 01-Mar-2023 16:36:22 JST permalink
    • Embed this notice
      :pci: Benjamin Bellamy 🇺🇸 (benjaminbellamy@podcastindex.social)'s status on Wednesday, 01-Mar-2023 16:36:28 JST :pci: Benjamin Bellamy 🇺🇸 :pci: Benjamin Bellamy 🇺🇸
      in reply to
      • Sebastian Rieger

      @rieger_san
      https://github.com/nostr-protocol/nips/blob/master/57.md

      In conversation Wednesday, 01-Mar-2023 16:36:28 JST permalink

      Attachments

      1. Domain not in remote thumbnail source whitelist: opengraph.githubassets.com
        nips/57.md at master · nostr-protocol/nips
        Nostr Implementation Possibilities. Contribute to nostr-protocol/nips development by creating an account on GitHub.
    • Embed this notice
      Sebastian Rieger (rieger_san@mastodontech.de)'s status on Wednesday, 01-Mar-2023 16:36:29 JST Sebastian Rieger Sebastian Rieger
      in reply to
      • Castopod :podcasting2:

      @Castopod everyone who voted with no has not heard of zap’s! They are a game changer for content creators!

      In conversation Wednesday, 01-Mar-2023 16:36:29 JST permalink
    • Embed this notice
      Castopod :podcasting2: (castopod@podlibre.social)'s status on Wednesday, 01-Mar-2023 16:36:30 JST Castopod :podcasting2: Castopod :podcasting2:

      Hmmm… Maybe too soon… ??
      #nostr

      In conversation Wednesday, 01-Mar-2023 16:36:30 JST permalink

      Attachments


      1. https://podlibre.social/system/media_attachments/files/109/943/486/098/731/510/original/0e60c331fed6b538.png

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.