It’s documented in the wiki, they are called VCS packages, and it’s not the usual, they work a bit differently: https://wiki.archlinux.org/title/VCS_package_guidelines

You can see in this instance, that it skips the sha checking for upstream source, in line 15 of the PKGBUILD it says ‘SKIP’: https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=hyprspace-git#n15

sha1sums parameter is documented in the wiki: https://wiki.archlinux.org/title/PKGBUILD#sha1sums

In the PKGBUILD file you can list sources (line 12,13) and their respective checksums (line 14,15). In this PKGBUILD there are 2 sources: the first is the systemd unit file, it’s coming from the package’s AUR repo, not from upstream, you can see its checksum. The second source is the actual source, and you can see, it’s checksum is ‘SKIP’ so it shouldn’t be checked.

With these kind of packages you can’t get notified if there is an update available, but if you install it again with your favorite AUR helper it would update itself for the latest version. It calculates version number from the latest commit hash, before building and installing, so if that is the same it won’t update again.

Nix just calls the *.nix files, it’s still go under the hood. PKGBUILD is similar to the flake.nix and package.nix files to me, but I have no experience with nix.

My general view is similar, yaml is better if it should be written by humans, json is better if it should be written and read only by a machine. but hyprspace uses json for configuration, so I don’t really understand cellardoor’s comment

what:
  is:
  your:
    - problem
    - with:
      YAML
# At least you can have comments unlike in json. Who need comments in a config file anyway.

Or port forwarding. You have to open a udp port for wireguard

AUR packages ending with"-git" or “-svn” always pull the latest commit from source. The version number means that was the last time the packager had to change something on the PKGBUILD script, not the actual version which would be installed.

Where should I look? Where were these talks? I’m interested.

Edit: I found the whitepaper about hole punching: https://research.protocol.ai/publications/decentralized-hole-punching/

It says it connects to a “Hole Punch Coordination (DCUtR - Direct Connection Upgrade through Relay)”. So for NAT traversal to work, you need a third party, this relay. As I expected. I guess you can self host this, but than you could just host a wireguard server. I guess if you are on a locked down network where you cannot connect to any relay (e.g. how the Chinese Great Firewall works technically they could block it) you can’t initiate a connection behind a NAT.

Nonetheless it seems interesting, but no magic here. Maybe the big difference that the relay servers are distributed, so no central authority to block easily.

Interesting, it’s on AUR, I will try it.

So it doesn’t need any port forwarding, and works on CGNAT? How the “NAT hole punching” works? Both clients connect to something on IPFS?

Afaik, for DHT with torrent, clients need to know at least one tracker, what is the “tracker” here? Something on IPFS? Who am I sending my IP addresses?

How much overhead does this add to speed? I love with Wireguard, that it’s barely noticeable, really close to p2p speeds, OpenVPN was awful in this regard.

Thank you for the clarification, I understand what is your issue now

It would be hard to get the context, and you could totally misunderstood the thread, e.g. from your hidden comment everyone get that replies are sarcastic, but you don’t.

Maybe an “temporarily unhide blocked user’s comment and replies” button to show the whole thread.

There are instances where downvotes are disabled, if you don’t like them you can just use an instance like that.

Downvotes are public and not anonymous, but they are hidden in Lemmy ui. Afaik you can see who downvotes your posts from Piefed or Mbin. See this thread: https://lemmy.world/post/18805474 or this: https://piefed.social/post/205362

Keyboard navigation. I know about https://github.com/vmavromatis/Lemmy-keyboard-navigation but it’s annoying that I have to use an addin/userscript for such a basic feature.

Option for default comment sorting. you can change the default sort only for posts, but not for comments, comments always sorted by Hot, and you have to manually change it each time you open comments.

In Voyager you can set this up, but it would be useful in the webui as well.

Workaround: use multiline code blocks with defined language, e.g:

systemctl --user cat emacs
pactl load-module module-switch-on-connect

Drawback: you cant use it in a list or inline

If you don’t need fancy gui and authentication, registry is easy to set up and works really well: https://hub.docker.com/_/registry

I have several addresses at cock.li. Uptime is not the best, around 98%, but free. According to their policy they don’t collect any personal data, but they comply with legal requests. https://cock.li/help

You can select from a lot of domains, some of them ar normal like firemail.cc or airmail.cc, some of them are funny like aaathats3as.com, some of them are edgy like cocaine.ninja or national.shitposting.agency, some of them are racist like nuke.africa or hitler.rocks

but I don’t see how what I am proposing would make things more difficult?

Now when a user reports a troll, the report goes to the moderators of the community. But in special cases the admins of the user instances should deal with banning. So the admins of the community instances have to deal with reports, but the solution is at the hand of the user instance admins. It’s the same as dealing with users from other instances, but an edge case.

My recommendations would be something like this: (I’m just a random user, so it’s just my point of view)

• Shut down the fully inactive instances. Noone will even even notice it
• Merge the semi active communities to a handful of instances, like sports and technology… . I’ve seen active communities move instances, it would be possible, take a look how !europe@feddit.de migrated to !europe@feddit.org. Give enough time for subscribers to notice and subscribe to the new one.
• Allow registration of moderators on these instances, so they can work around the current limitations of moderation tools. Maybe an invite only solution or something like this.
• You could find help more easily if you look for admins for 3-4 instances instead of for 18 instances.

This would be useful for you and other admins, because you would have to admin much less number of instances. They would be still considered small instances, compared to big one, so you still not at the “too big to fail” level. For users it would help community discovery, there are overlap between followers of similar topics, e.g. I have friends who follow both European football and NBA at the same time, I read both selfhosting related topics and about general tech support, etc…

I don’t like this kind of community/user instance because 2 instances have to deal with the same problem. E.g. a rogue user can troll on most community instances until they are banned by their user instance.

The instance fragmentatios is not as big issue as it’s quite easy to create new accounts. There was a thread about this some days ago here, I also use different accounts on different instances for different topics.

If a moderator is from a different instance, can they effectively moderate? So isn’t it a problem if all moderators would be from different instances?

I remember after the exodus community discovery in Lemmy was hard, and it made sense to create instances like these. But nowadays with Lemmy Explorer and with multiple community promo communities I think it’s not really hard to find the topics you are interested in.

Use WSL on the laptop for ssh, that’s actually a VM. VM separation should work correctly, or we have a much bigger problem. Just reset WSL, everything should be wiped related to the ssh sessions. Work IT would maybe allow that.

One of them is a laptop, why ssh to the server isn’t an option? Set up tmux on the server so it always connects to the same session, so you can just continue where you left last time. If you need desktop support, rdp in gnome works really well.

E.g if you connect with this command, and tmux is installed on the server, it will start a new session named “main”. If a session with that name exists it will connect to that:

ssh -t pi@192.168.1.2 tmux new-session -A -s main

Add something to .bashrc on the server to always do the same if you work on that phisically:

if command -v tmux &> /dev/null && [ -n "$PS1" ] && [[ ! "$TERM" =~ screen ]] && [[ ! "$TERM" =~ tmux ]] && [ -z "$TMUX" ]; then
tmux new-session
fi