Source forges like Gitlab, Gitea, Forgjo, Github, and others do not allow directly leaving comments on code. However, they all do allow leaving comments on pull/merge requests and individual commits. This unfortunately doesn't work for snippets like Gitlab Snippets, Github Gists, etc. .

We can however use these to our advantage and use workarounds in order to make certain parts of our code reviewable:

Snippets

Create a repository to host your snippets (if you don't have one already), add your snippet of code as one commit to the repository (can be in a throwaway branch, the master branch, whatever). Share that commit link!

Larger changes

If you have code that belongs together, it is already in your repository, and is spread out over multiple commits, fear not! Once again, you can use the power of temporary branches. With these methods you can even have your entire repo reviewed.

A commit to review

Create a new branch, delete the parts of the code you want reviewed, create a revert commit, and share that link!

A PR to review

This requires 2 branches. If you've read the steps above, you already know where this is going.

Create a branch (deleted), delete the code and commit it. Create a new branch (revert) from this point and revert the previous commit. Now you can push both branches to your source forge and create a new merge request to merge revert into deleted.

If you have other tips, share them!

Many of us write opensource code in a void: nobody ever looks at it, uses it nor reviews it. We are the only users and authors.

In order to improve, where can we get our code reviewed? I don't mean professionally, just from like-minded individuals.

This is a discussion on Python's forums about adding something akin to a throws keyword in python.

And I'll show you YAML

(a continuation of this post)

Where are Purism, System76, Tuxedo Computers, Starlabs, SlimbookES, and others? Instead there's Dell, HP, ASUS, and Fujitsu...

You too can contribute to I2P, fellow anonymity supporter

https://www.ovhcloud.com/en/vps/

Pick Ubuntu 22.04 as your OS and follow the instructions on https://geti2p.net/en/download/debian

You can ssh -L 7657:localhost:7657 ubuntu@yourhostname, login with the password you from the link you got in the email, then open http://localhost:7657 and configure your I2P instance. For the bandwidth, you can enter 12500 up and 12500 down (100Mb/s = 12500 KB/s) with a 90% share (if you aren't using the VPS for anything else).

You can also add more tunnels on http://localhost:7657/configtunnels . For more information on tunnel types (exploratory and client) see https://geti2p.net/en/docs/how/peer-selection .

Like a TUI version of stuff like in the picture?

Basically a settings dialog with:

• all nvim options (in sections)
• a plugin section with
• installed plugins
  • toggle
  • configuration options
• available plugins

I was wondering why my speed was only about 250KB/s and I think this is why: there simply aren't many high speed nodes in the network!

If you have a VPS sitting around, just spinning, do consider contributing.

With a simple docker-compose

version: "3.5"
services:
    i2p:
        image: geti2p/i2p
        container_name: i2p
        restart: always
        volumes:
            - ./i2pconfig:/i2p/.i2p
        network_mode: host

you can have i2p running in no time. Or follow the official installation instructions

Simply SSH with a local port forwarding to the router console ssh -L 7657:127.0.1.1:7657 $yourHost and open http://localhost:7657/

You can then configure your instance to share bandwidth.

It was announced about one year ago

If lemmy had user-defined filters, I'd use them. Right now I'm downvoting the stuff, but there's already a community for musk-related stuff: !EnoughMuskSpam@kbin.social