![](/static/253f0d9b/assets/icons/icon-96x96.png)
![](https://beehaw.org/pictrs/image/1be75b15-2f18-429d-acf7-dcea8e512a4b.png)
I’ve played open source games that assign ownership of the code to one person, but they operate like an open source project and anyone can use the source however they wish. It depends on how that owner chooses to license the code.
This is a secondary account. My main account is listed below. The main will have a list of all the accounts that I use.
Personal website:
I’ve played open source games that assign ownership of the code to one person, but they operate like an open source project and anyone can use the source however they wish. It depends on how that owner chooses to license the code.
You’re missing the most important element. Disgustingly large pile of money that you can use to drag out a suit until the other end folds.
Eternal copyright damages. This sounds like a safe and reasonable decision by our ever respectable Supreme Court.
Price to published write endurance might get you started, but I’m curious what answers you get because this is a difficult question IMHO. Actual reliability depends heavily on firmware which is a vendor-specific secret sauce.
Huge amounts of daily maintenance because I lack self control and keep changing things that were previously working.
At the moment your service becomes even marginally more difficult than piracy, yo ho yo ho. What am I paying you for?
What’s the catch? Is there a catch?
I’d like to gently un-recommend Shark. I’ve had two warranty replacements in 6 months. They stand behind the product, but it would have been nicer if it worked consistently.
Where did you buy them from? There’s been an uptick in counterfeit storage and flash chips getting into new products.
I’m somewhat confused what you’re asking here. The two technologies that you mentioned do not provide the ability to share a PCIe device to my knowledge which is what I understand you wish to do. The first allows network cards to directly access host memory and perform data transfers without consulting the CPU while the other allows for the sharing of a PCIe root or bus, not allowing multiple systems to access the same hardware device at the same time.
I’ve heard of proprietary solutions, which makes sense because if you want to virtualize multiple instances of one physical hardware device I don’t see how you can do that efficiently without really intimate knowledge of device internals. You have to have separate state for these things, and I think that would be really challenging to do for an open source project.
Anyway, just thought I would open up the discussion because I didn’t see any other comments. I hope to learn something.
In theory, sharing a digital file can have a much greater impact than sharing a CD physically. Plus, you lose access to your copy of the CD if you give it to someone else. You can think of it like transferring a license for one user to a different user. There is no simultaneous usage.
I don’t personally agree with this view, but I believe that’s the argument.
Safest possible way? Separate machine on a different network, like guest Wi-Fi.
Realistically? I use containers blocking Internet and most file access and only use sources I trust not Internet rando releases.
I’m willing to pay for one, maybe two subscriptions, and ain’t nobody got time to dig for which service has what show to find out season 2 is on some other service entirely.
Piracy provides a better user experience 🤷♂️
It was a solution to a Lutris bug. Basically, flatpak containers can use these things called portals to gain access to specific files and directories via a file chooser rather than broad access or manually assigned access.
In this case, my wine installation was crashing because some part of it was trying to obtain a lock on a directory object, which is an unsupported feature when accessing a directory through a portal. The error message is something completely unrelated like can’t draw window with a string of hex values. It took me a few hours to track down the real root cause.
Oh well. Works on my machine. Also, there’s a fix on the development branch now. I made a write-up, posted it, and it’s all gone. I should have known better honestly. It works great for some people but anybody can arbitrarily receive unfair treatment with no recourse at any time. I’m satisfied knowing that eventually the fix will get out to everybody eventually. It’s just a shame I couldn’t leave a signpost behind.
Man that place. I know it’s cliche to talk about it like talking about your ex on a date, but I posted there for good reason.
I found the solution to a rare bug that was bothering a group of people. I posted the solution, and my account was immediately banned sitewide for violating the terms of service, whatever that means.
I thought to myself: yeah… it was a mistake coming here. Leave it to the bots to have conversations with themselves.
Another perspective is data hoarding.
I have system images of machines of relatives who have died. Many of the photos that I have retained are the only ones. However, that was more an emergent utility than a motivating one.
Monthly, alternating locations.
You got me there! Not fireproof. In that case I’m just hoping that having two off-site backups at different locations has me covered, but that’s a good idea. I should consider fireproof foil.
I still have drawings I made in MS Paint on Windows 95 when it had just come out, my first text document, and the first report I ever typed in grade school.
Btrfs snapshots of the root volume in RAID1 configuration with 8 hourly, 7 daily, 3 weekly, and automated rsync backups to NAS, with primary and secondary offsite, physically disconnected backups stored in sealed, airtight, and waterproof containers at two different banks prepaid storage and with advanced directive in the event of my demise.
Bit of a hobby really. I acknowledge it’s completely unnecessary. I don’t like to lose data.
deleted by creator