

Osmand?
Osmand?
You’re assuming it is useful enough to find the person, and not just A person.
What’s scary here is the lack of training/understanding on the investigation side… This is just ignorance.
the family deserves to know that we tried everything
Like, have you tried praying? We don’t have any data, so it may be effective.
I run RSS2email and… read my RSS as emails, delivered fresh every morning :)
Been using self-hosted, static website builder https://simonrepp.com/faircamp/ with satisfying results here
Keep instance small, with all users in the same timezone. Use NixOS, let it update everynight automatically and safely. It’s good enough for a small service, downtime is mostly when people are sleeping.
Try again elsewhere, you’ll eventually find the right place!
Assembling a second dynamics (analog compressor). First one took me over 8h of work.
At this point though, you might as well skip AI and commission an artist (photographer, painter, fx).
Have you tried the archive link? There’s no need to sign in with it
Users can already do so, what would instance-level block bring?
I’ll let you compare the nix 2.4 manual page (https://web.archive.org/web/20211201073051/https://nixos.org/manual/nix/stable/command-ref/new-cli/nix3-flake.html) with the current one (https://nixos.org/manual/nix/stable/command-ref/new-cli/nix3-flake.html).
The flakes interface of nix may change in the future, and you should be prepared to update your code, documentation etc. if and when that happens. Consider flakes have been around since nix 2.4 and the interface haven’t drastically changed since then. If that risk sounds acceptable to you, then do use it :)
There is an ongoing effort to get flakes away from the experimental category, but as you may guess, it is a big chunk to stabilize all at once. The original RFC was closed https://github.com/NixOS/rfcs/pull/49 a long while ago, due to it describing the experimental feature, and not the final one. AFAIK, there’s no “one” RFC being discussed on finalizing an initial stable version of flakes (but I could swear I’ve heard of one).
I had “weathering steel” in mind, butt you’re right, even in this case, rust still eats at it, just slower.
Is it now? Github says it’s Rust at 80%. And a layer of rust is a good protection again further rust 😃
not enough nodes were there
And a bit later he mentions “Not just all account servers; different kinds of services”. I have a feeling this has been overlooked in the recent discussions about Threads. The fediverse is an excellent base to launch a myriad of varied kinds of services, not all of them “account servers” like lemmy, mastodon, pixelfed, etc. Let’s also build more bots and automated services too :3 It could be games played through fedi, it could be statistics, admin tools, and whatever comes to mind.
This is the kind of thing that would be added value even for huge account nodes, and would probably act as a deterrent to want to change the rules of the game (making changes to ActivityPub). If you change the proto, your users would lose access to all the nice things that exist outside of the instance, quite the backlash, like what happened with reddit.
What do you all think?
Good reminder that: small instances = small impact. Both true for the positive and the negative.
One could make the argument that 5000 users is still not mass adoption. If that is enough activity, then mass adoption is not a requirement for the fediverse to be a nice social place to be.
https://gist.github.com/yunfachi/6c073cc6edc18f78cfc60bb9bb3f7143