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

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

Embed Notice

HTML Code

Corresponding Notice

  1. Embed this notice
    Rob Ricci (ricci@discuss.systems)'s status on Monday, 03-Nov-2025 05:20:31 JSTRob RicciRob Ricci
    in reply to
    • Darnell Clayton :verified:

    @darnell For what it's worth: here is my argument with respect to including Threads in Fediverse numbers: we should only include the number of Threads users who have turned on ActivityPub integration (seems to be something like 50k, https://fediversereport.com/why-is-meta-adding-fediverse-interoperability-to-threads/ , which is incidentally about the same number of Fediverse users who have bridge dtheir accounts to atproto/atmopshere/bluesky via bridgy). Because: let's think about Google accounts. Some of them have direct access to "the SMTP network" via gmail. We should count those as email users. But there are also lots of Google accounts that do *not* have associated gmail address. Those have no connection to "the SMTP network", and we should not count them as "email users", at least not as "google email users". Same thing with Threads users and ActivityPub.

    In conversationabout a day ago from discuss.systemspermalink

    Attachments

    1. Domain not in remote thumbnail source whitelist: fediversereport.com
      Why is Meta adding fediverse interoperability to Threads?
      from Laurens Hof
      Why is Meta adding fediverse interoperability to Threads? What is Meta's goal here?
  • 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.