the initra mf

@me@doasu.dev

Making a mess out of my OS (hey, that rhymes!)
:3 () { :3 | :3 & }; :3 >:3 # >:3c
This is free and unencumbered content released into the public domain.
pronounsthey/them
LINGUASen pl /bin/zsh
idhttps://keyoxide.org/me@doasu.dev
shitposting code athttps://code.doasu.dev/me

84 following, 23 followers

0 ★ 0 ↺

[?]the initra mf [they/them] » 🌐
@me@doasu.dev

@mkljczk@fediverse.pl @drew@social.freebitcoin.gay why do you consider it an anti-feature? /gen

My code forge () is publicly accessible, but I want to restrict some repositories (e.g., mirrors) to logged-in users, so this is perfect.

    ...

    [?]nicole mikołajczyk 🔜 piwo ➡️ gpn [she/her] » 🌐
    @mkljczk@pl.fediverse.pl

    @me @drew there’s private repos for this, no need to introduce dark patterns

      ...

      [?]Drew DeVault [he/him] » 🌐
      @drew@social.freebitcoin.gay

      @mkljczk @me it's not a dark pattern. Dark patterns are designed to manipulate users into doing something they otherwise wouldn't, for the benefit of the operator.

      Private repos cannot be cloned or accessed in any way by anyone not on the access list. A repo which enabled this hypothetical feature could still be publicly listed and git cloned.

        0 ★ 0 ↺

        [?]the initra mf [they/them] » 🌐
        @me@doasu.dev

        @mkljczk@fediverse.pl I still don't get it... :awoothink:

        My instance has ~20 users (slowly growing) so that'd mean I'd have to manually add each new user to each repo / org.
        I think it's a pretty valid use case. I'm not doing that out of malevolence either. 0.o

          History