overview for kosmo

AMD Ready For Ryzen Linux Systems To Use AMD P-State Active Mode By Default in c/linux@lemmy.ml

[–] kosmo@satl.ink 8 points 2 years ago

It's likely to increase performance by running the CPU cooler when idle and better mapping thermal behavior to performace, so it's an improvement for things like the steam deck or gaming as well.

Intended way to federate in c/lemmy@lemmy.ml

[–] kosmo@satl.ink 2 points 2 years ago

Once you add things to the AllowList, only things in the AllowList federate. You probably want to use empty AllowList + populate BlockList as needed.

1

Mastodon federation & reinstallation (satl.ink)

submitted 2 years ago* (last edited 2 years ago) by kosmo@satl.ink to c/fediverse@lemmy.ml

0 comments fedilink

So, I experimented with running a mastodon instance on another domain. Due to issues with the "cache" directory actually requiring persistence, and thus somehow making all custom emojis 404, I decided to wipe it and try a different fediverse server on that domain. I didn't know about or expect to need to run tootctl self-destruct, so I dropped the database and installed something else. I still have the instance key around, but I realize I should have unsubscribed/deleted all accounts first. Is my other domain now broken permanently for the fediverse? Can I somehow use the extant instance key to unbreak it? I can't find clear documentation of the mastodon cryptosystem, and if it's permanent, this feels like a denial-of-service vector more than a security feature...

Following remote communities is hard. in c/lemmy@lemmy.ml

[–] kosmo@satl.ink 1 points 2 years ago (8 children)

At the simplest I feel a chrome extension or similar would be straightforward. A more native flow doing some sort of faux login/modal that could subscribe on the primary host would be better.

lemmy.ml is overloaded, use other instances instead in c/lemmy@lemmy.ml

[–] kosmo@satl.ink 1 points 2 years ago (1 children)

The backend especially is not too demanding (thanks to using a compiled binary via Rust). The database demands probably scale, but postgres scaling is relatively well understood. I think right now the least scalable parts look like the frontend node and websocket stuff, but that can be improved. I'm not sure how I feel about Activity Pub protocol wise, it feels pretty chatty, so transit scalability might be something else to consider.