First off all, the components are selected for the Linux compatibility, so it’s guaranteed to work. But they also provide some tools to make sure you use the preferred drivers, a control center tool for customising fan speeds, etc. All of which are open source. They even provide the windows drivers for all configs for when you want to dusk boot (and those are even fairly up to date).
Bought my last few laptops from Tuxedo. Their 13" infinibook can be quite noisy, but I’m having a blast with the Polaris I bought last year.
In the end it’s all just a linguistics game though - you’re profiting off the work somebody did, without paying the rate they charge for it.
But that’s exactly the kind of answer you’ll get in a community focused on piracy. Most people wouldn’t be here if they hadn’t already justified piracy.
Very nuanced take, I like it.
Wait, is “advocating death for” the evolution of “right to exist”? That sure escalated quickly.
They don’t need everyone to comply, just the vast majority.
If you’re in Europe, I can recommend Tuxedo Computers. They specialise in making Linux based computers, and are highly configurable.
Oh wow, it hadn’t even occurred to me such a subscription wouldn’t include the ability to watch on demand. That’s so last century.
That sounds like a contradiction.
Edit: For everyone else who doesn’t bother to read the rest of the thread: it hadn’t occurred to me that buying HBO doesn’t include video on demand. But now I do. You don’t have to tell me. I know now. What I’m saying is you don’t need to tell me. Because I already know. So there’s no need to tell me, for I already know.
If anything, wouldn’t that make vote abuse even easier? Just send 100 upvotes with 100 random hashes.
This completely goes against the entire philosophy of the Fediverse
Care to elaborate on that? As far as I know this is built in to all the ActivityPub applications.
Also, there’s way too much trust in instances.
I say there’s too much care about votes. Because someone can just give themselves infinite votes from their private instance, it makes it all the more worthless.
Instances should have their own settings on what instances are allowed to keep a local copy.
There’s a setting for that, it’s called the allowed list - configures who are allowed to federate with you. Beyond that - if it’s out, it’s out.
For transparency, this is what a Like payload looks like. The first part is just context for the activitiypub protocol and is pretty much the same for each message. The second part contains the actual data of the message, and the most personal detail in it is the url of your own profile, and the url of the post/comment you like:
{
"@context": ["https://www.w3.org/ns/activitystreams", "https://w3id.org/security/v1",
{
"lemmy": "https://join-lemmy.org/ns#",
"litepub": "http://litepub.social/ns#",
"pt": "https://joinpeertube.org/ns#",
"sc": "http://schema.org/",
"ChatMessage": "litepub:ChatMessage",
"commentsEnabled": "pt:commentsEnabled",
"sensitive": "as:sensitive",
"matrixUserId": "lemmy:matrixUserId",
"postingRestrictedToMods": "lemmy:postingRestrictedToMods",
"removeData": "lemmy:removeData",
"stickied": "lemmy:stickied",
"moderators":
{
"@type": "@id",
"@id": "lemmy:moderators"
},
"expires": "as:endTime",
"distinguished": "lemmy:distinguished",
"language": "sc:inLanguage",
"identifier": "sc:identifier"
}],
"actor": "--URL OF THE USER PROFILE--",
"object": "--URL OF THE POST OR COMMENT--",
"type": "Like",
"id": "-- URL TO THE INSTANCE THAT PASSED THE MESSAGE--",
"audience": "-- URL TO THE COMMUNITY THE POST IS PART OF--"
}
I don’t think email is a good example because you’re in complete control of who you send an email to.
You can easily check which instances your server is federated with in the footer of your server. If any of those external servers have subscriptions to the community you’re posting in, they will receive an update, so it’s safe to assume it’s being sent to all of them.
Generally speaking, lemmy is much more cpu bound than it is bound by bandwidth - so the added bytes don’t matter that much. The example above was just for 1 community. Now imagine the user is subscribed to a dozen communities, but doesn’t even browse lemmy that day. That’s probably thousands of api calls made to keep his server on sync, and 0 requests saved.
Like the big instances have literally hundreds of thousands of workers running in order to get all the updates out. If one of those calls fails, it gets put back into the queue for retry.
OP asked if having his server added to the lemmiverse would alleviate the load “Like with torrent”. That is demonstrably not the case - it only adds more workload on the other servers, with a break even point that’s highly variable. Yes, your server will be nice and snappy, but the origin servers have to pay the price - death by a thousand papercuts synchronisation calls.
So you need just 15 more users on your instance to break even, if you have 17 in total, you’ve saved 10 calls.
In this particular example, yes. But only if those 15 people subscribe to the exact same communities. If they don’t, the calculation gets even more complicated.
I’m not sure why exactly you’re opposed to federation when that’s one of the biggest points of fediverse.
Some people seem to be under the impression that setting up their own personal server is relieving the pressure on the network. What I trying to get across is that’s not the case, unless it’s being used by a reasonable amount of people.
I can’t tell you what the sweet spot is - but my guess would be that it’s only going to be at least several dozen, more if their interests (subscriptions) don’t overlap very well.
Super useful info! Thank you for your research.
Regardless of what tool OP ends up using, this is the most straightforward way.