Been using for what feels like a lifetime, although I went through a few usernames during the late 90s early 00s and somewhere along the way BlueEther or a derivative just stuck, it was after a comment something like “jus putting this out into the blue ether” in a forum post
It has bees asked quite a few times. I would go one further and also have notifications for select subscribed communities
Back 6 months ago we all but had that…
I feel like such a slacker, I must try harder
The only thing that doesn’t seem to federate on my 0.19.1 instance is new subscriptions, but in saying that it looks like the BE restarted an hour ago
see below
select person.id,name,local,local_user.email from person join local_user on person.id = local_user.person_id where person.id =2;
id | name | local | email
----+-----------+-------+---------------------
2 | BlueEther | t | firstname.nz
Email is only available for local users and only if filled in on the signup form
Yes us instance admin can pull the email address form local users.
The main table that all the growth was in is now split and the cached federated content can be dropped with out much work, and there was talk of tuning it to expire at 3 months.
The content on no.lastname.nz (very small instance) is only about 10-15GB including cached images
I have used
UPDATE person
SET deleted = 't'
WHERE id =nnnn;
You can get the id’s from:
SELECT id, name, published
FROM person
WHERE instance_id= 1 and deleted = 'f'
ORDER by id;
There are 3 instance for *.nz, lemmy.nz, no.lastname.nz and feddit.nz
@Dave@lemmy.nz and I (no.lastname.nz) have been workin together so we don’t overlap with nz based communities, with Dave concentrating on general NZ communities and I’m concentrating on more environmental type communities (Wildlife/Outdoors/Trees[therapeutic use based])
We probably need more collaboration for smaller communities, but there will always be different takes on topics and moderation.
The correct way (for your use case) is probably to do a full backup of the database and pictrs database and then import them into the new instance.
This is covered in the documentation