This is something I do on my new (Samsung) phones for the last 2 phones and this latest one I also turned off fast charging. On previous phones it was capped at 85%, current ones seem to have several options with the highest "saving" being to charge to 80%
If I'm going out for the day and need the full charge I turn it off for the duration and if I need a fast charge I turn that back on.
By and large though most of the time I keep it off. Seems to make the batteries last a bit longer. Too early to tell on the current phone though. Only a year old. I generally keep phones for around 4 years.
I used to do the opposite on the old nicad batteries phones had in the 90s. I'd carry a spare fully charged one, run the main one down to zero, swap them and then charge it to full. This made a huuuuge difference though.
We can see it ourselves. We use rabbitmq for incoming (and maybe outgoing, it's been a while since I looked at how it is) federation. So, you can see the queues there. For incoming (from rabbitmq) and outgoing there are also queues (symfony messenger) and these handle failures and can be configured and can be queried.
After the upgrade I just took the default configuration again (because it seems queue names changed). But I used to have various rules setup in rabbitmq for retries and it took a fair few tries before the messages ended up in the proper "failed" queue (which needs manual action to retry). Some items you eventually need to clear (instances that just shutdown, or instances that lost their domain for example). They will never complete.
But it's not exposed in any way to my knowledge. Well unless people have their rabbitmq web interface open and without login of course.
I think it must be hit/miss. Because I think those edits I made would have gone from my instance to world and then from world to .ee, and it was happening within seconds.
So, presumably random stuff is being dropped or delayed?
Wait, how do they get that data remotely? I was looking at my instance vs world and I saw there's like the +1 hour from a week or so ago when I upgraded to latest mbin lol.
I guess they're looking at common activities and when they appear on each?
Looking at incoming request. .world is working OK for me. They seem to be batching stuff like I'll get nothing for 30 seconds, then over 3 seconds like 50+ requests.
Of course I don't know if their queue is backed up and I'm getting delayed stuff. I'd need to stop processing and look into the incoming queue to see what they're sending.
Bit of an edit. Looking at incoming again I can see under newest items, an entry from world that was 11 minutes old. Oh I have an idea. I'll see if this edit gets there in a timely manner.
Spoiler alert, it was instant.
Oh ignore me. It's specifically between those two instances I guess.
Well for a gamer no real comment. But there is one metric Intel still trashes AMD in for the APU. Hardware video acceleration/encoding. The quality is objectively better on Intel Quicksync.
When getting a home box that also needed to do transcoding, Intel CPU was a requirement. My desktop development/gaming system? Ryzen + NVidia.
Well, apparently the first round has been annulled entirely. Which I am sure will be pretty spicy over there. Did I mention I'm going to .ro next week? Should be fun.
It's not how ActivityPub (at least Lemmy/*bin servers) works. There isn't so far as I've ever seen an API that allows for this within ActivityPub (now specific to Lemmy/*bin implementations there's the API the browser/apps use that must provide this, but that's not ActivityPub). It actually looks to be cleverly designed to prevent it. It might look like backfilling is happening because old stuff appears, but there are reasons for this.
How it works from my experience (I did some work on the federation in kbin a year or so ago).
Instance A subscribes to community B hosted on Instance C.
Instance C notes this and does nothing. No previous content is sent, only future activities will be.
User on Instance D already subscribed to community B upvotes a comment on a post in community B.
Instance D sends the activity to Instance C.
Instance C sends the activity to Instance A.
Instance A gets the notice of the upvote, but realises it has no context for the upvote. But luckily the upvote has the comment ID of the comment that it was related to. So, now Instance A makes a request for the comment from Instance C.
Instance A receives the response from Instance C. But it turns out that comment was in reply to another comment. But the comment contains the ID of the parent comment. So Instance A requests that comment (and any parent comments until it gets the parent post).
By now Instance A has the information about the like, all comments from the liked comment to the post. These are saved to the database and will appear on the local system.
For each of the likes, comments and posts. If the user isn't known locally the profile will also be fetched from their instance and stored locally.
And so old posts and comments will begin to appear as activities linked to them happen. But there isn't a method to ask for "all the posts in community X" using activity pub. I remember because I was specifically looking for this a year or so ago. It let's you see the parent object but not any children.
Maybe Mastadon etc does it different? No idea.
And all of this is moot because if I block a User Agent, or I block an AS number/IP block. They're not getting anything either by ActivityPub or scraping unless they change User Agent, AS number, or both.
I don't think they're optimising much at all. I think it's likely just a modified web crawler but without the kind of throttling normal search engine crawlers use. They're following links recursively. Then probably some basic parsing or even parsing with AI to prepare the data to make another AI model.
But, they aren't. They're not after Activitypub specifically. They're scraping the whole internet, most of them using clear bot User Agents. So, I routinely block their bots because the AI ones are usually hitting you multiple times a second non-stop. If they started making fake Activitypub nodes they would not be scraping as a bot, and they would want specifically fediverse data. Important to note here though, an Activitypub node doesn't "collect" data, they subscribe (to mastadon users/hashtags or communities) and then get new data delivered to them. So they wouldn't get the old stuff.
Having said that, I've seen some obvious bots using genuine browser user agents on IP addresses from certain very large Chinese companies. For those I just blocked their whole AS number.
I mean personally I did block all the AI scrapers I could find on my instance, around a month or so ago. There were a lot, mostly unscrupulous, some big names included. Probably should look at the logs to see what's new.
The amount of traffic was quite significant too. I have a theory that they expect legislation soon, so are not playing nice and slow like crawlers do, but are vacuuming as fast as they can.
But you're right. Everyone would need to do it, to make a difference.
I'd seen colaweizen plenty of times when I was in Germany years ago. But then this guy walked up to the bar and asked for a Fantaweizen. That was new for me.
r00ty @ r00ty @kbin.life Posts 2Comments 1,265Joined 2 yr. ago
Wayland on nvidia for me only has annoying glitches. Nothing serious.
Sure if I were getting a new card I'd consider amd. But the issues have only been a minor annoyance.