Heres a little guide for how to tag your community properly for it to get pulled into showing up on https://pangora.social/join . First youll need to get added to the whitelist by making an issue on the repository or asking me.

The tags used on the site follow a pattern

  • If the category has no subcommunities then the tag to show up there is usually its name or something similar to its name in lower kebab case
  • If the category has subcommunities then the tag to show up in the “general” category of the tag is the same as above but then -general if added onto the end

For example some of the tags for the technology category and subcategories are:

  • technology-general
  • programming-general
  • web-development
  • game-development
  • ai
  • radio
  • cybersecurity

Ill be exposing a full tag list once I get the feature fully set up in pangora.social (still in Ludum Dare mode but should hopefully happen in the second half of this month (for now ill make a comment here with them)

If you add tags it wont show up until then but you can do it now to get it set up

Its recommended to only tag your instance for topics youre catered towards or have a large community for. General communities that dont focus on one kind of content can just tag themselves as “general”

As an example of tagging. Heres the current tag setup for programming.dev programming programming-general game-development web-development

the programming tag is useless in the eyes of pangora.social but I like doing it to show that youre in that category of content for other uses in fediseer. programming-general lets us show up in the general programming category since were a general programming instance. game-development and web-development are tagged since we currently have the largest communities for both topics

If you have any suggestions for new categories let me know

  • Ategon@lemmy.dbzer0.comOP
    link
    fedilink
    English
    arrow-up
    1
    ·
    9 months ago
    • technology-general
    • programming-general
    • web-development
    • game-development
    • ai
    • radio
    • cybersecurity
    • monero
    • gme
    • gaming-general
    • star-citizen
    • magic-the-gathering
    • life-is-strange
    • diyrpg
    • ttrpg
    • warframe
    • soulframe
    • starfield
    • lgbtq+
    • furry
    • anarchist
    • blind
    • neurodivergence
    • cypherpunk
    • marxist-leninist
    • political-compass
    • memes
    • entertainment-general
    • television-general
    • star-trek
    • literature
    • anime
    • piracy
    • science-general
    • solarpunk
    • futurology
    • sports
    • creative-general
    • audio
    • visual-arts
    • writing
    • performing-arts
    • video-production
    • photography
    • nsfw
    • australia
    • brazil
    • canada
    • denmark
    • france
    • germany
    • italy
    • malaysia
    • netherlands
    • new-zealand
    • poland
    • portugal
    • sweden
    • united-kingdom
    • usa-midwest
    • general
  • db0@lemmy.dbzer0.comM
    link
    fedilink
    English
    arrow-up
    1
    ·
    9 months ago

    I guess you’re going to continue maintaining both manual org, and just appending fediseer tags to it?

  • db0@lemmy.dbzer0.comM
    link
    fedilink
    English
    arrow-up
    1
    ·
    9 months ago

    Out of curiosity, why require manual approval before on-boarding them? I think you could rely on censures to kick out onboard problematic instances and allow your selection choice to grow automatically.

    • Ategon@lemmy.dbzer0.comOP
      link
      fedilink
      English
      arrow-up
      2
      ·
      9 months ago

      helps me control it a bit better while I get the system setup. Can swap to an auto system in the future

      For your other comment, yeah im going to merge the tags ive currently done to the stuff set in fediseer. And then also add on pangora instance flairs onto there so theres 3 different sources its pulling from