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 mikedilger (ee11a5dff40c19a555f41fe42b48f00e618c91225622ae37b6c2bb67b76c4e49@mostr.pub)

  1. Embed this notice
    mikedilger (ee11a5dff40c19a555f41fe42b48f00e618c91225622ae37b6c2bb67b76c4e49@mostr.pub)'s status on Monday, 08-Apr-2024 10:33:26 JST mikedilger mikedilger
    Short <20 minute presentation on the Chorus Relay: https://mikedilger.com/chorus-talk.mp4
    In conversation about a year ago from mostr.pub permalink

    Attachments


  2. Embed this notice
    mikedilger (ee11a5dff40c19a555f41fe42b48f00e618c91225622ae37b6c2bb67b76c4e49@mostr.pub)'s status on Thursday, 04-Apr-2024 12:10:12 JST mikedilger mikedilger
    I'm not sure I should write down these thoughts right now while I'm not sure about them, but if you are reading this apparently I did.

    I think nostr may already be doomed for two reasons. And as a result of that, if I conclude as such, it would make sense to start working on a successor protocol. I've been taking some notes about what we should change if we started over, but that's the extent of it, I'm not working on a successor protocol. I'm only working on nostr. So don't misinterpret this note, which just represents some thoughts I've been having.

    Reason one is the misaligned incentives of note copying. The incentives are to copy your notes to every relay you can, blast them out everywhere, to get more reach. That incentive doesn't go away until and unless all the clients do the outbox model. But they don't have an incentive to change, and there are people who don't give a fuck about fixing this and argue against fixing it and argue for note copying, and there is no way in a free society to make them care. So we can never fix this, and nostr will always be centralized in practice and never what it could have been. That means nostr is doomed and unfixable and we should make sure to start differently next time so this doesn't happen again.

    Reason two is that the seed culture of nostr was far too monolithic: bitcoiners. What a culture develops into probably depends on how diverse its seed was. It's quite hard to get people onto nostr unless they are at least very bitcoin tolerant. Most people (yes, I think most) are put off by so much bitcoin promotion and related posts. Certainly people can follow anybody they want, and make their own independent cultures, perhaps even on a disjoint set of relays. But this isn't likely to happen due to the law of large numbers - there are far more ways for them to encounter and interact with the nest of bitcoiners then to not encounter and interact with them.

    These are thoughts I'm entirely unsure about. Maybe I'm wrong in both cases. These are my worries.
    In conversation about a year ago from mostr.pub permalink
  3. Embed this notice
    mikedilger (ee11a5dff40c19a555f41fe42b48f00e618c91225622ae37b6c2bb67b76c4e49@mostr.pub)'s status on Sunday, 24-Mar-2024 22:15:42 JST mikedilger mikedilger
    in reply to
    • Alex Gleason
    • fiatjaf
    Well, if someone doesn't publish a kind-10002 and instead publishes an inbox model thing, I can still secretly follow them using the gossip model (which may be by following them on one of their followers' relays)
    In conversation about a year ago from mostr.pub permalink
  4. Embed this notice
    mikedilger (ee11a5dff40c19a555f41fe42b48f00e618c91225622ae37b6c2bb67b76c4e49@mostr.pub)'s status on Sunday, 24-Mar-2024 22:15:41 JST mikedilger mikedilger
    in reply to
    • Alex Gleason
    • fiatjaf
    Someone might have a paid newsletter that is only delivered to private inboxes, each copy watermarked so they can determine if anybody leaked it and cancel that subscription.
    In conversation about a year ago from mostr.pub permalink
  5. Embed this notice
    mikedilger (ee11a5dff40c19a555f41fe42b48f00e618c91225622ae37b6c2bb67b76c4e49@mostr.pub)'s status on Sunday, 24-Mar-2024 07:07:06 JST mikedilger mikedilger
    • Alex Gleason
    • fiatjaf
    ON BLASTR:

    The main problem I have with blastr (@5be6446a) is that it works too well. So well that lots of nostr software is broken and the developers don't even know it is broken because blastr fixes it for them. It is like everybody is riding their bicycles with training wheels on, and we don't have a clear idea who what software would fall over if the training wheels came off.

    If events were not being copied (at least for a while) then the community of devs could find and fix the insufficiencies. But is that a pipe dream?

    Secondarily, I don't like the inefficiencies of copying events all over the place and I think that won't scale as nostr grows. But that is a self-correcting problem.

    ON THE INBOX MODEL:

    Outbox model is now also being challenged by "inbox model" (https://github.com/nostr-protocol/nips/discussions/1134, https://github.com/nostr-protocol/nips/pull/1135). I think these relay usage patterns can co-exist.

    These models of following people have different properties. Compared to the outbox model, the inbox model has these properties:

    * The publisher improves their reach by pushing their events to many relays
    * It is easy to see and count who is following the publisher
    * The publisher can cut you off, and you cannot follow someone secretly under this model
    * Readers only have to read from their own approved relays, not random ones they might not trust. This might also be nice for power-limited phones.
    * Worse overhead because events are copied to all the recipient relays, which might be a lot of copies.
    * It is not clear where reactions and replies go, or if everybody participating in a converstaion sees the reactions/replies of everybody else participating

    @3bf0c63f
    @alex
    In conversation about a year ago from mostr.pub permalink

    Attachments

    1. Domain not in remote thumbnail source whitelist: opengraph.githubassets.com
      Inbox model · nostr-protocol/nips · Discussion #1134
      Lots of talk about outbox model. People still discussing whether Nostr is decentralized etc. ActivityPub uses an inbox model. I think it's easier and more intuitive than an outbox model. The script...
    2. Domain not in remote thumbnail source whitelist: opengraph.githubassets.com
      nip-64: inbox model by fiatjaf · Pull Request #1135 · nostr-protocol/nips
      just throwing out the idea, I don't know if it is worth exploring. read here: https://github.com/nostr-protocol/nips/blob/inbox-model/64.md from the text: The approach described in this NIP doesn'...
  6. Embed this notice
    mikedilger (ee11a5dff40c19a555f41fe42b48f00e618c91225622ae37b6c2bb67b76c4e49@mostr.pub)'s status on Friday, 22-Mar-2024 12:48:24 JST mikedilger mikedilger
    • Alex Gleason
    We'll send them to you, and you can figure out what to do with them.
    In conversation about a year ago from mostr.pub permalink
  7. Embed this notice
    mikedilger (ee11a5dff40c19a555f41fe42b48f00e618c91225622ae37b6c2bb67b76c4e49@mostr.pub)'s status on Thursday, 22-Feb-2024 11:00:32 JST mikedilger mikedilger
    in reply to
    • Alex Gleason
    If this becomes popular among a political tribe, that tribe will win. I guarantee it.
    In conversation about a year ago from mostr.pub permalink
  8. Embed this notice
    mikedilger (ee11a5dff40c19a555f41fe42b48f00e618c91225622ae37b6c2bb67b76c4e49@mostr.pub)'s status on Saturday, 17-Feb-2024 05:48:28 JST mikedilger mikedilger
    Nostr is a giant shit show. The fact that our software interoperates at all is a miracle and probably just a temporary anomaly. Given enough time, the relentless breaking changes being made to published NIPs will eventually break everything.

    Linux succeeded because "WE DO NOT BREAK USERSPACE". For nostr to succeed, changes must "NOT BREAK EXISTING IMPLEMENTATIONS". There shouldn't be any exceptions to that EVEN IF THE IMPLEMENTATION WAS NON-COMPLIANT.

    Pay close attention to Linus right here:

    > Are you saying that pulseaudio is entering on some weird loop if the
    > returned value is not -EINVAL? That seems a bug at pulseaudio.

    Mauro, SHUT THE FUCK UP!

    It's a bug alright - in the kernel. How long have you been a
    maintainer? And you *still* haven't learnt the first rule of kernel
    maintenance?

    If a change results in user programs breaking, it's a bug in the
    kernel. We never EVER blame the user programs. How hard can this be to
    understand?

    Linus doesn't want to break pulseaudio EVEN THOUGH pulseaudio was doing the wrong thing.

    It seems like every week I find a NIP that I've coded for has changed. This last week I think it happened three times already. Sometimes it's a small change and I quickly update my code. But I can't read all the PRs, and I'm afraid dozens of small changes have slipped past my notice. Gossip is probably now incompatible with multiple other implementations which happen to have implemented different versions of the same NIPs (some older, some newer).

    Even if we didn't have any breaking changes, the simple fact that different software implements different optional NIPs itself presents to end users like broken software. Why does it work in Damus but not Amethyst? Why does it work in Amethyst but not Coracle? That is an even harder problem to solve.

    But let's at least solve the easier problem and stop changing NIPs. If you don't like a NIP make a new one, don't break the current one. Even if you think the current one sucks balls and should have never happened. Even if you think there aren't many implementations out there.
    In conversation about a year ago from mostr.pub permalink
  9. Embed this notice
    mikedilger (ee11a5dff40c19a555f41fe42b48f00e618c91225622ae37b6c2bb67b76c4e49@mostr.pub)'s status on Tuesday, 23-Jan-2024 12:35:41 JST mikedilger mikedilger
    in reply to
    • Alex Gleason
    I MAY define MUST and you SHOULD heed the definition or I SHALL object!
    In conversation about a year ago from mostr.pub permalink
  10. Embed this notice
    mikedilger (ee11a5dff40c19a555f41fe42b48f00e618c91225622ae37b6c2bb67b76c4e49@mostr.pub)'s status on Tuesday, 23-Jan-2024 11:54:22 JST mikedilger mikedilger
    in reply to
    • Alex Gleason
    You should drink some water after that. I bet it will taste amazing.
    In conversation about a year ago from mostr.pub permalink
  11. Embed this notice
    mikedilger (ee11a5dff40c19a555f41fe42b48f00e618c91225622ae37b6c2bb67b76c4e49@mostr.pub)'s status on Tuesday, 23-Jan-2024 04:34:52 JST mikedilger mikedilger
    • Alex Gleason
    • Karnage
    The reason he left Twitter is because they *didn't* kick off Alex Jones yet. I'm not sure he's ready to accept a world that contains people he doesn't like. Little Wesley Crusher still has some growing up to do.

    That being said, I'd be happy for him to join us.
    In conversation about a year ago from mostr.pub permalink
  12. Embed this notice
    mikedilger (ee11a5dff40c19a555f41fe42b48f00e618c91225622ae37b6c2bb67b76c4e49@mostr.pub)'s status on Sunday, 19-Nov-2023 12:18:12 JST mikedilger mikedilger
    in reply to
    • Alex Gleason
    That is a special ops turtle
    In conversation Sunday, 19-Nov-2023 12:18:12 JST from mostr.pub permalink
  13. Embed this notice
    mikedilger (ee11a5dff40c19a555f41fe42b48f00e618c91225622ae37b6c2bb67b76c4e49@mostr.pub)'s status on Thursday, 16-Nov-2023 16:46:39 JST mikedilger mikedilger
    in reply to
    • Alex Gleason
    I share your lack of appreciation of Family Guy. In fact after not seeing anything funny on TV in years, I turned mine off and didn't bother to install one in my new house.
    In conversation Thursday, 16-Nov-2023 16:46:39 JST from mostr.pub permalink
  14. Embed this notice
    mikedilger (ee11a5dff40c19a555f41fe42b48f00e618c91225622ae37b6c2bb67b76c4e49@mostr.pub)'s status on Thursday, 16-Nov-2023 12:17:30 JST mikedilger mikedilger
    > what kind of event you want to see next

    I want to see a kind 30023 event next (that was a little nostr humor)
    In conversation Thursday, 16-Nov-2023 12:17:30 JST from mostr.pub permalink
  15. Embed this notice
    mikedilger (ee11a5dff40c19a555f41fe42b48f00e618c91225622ae37b6c2bb67b76c4e49@mostr.pub)'s status on Thursday, 16-Nov-2023 07:39:47 JST mikedilger mikedilger
    in reply to
    • Alex Gleason
    Keeping animals alive forever is going to require the terraforming of Mars. Do you support terraforming of Mars and do you support the forcible transfer of animals (a possible crime against animality) to the terraformed Mars so that they do not die of Malthusian starvation here on an overcroweded Earth?
    In conversation Thursday, 16-Nov-2023 07:39:47 JST from mostr.pub permalink
  16. Embed this notice
    mikedilger (ee11a5dff40c19a555f41fe42b48f00e618c91225622ae37b6c2bb67b76c4e49@mostr.pub)'s status on Thursday, 16-Nov-2023 05:37:23 JST mikedilger mikedilger
    • Alex Gleason
    well obviously
    In conversation Thursday, 16-Nov-2023 05:37:23 JST from mostr.pub permalink
  17. Embed this notice
    mikedilger (ee11a5dff40c19a555f41fe42b48f00e618c91225622ae37b6c2bb67b76c4e49@mostr.pub)'s status on Wednesday, 15-Nov-2023 06:16:56 JST mikedilger mikedilger
    in reply to
    • Alex Gleason
    > Remember! You can't brin guns to the airport.

    Only in Texas
    In conversation Wednesday, 15-Nov-2023 06:16:56 JST from mostr.pub permalink
  18. Embed this notice
    mikedilger (ee11a5dff40c19a555f41fe42b48f00e618c91225622ae37b6c2bb67b76c4e49@mostr.pub)'s status on Monday, 09-Oct-2023 14:31:14 JST mikedilger mikedilger
    in reply to
    • Alex Gleason
    • fiatjaf
    Because AFAICT by the example, what is desired to be expressed is Alex is associated with gleasonator.com and also associated with mostr.pub. Which to me means that Alex could wish to have two different NIP-05 addresses. Which isn't currently a supported thing.
    In conversation Monday, 09-Oct-2023 14:31:14 JST from mostr.pub permalink

    Attachments

    1. No result found on File_thumbnail lookup.
      Gleasonator
  19. Embed this notice
    mikedilger (ee11a5dff40c19a555f41fe42b48f00e618c91225622ae37b6c2bb67b76c4e49@mostr.pub)'s status on Monday, 09-Oct-2023 14:31:14 JST mikedilger mikedilger
    • Alex Gleason
    • fiatjaf
    I don't know what alex@gleasonator.com@mostr.pub means. Explain in English what that is supposed to signify.
    In conversation Monday, 09-Oct-2023 14:31:14 JST from mostr.pub permalink

    Attachments

    1. No result found on File_thumbnail lookup.
      Gleasonator
  20. Embed this notice
    mikedilger (ee11a5dff40c19a555f41fe42b48f00e618c91225622ae37b6c2bb67b76c4e49@mostr.pub)'s status on Saturday, 16-Sep-2023 13:24:46 JST mikedilger mikedilger
    I think the only person in recorded history who was hated by the establishment more than Donald Trump was Jesus. And maybe not even Jesus.
    In conversation Saturday, 16-Sep-2023 13:24:46 JST from mostr.pub permalink
  • Before

User actions

    mikedilger

    mikedilger

    Author of Gossip client: https://github.com/mikedilger/gossip expat American living in New Zealand

    Tags
    • (None)

    Following 0

      Followers 0

        Groups 0

          Statistics

          User ID
          106896
          Member since
          14 Mar 2023
          Notices
          39
          Daily average
          0

          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.