> I run it in a Work profile on my GrapheneOS phone that I can switch off at any time
So this kind of works in stock Android, too. You have to reboot after switching back to the main profile, then the second profile won’t get loaded at all.
(I bet that this stops working in the future. It feels like the second profile doesn’t get loaded as a means to save CPU power. Once those smartphones get even more powerful, there’s no need to do that anymore …)
> I run it in a Work profile on my GrapheneOS phone that I can switch off at any time
So this kind of works in stock Android, too. You have to reboot after switching back to the main profile, then the second profile won’t get loaded at all.
(I bet that this stops working in the future. It feels like the second profile doesn’t get loaded as a means to save CPU power. Once those smartphones get even more powerful, there’s no need to do that anymore …)
> I run it in a Work profile on my GrapheneOS phone that I can switch off at any time
So this kind of works in stock Android, too. You have to reboot after switching back to the main profile, then the second profile won’t get loaded at all.
(I bet that this stops working in the future. It feels like the second profile doesn’t get loaded as a means to save CPU power. Once those smartphones get even more powerful, there’s no need to do that anymore …)
> I run it in a Work profile on my GrapheneOS phone that I can switch off at any time
So this kind of works in stock Android, too. You have to reboot after switching back to the main profile, then the second profile won’t get loaded at all.
(I bet that this stops working in the future. It feels like the second profile doesn’t get loaded as a means to save CPU power. Once those smartphones get even more powerful, there’s no need to do that anymore …)
🤣
🤣
/https://duque-terron.cat/media/photos/photo_21818-08-2024_10-00-52.jpg) #catsoftwtxt
#catsoftwtxt
#catsoftwtxt
felt great today! temp was down to 78F and 80% RH, but there was an ever so slight breeze so it did not feel sticky. carbo loaded the day before so maybe that had something to do with it too, but i really have not been tracking my nutrition at all. kept it easy the first five or so miles and then bumped it up ever so slightly for the remainder. probably could have gone an even two hours but running on new shoes (hoka mach 6) and really have not broken them in yet. lots of hot spots and a lot of troubleshooting on the go.
#running
felt great today! temp was down to 78F and 80% RH, but there was an ever so slight breeze so it did not feel sticky. carbo loaded the day before so maybe that had something to do with it too, but i really have not been tracking my nutrition at all. kept it easy the first five or so miles and then bumped it up ever so slightly for the remainder. probably could have gone an even two hours but running on new shoes (hoka mach 6) and really have not broken them in yet. lots of hot spots and a lot of troubleshooting on the go.
#running
felt great today! temp was down to 78F and 80% RH, but there was an ever so slight breeze so it did not feel sticky. carbo loaded the day before so maybe that had something to do with it too, but i really have not been tracking my nutrition at all. kept it easy the first five or so miles and then bumped it up ever so slightly for the remainder. probably could have gone an even two hours but running on new shoes (hoka mach 6) and really have not broken them in yet. lots of hot spots and a lot of troubleshooting on the go.
#running
Before:
https://movq.de/v/b7443c8873/a.jpg
After:
https://movq.de/v/b7443c8873/b.jpg
And the fix was using
-define jpeg:sampling-factor=2x1 when creating the thumbnails using ImageMagick.I’m not really sure, though, what’s going on. 🤔
More context: https://tilde.zone/@movq/112981572946464025
Before:
https://movq.de/v/b7443c8873/a.jpg
After:
https://movq.de/v/b7443c8873/b.jpg
And the fix was using
-define jpeg:sampling-factor=2x1 when creating the thumbnails using ImageMagick.I’m not really sure, though, what’s going on. 🤔
More context: https://tilde.zone/@movq/112981572946464025
Before:
https://movq.de/v/b7443c8873/a.jpg
After:
https://movq.de/v/b7443c8873/b.jpg
And the fix was using
-define jpeg:sampling-factor=2x1 when creating the thumbnails using ImageMagick.I’m not really sure, though, what’s going on. 🤔
More context: https://tilde.zone/@movq/112981572946464025
Before:
https://movq.de/v/b7443c8873/a.jpg
After:
https://movq.de/v/b7443c8873/b.jpg
And the fix was using
-define jpeg:sampling-factor=2x1 when creating the thumbnails using ImageMagick.I’m not really sure, though, what’s going on. 🤔
More context: https://tilde.zone/@movq/112981572946464025
(Regarding Musk: He bought Twitter, ruined it and people mass-migrated to Mastodon. So let’s let him buy Meta and do the same thing! 🤪)
(Regarding Musk: He bought Twitter, ruined it and people mass-migrated to Mastodon. So let’s let him buy Meta and do the same thing! 🤪)
(Regarding Musk: He bought Twitter, ruined it and people mass-migrated to Mastodon. So let’s let him buy Meta and do the same thing! 🤪)
(Regarding Musk: He bought Twitter, ruined it and people mass-migrated to Mastodon. So let’s let him buy Meta and do the same thing! 🤪)
My wifes mom nearly got her account fully taken over by some hacker. They were able to get control and change password but I was able to get it recovered before they could get the phone number reset. They sent messages to all her contacts to send cash.
My wifes mom nearly got her account fully taken over by some hacker. They were able to get control and change password but I was able to get it recovered before they could get the phone number reset. They sent messages to all her contacts to send cash.
Do you think yhere'd be any noticeable tangible benefits observed for self hosting? 🤔
Do you think yhere'd be any noticeable tangible benefits observed for self hosting? 🤔
HTTP/3 moves the binary protocol from HTTP/2 over to QUIC which is based on UDP instead of TCP. This makes it better suited to mobile or unstable networks where handling of transmission errors can be handled at a higher level.
HTTP/3 moves the binary protocol from HTTP/2 over to QUIC which is based on UDP instead of TCP. This makes it better suited to mobile or unstable networks where handling of transmission errors can be handled at a higher level.
#catsoftwtxt
#catsoftwtxt
/https://baldo.cat/media/photos/photo_21717-08-2024_20-21-44.jpg) #catsoftwtxt
/https://duque-terron.cat/media/photos/photo_21517-08-2024_15-39-07.jpg) #catsoftwtxt
#catsoftwtxt
#catsoftwtxt
#catsoftwtxt
/https://baldo.cat/media/photos/photo_21417-08-2024_15-39-03.jpg) #catsoftwtxt
#catsoftwtxt
I consequently make use of the UTF-8 encoding and state that in each end every one of the HTML files. This keeps me from surprises later on. The web server in the end is configured to automatically include the
Content-Type header with the right character encoding (super easy as it is always UTF-8) in the response, so this is very bullet-proof in my mind.My editor simply does not auto-"correct" anything. This almost never works in my experience. Especially when dealing with computer languages.
On the other hand, this is probably a reasonable argument: The vast majority of users have no idea what a DNS query even is (and they don’t care to begin with), so trying to hide something here is probably not worth the effort for Google/Apple. This would make filtering DNS requests more meaningful after all.
(But you can’t be sure and that is driving me nuts. I don’t want to deal with this in the first place.)
On the other hand, this is probably a reasonable argument: The vast majority of users have no idea what a DNS query even is (and they don’t care to begin with), so trying to hide something here is probably not worth the effort for Google/Apple. This would make filtering DNS requests more meaningful after all.
(But you can’t be sure and that is driving me nuts. I don’t want to deal with this in the first place.)
On the other hand, this is probably a reasonable argument: The vast majority of users have no idea what a DNS query even is (and they don’t care to begin with), so trying to hide something here is probably not worth the effort for Google/Apple. This would make filtering DNS requests more meaningful after all.
(But you can’t be sure and that is driving me nuts. I don’t want to deal with this in the first place.)
On the other hand, this is probably a reasonable argument: The vast majority of users have no idea what a DNS query even is (and they don’t care to begin with), so trying to hide something here is probably not worth the effort for Google/Apple. This would make filtering DNS requests more meaningful after all.
(But you can’t be sure and that is driving me nuts. I don’t want to deal with this in the first place.)
*.apple.com DNS requests look legit and valid, like itunes (_the App Store_) and push notifications. Need to investigate what some of the other ones are. There are _some_ Apple domains I already block as well that I've figured out over the years.
*.apple.com DNS requests look legit and valid, like itunes (_the App Store_) and push notifications. Need to investigate what some of the other ones are. There are _some_ Apple domains I already block as well that I've figured out over the years.
~
~
Obviously I can't guarantee that it's making its own DNS requests and sneaking through my filters, I could go and check at my router level, but I'm fairly confident it probably isn't.
Obviously I can't guarantee that it's not making its own DNS requests and sneaking through my filters, I could go and check at my router level, but I'm fairly confident it probably isn't.
Obviously I can't guarantee that it's not making its own DNS requests and sneaking through my filters, I could go and check at my router level, but I'm fairly confident it probably isn't.
Best you can do with any of these devices is disconnect them from the Internet.
Best you can do with any of these devices is disconnect them from the Internet.