@fack BTW how much ram does it use? Honestly considering running my own until gotosocial + UI options are looking better.
@fack Isn't this all software these days????
@fack I'm sure there's a way to do this.. I'm assuming you cant just shell in and slap your own theme file in there? Does fly let you run your own container? Maybe you can do a quick docker build with the container you use now in the FROM line and then just COPY or RUN whatever you need to get the custom CSS installed .
@auroris@artisan.chat The instance I am on puts a big ugly red CSS border around all non-alt-text'ed images on timelines. I really like that feature, I think it's something more instances / web apps should do.
It looks like there is a small guide on it posted by feditips here:
https://mstdn.social/@feditips/107854431995239439
And the direct link to the css Gist on GitHub: https://gist.github.com/FiXato/3de505b04efefd49a1e3568b70545234
I created an account for my dogs to try out pixelfed: @fedipugs
So far its been a bit rough (no video support, hyperlinks get broken 🪦)
But if you like cute pet pictures maybe it could be worth a follow, I'll try to post when I can and occasionally maybe repost older stuff from the instagram that my partner made in the past.
```
Updating crates.io index
Fetch [===================> ] 82.56%, (163401/213323) resolving deltas
```
Ok, tinygo is definitely not stable enough for this, moving on to trying rust instead https://docs.rs/age/latest/age/ 👀
From yesterday: research into related memory leak here: https://github.com/tinygo-org/tinygo/issues/1140#issuecomment-1314608377
Streaming again, getting to work on running FiloSottile/age to run in the web browsa (compile golang to WASM with tinygo compiler)
music rn: 🎸🎺 Less Than Jake 🧨🍺
https://github.com/mastodon/mastodon/issues/20820
> **USABILITY: init db before configuration is completed causes silent failures / broken instance #20820 **
IMO this is usability bug in mastodon or in the specific mastodon docker container you are using. A configuration issue of this magnitude should trigger massive highly visible error messages, it should trigger the app failing to start.
Querying the db showed:
```
# SELECT username FROM accounts WHERE id=-99;
username
----------------
localhost:3000
```
Which corresponded with the value in the curl
```
"preferredUsername": "localhost:3000",
```
So a quick fix was to connect to psql and run the following update: UPDATE accounts SET username = 'destituent.social' WHERE id=-99;
Now I can toot at my friends over on pixie.town!
Hopefully I didn't burn too many of your CPU cycles @f0x and @forestjohnson thanks!
streaming again today https://stream.sequentialread.com/
music: 🧪🏠 Goop House 🪴👽
I am a web technologist who is interested in supporting and building enjoyable ways for individuals, organizations, and communities to set up and maintain their own server infrastructure, including the hardware part.
I am currently working full time as an SRE 😫, but I am also heavily involved with Cyberia Computer Club and Layer Zero