Git Product home page Git Product logo

Comments (2)

haniawni avatar haniawni commented on June 18, 2024 3

Considering the wide variety in instance cultures, and the increasingly immense number of instances, it seems to be that the dominant factors for where a new user should go would, in the current design, only be captured through the text field on the instance description.

Instead asking about social norms or the purpose of the instance in a way that provides easy filtering to match ppl with instances they actually will enjoy being at seems to me like it'd make the site vastly more useful.

This could be done with:

  1. asking a bunch of questions, OkCupid style, of the user about extent of agreement with statements ex "I value being able to disengage from politics whenever I get overwhelmed" or "I'd like to meet other furries/scalies/etc". I worry the number of questions would soon become far too big this way, though, and every instance would need to constantly be inputting data on how they relate to new dimensions that are most likely irrelevant (ie. Is candy.land a good place to discuss BDSM techniques?)
  2. alternatively, instances could "tag" themselves with short tags- "safe space", "activism", "personal branding", "witches", "japanese only", "NSFW"- which the instance picker can then use in a search style to help guide user toward suitable instances.

I strongly prefer 2, because this data of tags can then also be used by instances when determining rules for inter-instance toot translation- an admin/user could establish a rule saying "all toots from an instance tagged "NSFW" should be auto-CW'd and auto-NSFW'd" or "I want to silence all instances that tag themselves with 'personal branding'"

from joinmastodon.

latrani avatar latrani commented on June 18, 2024

The tags idea is a really good one, though a concern I have there is seeding it; if we only have on the order of hundreds of instance entries in the DB, all self-report, we might not get enough conversion on tags for that to be better than noise.

Is there a way we can think of to try to pre-seed such a database, possibly based on the admin's self-reported "description blurb" stuff?

That might also help address something that I think alluded to in your last comment; some of this seems like it wants to be (loosely) structured, especially when it comes to defining stuff like instance social norms.

from joinmastodon.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.