• 0 Posts
  • 34 Comments
Joined 1 year ago
cake
Cake day: June 13th, 2023

help-circle
  • I’ve used 4k and 1440p monitors, and my TV is 4k as well. For desktop use, 4k isn’t really a big difference because of the hardware needed to run it at a decent speed. However, once I got my hands on a 170hz 1440p monitor, I can’t go back to anything less. It’s extreme noticeable. The higher refresh rate, and the reasonable upgrade in pixel density makes text much clearer, especially in motion.

    For content viewing though, 4k on a TV it depends on how much of your field of view is occupied by the TV. Most of time though, a high quality panel is worth much more than higher pixel density. There is a massive difference between a basic 4k big box store TV, and 4k LG oled. The color, even outside of HDR content is just so much better, and the true actual black color is fantastic. Resolution is nice, but honestly, oled color is so good.




  • Don’t worry I’ve been quoted EEE enough times. I really don’t think that is the direction this will go down. If Meta actually embraces it, then the whole of the fediverse grows over all. Then, if Meta does extend the ActivityPib protocol in a way the that becomes incompatible with the rest of the ecosystem, we just let them go and do their own thing. ActivityPub already has a userbase, if they join us, and then later on cause problems then everything just goes back to how it is right now. The final E can’t realistically happen because the existing ecosystem will just carry on exactly as it is now. If people on Threads want to communicate with us, then they need to speak the same protocol. If they don’t, then they don’t get to participate.

    Do you genuinely believe that the whole community of the fediverse would just lie down and accept breaking changes to the protocol without resistance? There are too many talented and passionate people invested in this ecosystem, the absolute worst case scenario is the protocol itself gets forked, and again the exist communities just carry on. There is no extinguish time line. Everyone points to how Meta handled XMPP, please compare the user bases of ActivityPub vs XMPP. The world has changed a lot since then. Another example I’d like to point out is Hashicorp’s Terraform. They explicitly tried to EEE, and the moment they attempted the final E, it was instantly forked, and the open licensed fork was adopted into the Linux Foundation and the ecosystem carried on.

    Take that what you will, but I am reasonably convinced ActivityPub has enough support and community that any EEE attempt will inevitably fail. The front ends will change, the hosters will come and go, the open standard is here to stay.



  • 100% agree. Universal Basic Income feels inevitable as a solution. Better and better technology puts machines in place of human labor, with no guarantee that other jobs will come into existence to replace the ones lost. Is it not the ideal goal to have machines do all labor, leaving humans to do what they actually want without fear of homelessness and starvation.

    It just kinda sucks right now because these systems don’t exist to support this changing landscape.



  • Improvements in technology do not guarantee employment for tradespeople of current technology. A whole lot of horses became unemployed when cars became ubiquitous. I’d say the improvement of cars to society is worth the loss of employment to all those who maintained the horse’s infrastructure. Like all those manufacturing jobs lost from the improvement in machines, professional creatives must adapt to the times, or seek other forms of work. No different than any other job in all of history.


  • By writing text on their platform, you consented to their free and unlimited use of your text. Terms of Service and EULA on practically all platforms has this boilerplate legal agreement. You DID consent. Facebook has access to a massive amount of text, same with Google. They don’t need to bother stealing when so much is already in their databases.

    Now if you never wrote any text published on any platform with that agreement, sure you could have an argument there.



  • I despise that the artwork generators are all based on theft.

    Ownership of anything is difficult to define. The internet has accelerated this loosening of definition. If I pay a subscription to use my coffee pot, do I really own it? If I take a picture of the coffee pot, do I own the picture? If I pay a photographer to take a picture of the pot do I own the picture, do I own their time?

    I don’t intend on trying changing your opinion on theft, but its interesting to think about how ownership feels very different as time goes by.





  • You missed the point of my example entirely. How can those commits exist, and those people exist in that instance if they don’t have accounts? I was refuting your statement that a frontend needs an account. By mirroring an existing repo, as an example, you could verify that my claim is correct. Git as platform is already decentralized and doesn’t require accounts. You could email someone your git diff’s and it will function the same.


  • You need a frontend

    Yes, but the requirement of said frontend are very small.

    and a frontend needs an account.

    Not required at all actually. For example, mirror a github repo in gitea. You’ll see all the commits, their messages, and who made them. Yet that gitea instance isn’t accessible publicly. None of those people have an account, and none of them can login even if they could access the instance. A commit is just attached to a name, that is user configurable, and a lot less data minable than a “real” account.


  • I agree with you, I’m totally fine federating with them. If they choose to become incompatible with me, THEIR users will lose access to the content on the rest of the fediverse. They have an obligation to get ad revenue. If they can have someone else host the content, then use their interface to put ads and collect data on their users, it sounds like a win, as those users can still interact with me. If they really wanted to EEE and create incompatibilities, the rest of the ActivityPub instances just carry on as normal without supporting those extensions. The ecosystem already exists without the integration, so it’ll just go back to being separate again, exactly as it is now.