They’re deporting themselves now too? That’s efficient.

Yep. Also, I did clarify that I would usually do an overall upgrade at the same time.

I get the message there’s an upgrade. Say I’ll do it myself, go to console.

yay -S discord (or more likely just do an overall upgrade and reboot, what they hell)

Restart discord.

It is if you leave the keys in the ignition.

They send fake (non-existing) actor ids for votes to obfuscate the identity of the real user. It is “compliant”, but completely against the spirit of a public social network.

There have been discussions about how to implement this before. But it has to be done in a way that is agreed by other threadiverse software. Unless they actually provide profiles for these fake actors there will be problems since some software will look up the profile info to cache it, even for likes…

Personally I’m of the opinion of a standard header to mark a favourite message as a private one and use a random ID that the originating instance can use to validate the message as genuine. But, this needs to be adopted properly by all.

But this is the crucial thing. It wasn’t in the repository. It was in the tarball. It’s a very careful distinction because, people generally reviewed the repository and made the assumption that what’s there, is all that matters.

The changes to the make process only being present in the tarball was actually quite an ingenius move. Because they knew that the process many distro maintainers use is to pull the tarball and work from that (likely with some automated scripting to make the package for their distro).

This particular path will probably be harder to reproduce in the future. Larger projects I would expect have some verification process in place to ensure they match (and the backup of people independently doing the same).

But it’s not to say there won’t in the future be some other method of attack the happens out of sight of the main repository and is missed by the existing processes.

I bought my first HDD second hand. It was advertised as 40MB. But it was 120MB. How happy was young me?

Yeah, but asking film/tv producers for permission would kill my content collection!

And just to show I’m serious, you have zero seconds to comply.

Actually how is your ISP giving out IPs to you? Mine uses IPv6 PD to give me a /48. And I then use SLAAC locally on the first /64 prefix on my LAN. Plus another /64 for VPN connections.

If you mean receiving RA/ND packets from your ISP (which are used to announce IPv6 prefixes) then you need to allow icmpv6 packets (if you don’t want to be able to be pinged, just block echo requests, ICMP in v4 and v6 carry important messages otherwise).

If your ISP uses DHCPv6 Prefix delegation you will need to allow packets to UDP port 546 and run a DHCPv6 client capable of handling PD messages.

If you have a fixed prefix, then you probably don’t need to use your ISPs SLAAC at all. You could just put your router on a fixed IP as <yourprefix>::1 and then have your router create RA/ND packets (radvd package in linux, not sure what it would be on pfsense) and assign IPs within your network that way.

If you have a dynamic prefix… It’s a problem I guess. But probably someone has done it and a google search will turn up how they handled it.

EDIT: Just clarified that the RA/ND packets advertise prefixes, not assign addresses.

I believe the privacy concerns are made moot if all consumer level routers by default blocked incoming untracked connections and you need to poke holes in the firewall for the ports you need.

Having said that, even knowing the prefix it’s a huge address space to port scan through. So it’s pretty secure too with privacy extensions enabled.

But for sure the onus is on the router makers for now.

I used HE for ages until my isp gave native ipv6. I also used sixxs back then too. Both provided good connectivity for the few sites that were around using it at the time.

This is my biggest bugbear about a lot of UK isps. They are dynamically allocating ipv6 prefixes for absolutely no good reason.

I’ve only ever done ipv6 using Linux directly as a firewall or a mikrotik router. So cannot help with pfsense I’m afraid.

You start by adding ipv6 and serving both. One side needs to move first. Content providers or isps.

The big tech companies are using ipv6. In the UK the isps are mostly offering it too.

Host both and help us move towards dropping Ipv4 some day. It’s not going to happen in a day.

“Fresher”

Don’t be so sure. Piers Morgan will do whatever he thinks makes “good television” and especially good sound-bites that can have his ugly mug displayed ad-nauseam.

He saw a weakness and exploited it. I doubt he’s “chosen a side” at all.

Death panels are fine, provided the reason is pure profit. Apparently.

The big websites are operating on ipv6. If you want to run your own website it’s actually trivial to host it on both ipv4/ipv6 now and most good hosting providers will give you a /64 allocation.

In the UK broadband providers also are quite commonly providing IPv6 as standard (albeit the scummy ones dynamically assign a prefix, for absolutely zero reason aside from annoyance). My provider uses PD to assign a /48 even.

So, really not sure why it’s so slow going elsewhere. There’s really no reason for it now in 2025.

Can you imagine that much RA/ND chatter? Would need some serious capacity.

I think his unrealistic 24 hour plan was to give putin what he thought he wanted. Eg all the territory he’s captured so far and assurances against nato action/withdrawal of some western personnel at nato border country bases. You know putin’s public story.

He just didn’t know putin’s real objective. Maybe now he’s getting a bit of an idea. He’s too simplistic to fathom that there could have been an ulterior motive.