I look forward to tronicsfix tearing one down and seeing just how “refurbished” they really are. I expect great things from Valve but I still remain skeptical
It depends on the source. Lemmy uses “pict-rs” as the built in image hosting mechanism, this includes a way to fetch small thumbnails. But other hosts, like catbox.moe or Imgur or anywhere else might not be being fetched efficiently.
Additionally, pict-rs uses imagemagik to transform the image on request. If that transformation doesn’t already exist (cached), or the host is over-loaded or under-spec’d, then you might see a delay in the request response
Your best bet is to use your developer tools to check network usage and response times if you are interested
I’m in my mid 30’s and I spent A LONG time working out, getting as fit as I could.
I still hated my body when I looked in the mirror, and I hated every second of the workout. “Post workout” I was so proud, but like, that’s equivalent to drinking so you could appreciate being sober.
I stopped a while ago and started just trying to eat healthy and focus on other sources of happiness. I’m much happier since!
I’m in my mid 30’s and I spent A LONG time working out, getting as fit as I could.
I still hated my body when I looked in the mirror, and I hated every second of the workout. “Post workout” I was so proud, but like, that’s equivalent to drinking so you could appreciate being sober.
I stopped a while ago and started just trying to eat healthy and focus on other sources of happiness. I’m much happier since!
Due to how federation works, the federated instance needs to accept and process the activity. Each application can define its own "optional" activity properties, but the activitypub specs define mandatory properties and some optional properties for coherence across the fediverse.
The way lemmy implements this is to use the activitypub-federation-rust library that the lemmy devs built. Through this, activities in Lemmy are sent using HTTP and have a failure retry:
It is possible that delivery fails because the target instance is temporarily unreachable. In this case the task is scheduled for retry after a certain waiting time. For each task delivery is retried up to 3 times after the initial attempt. The retry intervals are as follows:
one minute, in case of service restart one hour, in case of instance maintenance 2.5 days, in case of major incident with rebuild from backup
In the case of votes, the activity is a "like" - some other federated applications understand this and will accept it, but others won't. For example, peertube does not have a like activity, and I don't believe they would handle it.
However votes are shared across instances. When a user "likes" something from another instance, Lemmy will notify that actor (the page) that the activity (a like) was emitted by another actor (you).
Hope that clarifies things. I'm still learning all this myself so if anyone can contribute or improve my answer, please do!
Doesn’t really make sense, if they’re federated then you wouldn’t need to pay them to access their content. If they’re not federated then what are you paying for?
I completely agree, but I don’t agree that RHEL can’t pivot to this new model. And their first mover advantage as the “enterprise operating system” won’t go away.
I guess your point is that their mismanagement of this situation is evidence of their eventual downfall, but I just don’t know if I buy that
I think their position in the market allows them to make these types of bad decisions without much fallout. If anything this just buys them more time
You mean like my friend fiction? Like the story where the whole basketball team becomes zombies and then they all fight over dating me?
Butts butts, I love butts.