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
    Metro (metro@newsie.social)'s status on Sunday, 20-Nov-2022 21:35:58 JST Metro Metro
    • Alex Gleason
    • Eugen Rochko

    Question: on my private instance (just abandoned) I was following many from Mastodon.social but not seeing any posts from Mastodon.social in my federated timeline. My instance wasn't on the Mastodon.social "blocklist." Do some instances shadow ban other instances without adding them to the "official" blocklist?

    Or is Mastodon inefficient at times (now) that the feeds of some slammed instances won't populate to the Federated timeline you're able to view from your timeline?
    @Gargron
    @graf@poast.org
    @alex

    In conversation Sunday, 20-Nov-2022 21:35:58 JST from newsie.social permalink
    • admin repeated this.
    • Embed this notice
      Metro (metro@newsie.social)'s status on Sunday, 20-Nov-2022 21:35:56 JST Metro Metro
      in reply to
      • admin
      • Admin

      @Graf@poa.st
      @admin@home.social
      @admin@mastodon.tech

      Question: on my private instance (just abandoned) I was following many from Mastodon.social but not seeing any posts from Mastodon.social in my federated timeline. My instance wasn't on the Mastodon.social "blocklist." Do some instances shadow ban other instances without adding them to the "official" blocklist?

      Or is Mastodon inefficient at times that the feeds of some slammed instances won't populate to the Federated timeline you're able to view from your timeline?

      In conversation Sunday, 20-Nov-2022 21:35:56 JST permalink
    • Embed this notice
      admin (admin@mastodon.tech)'s status on Sunday, 20-Nov-2022 21:36:39 JST admin admin
      in reply to

      I don’t know the answer but I’ll boost your post in hopes of helping you find it.

      In conversation Sunday, 20-Nov-2022 21:36:39 JST permalink
      admin likes this.
    • Embed this notice
      Linux Renaissance (darth@silversword.online)'s status on Sunday, 20-Nov-2022 22:40:27 JST Linux Renaissance Linux Renaissance
      in reply to
      • admin

      @admin @Metro I see your boost, so it federates fine on my instance.

      In conversation Sunday, 20-Nov-2022 22:40:27 JST permalink
      admin likes this.
    • Embed this notice
      Metro (metro@newsie.social)'s status on Monday, 21-Nov-2022 00:39:42 JST Metro Metro
      in reply to
      • admin
      • Linux Renaissance

      @darth @admin

      Thank you sincerely Darth ?

      In conversation Monday, 21-Nov-2022 00:39:42 JST permalink
      admin likes this.
    • Embed this notice
      Metro (metro@newsie.social)'s status on Monday, 21-Nov-2022 00:42:38 JST Metro Metro
      in reply to
      • Eugen Rochko
      • admin
      • Jeff ( #TeamNormal )
      • Admin

      @jeff @admin@home.social @admin@mastodon.tech

      Thanks Jeff. It's sad that when I follow users from other instances, I can only see their posts from after the time I follow then and not from before. The local timelines of each instance will always be missed by anyone not on that server. I know @Gargron has talked about removing the "local timeline" feature and I hope he does so that everyone shares a Federated timeline.

      I hope Mastodon changes as we are missing out on much content that you would see on Twitter.

      In conversation Monday, 21-Nov-2022 00:42:38 JST permalink
    • Embed this notice
      Jeff ( #TeamNormal ) (jeff@newsie.social)'s status on Monday, 21-Nov-2022 00:42:39 JST Jeff ( #TeamNormal ) Jeff ( #TeamNormal )
      in reply to
      • admin
      • Admin

      @Metro @admin@home.social @admin@mastodon.tech

      Newsie.social doesn't shadowban instances.

      You can view the moderated instances, and why at newsie.social/about

      In conversation Monday, 21-Nov-2022 00:42:39 JST permalink
      admin repeated this.
    • Embed this notice
      admin (admin@mastodon.tech)'s status on Monday, 21-Nov-2022 00:45:50 JST admin admin
      in reply to
      • Alex Gleason
      • Eugen Rochko
      • Eric Shields | ?assTransitKrow

      I agree with doing away with local-instance timelines.

      In conversation Monday, 21-Nov-2022 00:45:50 JST permalink
      admin likes this.
    • Embed this notice
      Metro (metro@newsie.social)'s status on Monday, 21-Nov-2022 00:45:52 JST Metro Metro
      in reply to
      • Alex Gleason
      • Eugen Rochko
      • Eric Shields | ?assTransitKrow

      @masstransitkrow @alex @Gargron

      I appreciate that ?

      What is the most effective way to lobby @Gargron to consider removing local server timelines so that everyone more closely shares info like Twitter? Are there unions on Mastodon for petition drives?

      Do you agree that local timelines should be removed so everyone will stop crowding onto Mastodon.social? Although they say "spread out," local timelines are a HUGE advantage for large instances. It would be advantageous to be all on 1 server

      In conversation Monday, 21-Nov-2022 00:45:52 JST permalink
    • Embed this notice
      Eric Shields | ?assTransitKrow (masstransitkrow@federation.ninetiesmysteri.es)'s status on Monday, 21-Nov-2022 00:45:53 JST Eric Shields | ?assTransitKrow Eric Shields | ?assTransitKrow
      in reply to
      • Alex Gleason
      • Eugen Rochko
      @Metro @Gargron @alex the federated timeline populates on a need to know basis. Whatever shows up there is the sum of all interactions made by a server that wishes to communicate with you, or interactions made to the third degree. When you create a new instance, all three timelines will start empty and it generally takes 48 hours for other instances to see you. Also, due to mastodon.social's very large size, it may take longer for those posts to federate. Also, you mis-mentioned graf.
      In conversation Monday, 21-Nov-2022 00:45:53 JST permalink
    • Embed this notice
      Alex Gleason (alex@gleasonator.com)'s status on Monday, 21-Nov-2022 00:56:22 JST Alex Gleason Alex Gleason
      in reply to
      • Eugen Rochko
      • Eric Shields | ?assTransitKrow
      @Metro @masstransitkrow @Gargron

      What is the most effective way to lobby @Gargron to…

      You have the wrong philosophy. It’s open source. The best approach is pictured below:

      In conversation Monday, 21-Nov-2022 00:56:22 JST permalink

      Attachments


      1. https://media.gleasonator.com/c51aaa3ddf26c784b73ba81733b08391a9a0fd4366e843ed3a7d01cfb9f6c237.jpg
    • Embed this notice
      Alex Gleason (alex@gleasonator.com)'s status on Monday, 21-Nov-2022 01:41:47 JST Alex Gleason Alex Gleason
      in reply to
      • Eugen Rochko
      • Eric Shields | ?assTransitKrow
      • Corfiot

      @corfiot @masstransitkrow @Gargron There are at least 5 notable Mastodon forks under active development, and at least 100 actively used by servers.

      We need to get out of the consumer mindset and into the Genghis Khan mindset. There’s no CEO or treaty organization. The way to win is by force. Force doesn’t mean bullying devs, it means building the best product with the most users, so that you can’t be ignored.

      In conversation Monday, 21-Nov-2022 01:41:47 JST permalink
    • Embed this notice
      Corfiot (corfiot@pleroma.elementality.org)'s status on Monday, 21-Nov-2022 01:41:49 JST Corfiot Corfiot
      in reply to
      • Alex Gleason
      • Eugen Rochko
      • Eric Shields | ?assTransitKrow
      @alex @masstransitkrow @Gargron he still has to approve the PR tho. Not everyone can maintain a fork and (let's face it) it's gonna be ignored unless it's supported by a whole team.
      In conversation Monday, 21-Nov-2022 01:41:49 JST permalink
    • Embed this notice
      Eric Shields | ?assTransitKrow (masstransitkrow@federation.ninetiesmysteri.es)'s status on Monday, 21-Nov-2022 01:46:15 JST Eric Shields | ?assTransitKrow Eric Shields | ?assTransitKrow
      in reply to
      • Alex Gleason
      • Eugen Rochko
      he's saying that if you want certain features you could bake them in yourself, and that'd require you to learn Ruby, which Mastodon is built with.

      But I strongly suggest you look into Glitch.

      Having three timelines is pretty dang equitable if you ask me. But if you want a domain to not be visible from the timeline, you can mute that domain and those posts would vanish on refresh.
      In conversation Monday, 21-Nov-2022 01:46:15 JST permalink
      Alex Gleason likes this.
    • Embed this notice
      Metro (metro@newsie.social)'s status on Monday, 21-Nov-2022 01:46:17 JST Metro Metro
      in reply to
      • Alex Gleason
      • Eugen Rochko
      • Eric Shields | ?assTransitKrow

      @alex @masstransitkrow @Gargron

      To make sure I understand, youre suggesting i learn Ruby on Rails and make a commit to the Mastodon Github of the change I seek to do away with local server timelines?

      Do you agree with me @alex that the Mastodon would be a more equitable platform and more like Twitter if we ended local server timeline?

      In conversation Monday, 21-Nov-2022 01:46:17 JST permalink
    • Embed this notice
      Alex Gleason (alex@gleasonator.com)'s status on Monday, 21-Nov-2022 01:50:49 JST Alex Gleason Alex Gleason
      in reply to
      • Eugen Rochko
      • Eric Shields | ?assTransitKrow
      • Corfiot

      @corfiot @masstransitkrow @Gargron If mainline Mastodon doesn’t want it, maybe Glitch, Fedibird, Qoto, or various others will.

      If nobody else wants that patch, maybe it’s not such a good idea. That’s natural selection.

      If the idea is good but belongs to a bigger picture that hasn’t been tapped into yet, it’s time to form a new community around it.

      In conversation Monday, 21-Nov-2022 01:50:49 JST permalink
    • Embed this notice
      Corfiot (corfiot@pleroma.elementality.org)'s status on Monday, 21-Nov-2022 01:50:51 JST Corfiot Corfiot
      in reply to
      • Alex Gleason
      • Eugen Rochko
      • Eric Shields | ?assTransitKrow
      @alex @masstransitkrow @Gargron
      I see your point, still a single guy wanting to make a small patch will not fork the whole thing. He'll go for the pull request.

      If that is not approved THEN he'll probably fork and use his fork but it'll be basically just a running copy, until a merge conflict happens and then who knows. So the 100 forks are good, but not effective as the 5 notable/big ones.

      If the dev has time to make many patches, I say yes, get on board with one of the 5 major forks from the start and deny the original project the feature as a way to force change.
      In conversation Monday, 21-Nov-2022 01:50:51 JST 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.