Politely, but no.

It’s a compression tool that is also used to mask malware, and you’re proposing to expand it’s use in a use case that’s ALREADY coated in enough malware to give you herpes just by walking past your average tracker.

It’s a bad idea from a security perspective, and it’s not going to outperform a LZMA-based compression tool using a large dictionary (7zip, etc.) which also isn’t fucking with binaries in a way that makes detecting and preventing malicious software more complicated for the average user, who typically knows absolutely zero about what’s going on.

Sorry, I meant antivirus. (Corpo IT calls it endpoint, since it’s, well, the endpoint.)

Pack what executables exactly?

Like take a copy of Nodobe Notoshop and repack it?

If that’s what you mean, uh, politely, but fuck no. Malware is enough of a problem that there’s no way I’d want to start downloading crap that’s been UPXed since that’s going to make it impossible to determine if it’s legitimate or not by (most) endpoint tools, or they’ll just see UPX and go ‘bad shit!’ on everything.

Wait you’re saying 30 year old drives are all dying or dead?

I, for one, am COMPLETELY shocked at this totally unexpected and impossible to plan for eventuality.

Who could possibly have known that hard drives might fail after decades?

Yeah. You can’t offer a half-secure and half-private platform and expect your average person to be able to figure out which half is which, which leads to crazy misconceptions, misunderstandings, and ultimately just a bunch of wrong and misleading information being passed around.

I’d argue, though, that Telegram probably did this on purpose, and profited GREATLY from being obtuse and misleading.

At the moment, essentially.

The way Google got carrier buy-in for yet another messaging platform was to basically run it for them at no charge.

The carriers COULD run their own RCS infra, but if you’re getting the milk for free, why buy the cow?

Meh, you never could trust them.

Group chats were NEVER encrypted, so I’m surprised that people are just now figuring out that if it’s not encrypted = people can read it.

If it wasn’t a 1:1 “secret chat” encrypted message, then congrats, you weren’t as opsec-y as you thought you were.

The discussion around special offers and pricing are actually why I don’t subscribe to a lot of things.

It always feels like there’s likely going to be a better deal if I just go away and wait and don’t bother right now, which typically means I forget I was even interested.

I’d rather places be honest with pricing than play those variable price games because it always feels like I’m going to get scammed if I don’t just do nothing and see if the price gets better.

Good luck, I guess?

Seems like it’s not worth the tens or hundreds of thousands you’re going to spend fighting in US Federal court over the next 5 years, but also not my money.

I’m using 12.3 on Windows, and the version I grabbed didn’t require me to do anything other than mount the iso, and run the installer.

YMMV, no clue about OS X support, no clue about version 13.

Their metadata DB is still poorly and broken, and uh, it kinda makes the whole app pointless.

You probably want LazyLibrarian until and unless (and it’s been literal years now) they fix their shit.

Yep, it’s fully supported in HA/ESP32 and is suuuuuper easy to deploy and configure and the HA devs even documented how: https://www.home-assistant.io/voice_control/thirteen-usd-voice-remote/

Unless there’s something wonky with your virsh configuration, no.

This is a shitty explanation and if anyone would like to explain it better feel free, but the bridge interface acts as sorta like a network switch that can forward packets as well as be used for an interface, if configured.

What that means is, essentially, your VMs will be attaching their ethernet devices to a “switch” that then routes the packets out to the local LAN as if it were, well, a nic plugged into a switch.

virsh shouldn’t assign an in-use MAC, as it generates a random one (and I have no idea what you’d have to do to make them not do that) so everything should… just work.

No, because the bridge interface becomes the primary interface as far as Linux is concerned.

You’d just use dhcp to assign an IP to br0 instead of the physical ethernet device, though for a server a static IP is probably a better choice (so that it doesn’t bounce around on your local network making it harder to access)

My nas isn’t running fedora and thus isn’t using whatever fedora uses for network definitions, but is netplan under ubuntu.

I mean, probably the same thing, but it was shockingly trivial to configure:

network:
  ethernets:
    enp0s31f6:
      dhcp4: no
      dhcp6: no
  version: 2
  bridges:
    br0:
      interfaces: [enp0s31f6]
      addresses: [x.x.x.x/24]
      gateway4: x.x.x.x
      nameservers:
        addresses: [x.x.x.x, 8.8.8.8]
      parameters:
        stp: true
        forward-delay: 0
      dhcp4: no
      dhcp6: no

Disabled addresses on the physical interface, added the bridge section and told it which interface(s) to bridge - in this case it’d be the real interface and whatever gets added later by qemu/kvm, and then defined the IP address info.

the virsh network xml file was also straightforward, just make a xml file similar to:

<network>
  <name>host-bridge</name>
  <forward mode='bridge'/>
  <bridge name='br0'/>
</network>

and then it’s just

virsh net-define your.xml.file.here
virsh net-start the-name-you-used-in-the-xml
virsh net-autostart the-name-you-used-in-the-xml
virsh net-list --all

Should show up in the net list, and be selectable by name when making a VM

That’s a configuration problem you’ve made somewhere: you shouldn’t be assigning an IP to the bridge and it’s constituent interfaces.

You should take a look at your network config, and run (I’m assuming) dhcp only for br0.

Once you define the bridge network in virsh, and use that to make your VMs, kvm/qemu will assign unique MAC addresses to the VMs, so all you really need to sort out is getting your host OS to only assign an IP for the bridge.

Edit: also checked and yeah, eno2 and br0 and virbr0 are all different MAC addresses; did you maybe pick an option that forces them to inherit a MAC or something?

Yeah you don’t say.

They’re at like a minimum of $80 a fight at this point.

Of course people are going to pirate that shit, because that’s far far too expensive.

It’s more about the quality of the content: you posted more than a couple hundred characters and thus were able to clearly outline what you wanted, why, and how you thought that would improve things.

Mastodon has the twitter problem where it’s short-form hot-takes and basically no good long-form content, other than like, to link to somewhere else for the good content.

I don’t have a lot of use for that kind of content especially in a format where it’s hard to respond to and have an actual conversation. Most twitter-clone UIs don’t do a good job of threading and nesting comments in a way that you can easily follow along and have conversations with the people engaged in discussion.

I’m old and like the forum-style interface where people can write out a complete thought, engage in a formatted discussion that’s easy to follow along with, and does so in a way that lets other people easily hop in at any point.

So I’d say it’s less about the idea of unifying platforms on a single identity (which I think is a great idea and firmly agree that having some sort of Fediverse SSO would make this a lot easier of a sell for less technical users) but more that dumping a pile of low-quality content into a place with reasonably good content isn’t actually improving anything.

(I would also qualify this with a comment that I’m old enough that my first “fediverse service” was FidoNet, so I’m reasonably sure I have a different opinion on the value of a well-designed platform for a single specific task vs making one that can do everything for everyone.)

As long as it’s something you can turn off and remove, that seems like a weird ‘I want everything in one place’ thing but not utterly destructive of the Lemmy experience.

It sounded more like stuffing a firehose into your Lemmy UI, at which point all you’ve really done is just make Lemmy a mastodon client, and I’ve already got several better options for that anyway.

If you want to follow Mastodon hashtags, you should just use Mastodon. It has the UX to support this, and all you’d end up by shoving this into lemmy is a lot of noise in a UI that’s designed for replies to a single thread and not just hundreds and hundreds of threads.