Hacker Newsnew | past | comments | ask | show | jobs | submit | moritzruth's commentslogin

What CLI can I use to extract an interface from a class?


open-code run "extract interface x from class y"


I had the exactly opposite experience. I'm even selfhosting my own (non-reference implementation) PDS, and going in I was fully expecting to encounter weird consistency issues, but there were none at all.


Are you saying that wind farms think you are ugly and noisy?


Trump is ugly and noisy


Technically, depending on how "share" is to be interpreted, this addition does not retroactively make existing projects infringing.


It doesn't matter whether you technically infringe or not, that's irrelevant. It matters whether Codeberg bans your account.


First you spread the disease, then you sell the cure.


I think this is more of a “keep friends close but enemies closer” type thing.


Sounds more like “let’s make money twice”.


It's business so they have neither enemies nor friends, just various breeds of cattle to milk.


I'm not affiliated. From what I understand, they provide an open-source implementation of the relay server: https://github.com/n0-computer/iroh/tree/main/iroh-relay (which may or may not be what they actually run as part of their hosted offering).

If you use their offering, you probably get some kind of web interface for metrics that isn't open-source.


Correct


Those are intended to solve the problem at the OS layer, while Iroh (being a library) does it at the application layer.



From reading that, it lets you establish connections within your tailscale vpn. Iroh let's you establish connections between devices regardless of their network.


There might be a misunderstanding of what Tailscale offers here. There is no "VPN" in the classic "virtual network" way. With Tailscale, you can - as with Iroh, IIUC - connect arbitrary nodes to each other, where a node can be a device or an application (via tsnet). All nodes get CGNAT IPs and an addressable hostname, so there is one giant "network" of all your nodes with automatic DNS resolution baked in.


Doesn't tailscale require those all be administered and approved by one account?

> there is one giant "network" of all your nodes

From what I understand they're saying, the point is that you get easy connections to things that aren't "your" nodes, sort of like allowing me to connect one of my tailscale nodes ad-hoc to one of your tailscale nodes, when our accounts are not related in any way prior to us doing that, and without me having to allow your node onto my network or you allow one of mine onto your network and have to deal with the specialized ACLs for that, since it's just a direct connection between two nodes.


Yeah, I figured that in the mean time. It just didn’t occur to me because my use case is literally the opposite—having a secure company network where strict ACLs are the core value, not a nuisance. But if easy ad-hoc connections are your goal, Iroh sure looks like the better choice then.


I think everyone in this thread agrees on that part already.

The similarities are in an application lib to connect, and that tail net IPs correspond to device keys like in Iroh. The service using the Go library has its own Tailscale identity.


Similar on the technical level (though QUIC vs WireGuard), but that would make your app dependent on Tailscale, and require your users to have Tailscale accounts. You'd also be limited to Golang currently.

In theory you could run Headscale, but you're really working against Tailscale's intended design at that point, and Iroh was built for this from the ground up, so what is Tailscale buying you?


You don't need tailscale accounts to access tsnet (via funnel).


I think in Hyprland it just works because floating windows stay on top by definition.


When was the last time you tried? What compositor?


I stick with LTS releases so last honest attempt would have been on a Kubuntu 24.04 LTS system.

What is a compositor - thing that actually draws window content on the screen? Whatever KDE provides?

Edit: To be fair to KDE/Wayland, the Wayland Kubuntu 24.04 experience was vastly improved over Kubuntu 22.04.


You are using a 3 year old Plasma release (5.27). Give the latest Plasma a try and you should hopefully be positively surprised.


They've made major strides in the last two years. Give the next LTS a shot and I think you'll agree.


Just works out of the box without problems in Debian 13.

The only issue that I noticed it's with screen scaling doing weird things with OpenOffice.


Out of the box for you, doesn't necessarily mean it does for everyone else.



Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: