🧮 USERS:2 FEEDS:6 TWTS:721 ARCHIVED:131812 CACHE:17882 FOLLOWERS:27 FOLLOWING:50
🧮 USERS:1 FEEDS:2 TWTS:66 ARCHIVED:12445 CACHE:821 FOLLOWERS:11 FOLLOWING:14
**Pink Monday💕 @prettylittlething **
Pink Monday💕 @prettylittlething
Shop their cyber sale today for up to 80% off! Full haul in bio!
 on screens. There’s a chance that you might update and find your font extra large or small. If so, you can just manually add
xrandr --dpi 96to the beginning of yourxprofileto set the DPI to the typical 96 (or whatever number looks best).
- I have no switched new installs of LARBS from using Pulseaudio to Pipewire as an … ⌘ Read more
Important notes for LARBS users
Two notes for LARBS users:
- Xorg went through some updates last week that changed how it calculates dots-per-inch (DPI) on screens. There’s a chance that you might update and find your font extra large or small. If so, you can just manually add
xrandr --dpi 96to the beginning of yourxprofileto set the DPI to the typical 96 (or whatever number looks best).
- I have no switched new installs of LARBS from using Pulseaudio to Pipewire as an … ⌘ Read more
🧮 USERS:1 FEEDS:2 TWTS:31 ARCHIVED:8745 CACHE:747 FOLLOWERS:8 FOLLOWING:10
🧮 USERS:1 FEEDS:2 TWTS:27 ARCHIVED:8654 CACHE:720 FOLLOWERS:8 FOLLOWING:10
Linux Sucks - Audio Book - Chapter 1
Listen now (5 min) | After Covid derailed my publishing schedule, things are finally fully back on track! My voice is now totally back to normal and everything! Huzzah! For the paying subscribers to The Lunduke Journal you will now start receiving audio book chapters of “Linux Sucks” regularly (this is Chapter 1, with Chapter 2 to follow). New text chapters will also be posted to the ⌘ Read more
🧮 USERS:1 FEEDS:2 TWTS:25 ARCHIVED:8268 CACHE:685 FOLLOWERS:8 FOLLOWING:9
FOLLOW: @xuu@txt.sour.is from @darch2@yarn.algorave.dk using yarnd/0.6.2@86938ca
🧮 USERS:1 FEEDS:2 TWTS:24 ARCHIVED:8158 CACHE:641 FOLLOWERS:8 FOLLOWING:9
Save the Date: Next Community All Hands on December 9th
We’re one month away from our next Community All Hands event, on December 9th at 8am PST/5pm CET. This is a unique opportunity for Docker staff, Captains, and the broader Docker community to come together for live company updates, product updates, demos, community shout-outs and Q&A. The last all-hands gathered more than 2,000 attendees from […]
The post [Save the Date: Next Community All Hands on December 9th](https:/ … ⌘ Read more
🧮 USERS:1 FEEDS:2 TWTS:16 ARCHIVED:6605 CACHE:541 FOLLOWERS:5 FOLLOWING:8
Docker Desktop 4.2 Release: Save Your Battery with Pause / Resume, and Say Goodbye to the Update Pop-up
With Docker Desktop 4.2 we’re excited to introduce Pause / Resume as well as a host of changes to make it easier for you to manage updates. These features are available to Docker Desktop users on any subscription tier. Save your battery with Pause / Resume Pause / Resume gives developers the power to pause […]
The post [Docker … ⌘ Read more
@darch@twtxt.net
Getting this when trying to use it:
error executing template timeline: template: timeline:131:43: executing "twt" at <formatForDateTime>: wrong number of args for formatForDateTime: want 2 got 1
x86chi/FEMOE
🏖 A simply theme for hugo. You can see preview at http://www.frontend.moe
Language: HTML
Star: 2
Watch: 2 ⌘ Read more
On the blog: Free Culture Book Club — Occupy This Novel!, Part 2 https://john.colagioia.net/blog/2021/10/30/occupy2.html #freeculture #bookclub
Source code released for Little Big Adventure 1 & 2!
The engines of the classic 1990s 3D adventure games get released under the GPL. ⌘ Read more
My thoughts about range requests
Additionally to pagination also range request should be used to reduce traffic.
I understand that there are corner cases making this a complicated matter.
I would like to see a meta header saying that the given twtxt is append only with increasing timestamps so that a simple strategy can detect valid content fetched per range request.
- read meta part per range request
- read last fetched twt at expected range (as known from last fetch)
- if fetched content starts with expected twt then process rest of data
- if fetched content doesn’t start with expected twt discard all and fall back to fetching whole twtxt
Pagination (e.g. archiving old content in a different file) will lead to point 4.
Of course especially pods should support range requests, correct @prologic@twtxt.net?
My nutritional supplements aim should be:
- 1 or 1.5 cups of lentils (or any beans you might like better).
- 2 or 2.5 cups of bitter greens.
- 1 cup of your favourite protein (or an egg), grilled, or fried with a little of olive oil.
- 1 or 2 tomatoes, or a handful if of the cherry type.
- No added sugars. If it is sweet, make it have fibre.
- No added salt (or very little and ionised), as salt is everywhere.
Related, I tried wild rice for the first time yesterday. It was different, in a good way.
@prologic@twtxt.net
Thank you, that’s the correct one.
Still I have this in my logs (first access of “eleven” by yarnd):
ip.ip.ip.ip - - [21/Oct/2021:20:05:36 +0000] “GET /eleven.txt HTTP/2.0” 200 344 “-” “yarnd/0.2.0@46bea3f (Pod: twtxt.net Support: https://twtxt.net/support)”
ip.ip.ip.ip - - [21/Oct/2021:20:05:36 +0000] “HEAD /avatar.png HTTP/2.0” 200 0 “-” “yarnd/0.2.0@46bea3f (Pod: twtxt.net Support: https://twtxt.net/support)”
And I guess without avatar.png sitting there I would have seen even more requests like /eleven.txt/avatar.png.
I’ve copied stackeffect.png to avatar.png to make yarnd happy when accessing stackeffect.txt.
So in this setup yarnd fetched eleven.txt along with avatar.png which belongs to another twtxt. This feels buggy.
We all strive to be like the others - more exactly, like the others, but better. (Chapter 2) Book Review: The End of Average - LessWrong
My home and code server now has 2 TB of SSD storage and 16 GB of RAM. While I’ll be using the storage for backups, etc., I’m not quite sure what I can use the 16 GB of RAM for yet. What else can I run besides Home Assistant, AdGuard Home, Drone and Tailscale? I still have my VPS running my websites, Miniflux, Bitwarden, Firefox Sync Server, RSS-Bridge, Firefly III, Nitter and Gitea. 🤔 ⌘ Read more