• 2 Posts
  • 44 Comments
Joined 2 years ago
cake
Cake day: December 31st, 2023

help-circle



  • Same, it’s impressive how much it irks people.

    My own hasty judgement is that [those upset] only speak English, have a prescriptivist take on language (albeit unconsciously), and have no idea how damaging hegemony and uniformity for their own sake can be.

    Also they’re lazy and would rather shame someone than take on a little bit of discomfort to adapt to them.

    I guess that makes it “judgements”, plural.



  • For instances that already have a user base, admins should not make any significant decisions without the consent of their users. This goes against our values, and we will not permit an instance to use Bridgy Fed in this manner. We’ve had conversations on how to handle a situation like this, and we would block instances [3] from doing so. We strongly expect admins to be loud about bridging, especially during signup. 3/10

    This is very encouraging to read from a project that initially did not understand why many would be opposed to an opt-out bridge to ATProto.





  • This would be great but how do you train an LLM to act as you? You’d need to be recording your thoughts and actions, not only every bit of speech you utter and every character you type on a device.

    And as far as I’m aware, we don’t know how to rapidly nor efficiently train transformer-based architectures anywhere near the size needed to act like chatgpt3.5, let alone 4o etc, so you’ll also need to be training this thing for a while before you can start using it to introspect - by which point you may already no longer behave the same.



  • Ok but if it allows anubis to judge the soul of my bytes as being worthy of reaching a certain site I’m trying to access, then the program is not making any calculations that I don’t want it to.

    Would the FSF prefer the challenge page wait for user interaction before starting that proof of work? Along with giving them user a “don’t ask again” checkbox for future challenges?


  • To my knowledge, there is 1 feature that forgejo has that gitea doesn’t: it can generate a new ssh key for you at the click of a button that can be used to push repo changes to another git forge.

    I have several personal repos on my forgejo instance that are each setup so that they mirror themselves onto my Codeberg account at noon every day.

    I also have a gitea instance on a raspi on my local network that itself will push out changes on certain repos to the (public-facing) forgejo instance.

    I can push and/or pull to any of the three origins as needed, but usually I just push to the gitea when I’m at home and the forgejo when I’m not, and let the mirroring take care of propagating changes to Codeberg.