• 1 Post
  • 29 Comments
Joined 1 year ago
cake
Cake day: June 23rd, 2023

help-circle

  • I’m always privating my repos because I’m not sure if I’m doing some horrible beginner inefficiency/bad practice where I should be embarrassed for having written it, let alone for letting other people see it.

    Well that’s something not to do. Make you “horrible code” public, and ask people to do a code review. Or see what contributors want to change through a PR (if you’re so lucky). You’re not going to learn anything from others by hiding your mistakes. And no one besides you really cares if you’re committing horrible code.

    It’s pretty hard to just give generic advice on how to write clean code, but if people can just tell specifically what you can improve it’s much easier






  • Did you stop reading or are you intentionally trying to phrase it as if the universities won’t do anything? […]
    It doesn’t seem like you’re even trying to make a good faith argument.

    My first sentence and first 4 words are “So what’s stopping them?”. So did you stop reading before that - or what are you even arguing about, and where is your ‘good faith’? You’re arguing about meta-nonsense without answering

    What’s stopping them? What do they even need from “federation” or “ActivityPub” to just build this?



  • So what’s stopping them? Universities have internship programs and internal projects. In a university team of 4 people doing projects, 63x4 252 students could be assigned to a project to build this.

    But

    The french open science committee (CoSO) is indeed interested in the ActivityPub implementation in GitLab

    Good phrasing. They are “interested in the ActivityPub implementation” not “interested in the implementing ActivityPub” - so who gives a shit what a bunch of universities are interested in










  • We have seen time and again, especially on Android, that whenever a moderately-popular app goes open-source, it is immediately picked up by unscrupulous developers. They download the source, add obnoxious ads […]. tracking code […]. Finally, they publish it to the Play Store

    This is a pretty bad argument, especially when you’re specifically talking about Android. Android APKs are extremely easy to just download from closed-source, decompile them, and add new things or overwrite existing things.

    The argument makes more sense for things that are harder to decompile and recompile


  • Yea, I wasn’t saying it’s always bad in every scenario - but we used to have this kinda deployment in a professional company. It’s pretty bad if this is still how you’re doing it like this in an enterprise scenarios.

    But for a personal project, it’s alrightish. But yea, there are easier setups. For example configuring an automated deployed from Github/Gitlab. You can check out other peoples’ deployment config, since all that stuff is part of the repos, in the .github folder. So probably all you have to do is find a project that’s similar to yours, like “static file upload for an sftp” - and copypaste the script to your own repo.

    (for example: a script that publishes a website to github pages)