“way before the toilet paper shortage even starts.” LMAO.

John Wayne toilet paper. Rough, tough, and doesn’t take shit off of anyone.

You saying they might have an unexpected dangling pointer?

https://en.m.wikipedia.org/wiki/Long-term_nuclear_waste_warning_messages

For reference.

Ok now we know why their alignment team quit.

X gon’ give it to ya Fuck waiting for you to get it on your own X gon’ deliver to ya Knock knock, open up the door, it’s real Wit the non-stop, pop pop of stainless steel

Sounds like you’re well on your way with a good process. The book Software Architecture: The Hard Parts is a pretty decent guide to breaking apart a monolith. It’s not a 100% follow it to the letter guide IMO, but I think the overall approach makes sense. At each step you have to consider trade-offs instead of following any kind of dogma.

I think we’re in violent agreement. The problem is you need someone in licensing/legal to take a risk at this point to even use AGPL on a corp machine. Figure out the law and the license, then make judgement calls on some slightly fuzzy parts. They’re just not going to do it. Maybe in a few years if someone tests “the right” model, whatever that is in court and prevails. Meaning the dev gets paid and the user retains intellectual property that is either tangential to the product or provides enough value to be it’s own product that’s still sellable in the same way as before the suit.

Unless it’s open source and you have any contributions without a rug pull contributor agreement. Also you don’t have any AGPL dependencies.

We had that relicense convo with the desktop tool maker and they were hogtied by both. Corporate policy dudes had to be harassed into even looking into it. Then maybe 3 months of back and forth championed by motivated tool users later they said to hell with it and banned it.

So if you plan for the AGPL rug pull for your contributors or you have no contributors and none of your dependencies are AGPL in a viral way, go ahead.

They might hope to make money at any point in the future. AGPL is too viral to integrate with. Working at a large corporation they’ve banned a standalone desktop tool we could have used because it was AGPL. We wanted to pay for it, but we couldn’t. It’s a dead end product for corporate users. So personal use , hobbyists, and those companies that think the AGPL won’t infect their IP or don’t care. You limit your TAM severely if you use AGPL.

So if you aren’t in it to ever make money in the future, go for it.

Yeah, if I’m reading that right they’re complaining that they’re stuck at phase one of enshitification - lose money on aquiring users. The reason behind that is they’re not able to monopolize the market for their games. “These damn mobile stores won’t let us turn the corner and put the clamps on our users. Fix it please.”

There are far fewer hurricanes. You also get a couple days warning on most weather events. I take your point though, between waking up to seeing a related push message and seeing this meme I had forgotten about it.

At least it appears nobody died, only 5 injured.

Beer warmer!? Yeah the bad thing is you’re about to ruin a beer.