I’m looking to build a social platform focused on sharing multimedia content like images, GIFs, and videos, with collaborative curation features like tagging, collections, searching, downloading, etc.

Essentially the goal is to make it really easy to post, organize, discover, and collect multimedia content. I envision a mix between booru-style imageboards, Internet Archive and Lemmy.

I’m looking to use this as a learning project to get more hands-on fullstack and devops experience.

What would you all recommend technology-wise for someone starting out? I have some Python and web dev basics down, but not enough to feel comfortable just jumping into a big project.

Ideally I’d like something with good documentation/tutorials and an active community I can turn to when stuck.

Would love any suggestions on stacks to look into or good starter tutorials/books related to making the jump to a large project like this.

Thanks for any advice!

  • MajorHavoc@programming.dev
    73·
    7 months ago

    The framework, frankly, doesn’t matter. Use what you can find good help documents for and examples. Statistically, that’ll be Python or JavaScript. But use what works for you.

    The big challenge you’re going to run into is that I’m not going to create yet another login account to use your site, and no one else is either. To solve that, you’ll need activity pub.

    So while you’re picking tools, frameworks and libraries, use whatever is working for you, but do a quick check that it supports or can be made to support ActivityPub.

    Edit: This post brought to your server by - you guessed it - ActivityPub. ActivityPub: Like it or love it, you’re hearing about it through ActivityPub.

    • ericjmorey@programming.dev
      3·
      7 months ago

      Sign in with Google/Facebook/etc. bypasses the problem that ActivityPub isn’t all that popular (this may change with Threads but it’s unclear how that will play out). But I also think you’re overstating the hesitation most people have in creating an account for a service. Also, being a hobby project, it doesn’t necessarily need to be or desired to be popular right away. It doesn’t need to have all the features right away. It doesn’t have to be built in one try or architected perfectly.

      • MajorHavoc@programming.dev
        21·
        7 months ago

        Sign in with Google/Facebook/etc.

        Those are also good options. It used to be that only the Twitter SSO wasn’t a huge pain in the ass. I suspect that went away during Twitter’s “why do we have all these microservices?” era.

        But I also think you’re overstating the hesitation most people have in creating an account for a service.

        I’m really not. The majority of new account creation results in massive amounts of spam.

        I had to add SSO auth to my hobby project before I got my first user, and I got my first user shortly after.

        Also, being a hobby project, it doesn’t necessarily need to be or desired to be popular right away.

        Agreed for most hobby projects. But this one appears, to my read, to be banking on user participation.