20 days ago 31 views

2025-03-10

[[Andrew]], [[Calix]], [[Dan]], [[Flancian]].

2025-02-10

[[Dan]], [[Edsu]], [[Flacian]].

2025-02-03

[[Dan]], [[Flacian]], [[Calix]]
https://git.coop/social.coop/tech/ansible/-/merge_requests/51

  1. Write a draft summary of our conversations
  2. With your joint approval, post it for others to read (Loomio?)
  3. Read the wiki link above (!) and consider incorporating changes from our experiences
  4. Make sure Calyx gets meeting info for our next CWG meeting.

2025-01-20

[[Dan]], [[Flacian]], [[Calix]]

https://agriculturaljusticeproject.org/toolkit/resources/relations/soulfire-courageous-conversations/
https://srinathramakrihttps://seedsforchange.org.uk/downloads/conflictbooklet.pdf
shnan.wordpress.com/wp-content/uploads/2016/07/non-violent-communication-summary.pdf

Timeline

dnlbrnds: Good day everybody — I think this has been discussed when Threads went live, but with the recent developments around Meta, do you think we shall reconsider de-federating it?

3wc: I have to say the previous decisions seemed like a textbook case of how decisionmaking processes are vulnerable to how the question is framed, and it would be great to try to correct that this time around
it’s clear to me that Threads should be defederated based on our existing policy, so I think the proposal should be framed as “Should we make an exception to our policy for Meta”, which I think is the correct & fair allocation of “status quo” / “do nothing” voting

flancian suggests a vote would be needed for taking action and “I’d recommend interested people ideally get together to agree on the phasing and then start one”

dnlbrnds and 3wc discuss co-drafting a proposal

Flancian: Thanks for the context and sharing your view! FWIW Meta does have policies still and claims to enforce them, the question then seems to be whether the policies are good, mediocre or actively harmful (the “encouraging abuse” argument). Abuse to members of our instance has not materialized from threads.net yet AFAICT; I can review moderation reports to be sure if people think that would be an interesting data point.

3wc: [are you saying] that your interpretation is that if a server’s policy only bans some hate speech (while explicitly allowing other types) then it does not “[lack] policies … to deal with hate speech”?

Flancian: […] I was trying to say that Meta does seem to be defining hate speech and is apparently “just” choosing to exclude some classes of speech from this category, which is different than not caring about hate speech at all like e.g. nazi instances do.

3wc: I have read many Nazi instances’ policies and a significant number are similar to Facebook’s - some hate speech is disallowed, some is explicitly allowed
8HJYUNMMMMMrts a thread with the CWG

16:39 UTC foolishowl: It sounds like several of our moderators think it’s best to have a vote on this, and I haven’t seen any arguments against doing so. Unfortunately I’m bogged down at work, so I can’t do a proper job drafting it at the moment, but I’ll work on it when I can.

19:45 UTC Flancian: https://doc.anagora.org/against-meta, open to universal access, please review/edit :)

20:58 UTC Flancian: I will check back later tonight and run the vote by default, then we can go further in Loomio? I think it’s a good opportunity for people to express their views on what is happening. I hope the community finds the time to participate widely.

21:25 UTC Flancian: PSA: https://www.loomio.com/d/u1OkUA6M/clarity-on-stance-with-regards-to-threads/30 is the vote. please vote at your earliest convenience, but also optionally take the time to consider what you would like to publish on such an occasion; I think history will likely look back on both corporations and the commons at this moment. We have six days as per our governance template.

22:00 UTC: flancian and 3wc have a 1:1 discussion about the vote

3wc: “as i said in DM, I will take you on good faith that that was your conscious intention. I will also observe that your choice of framing has made it more likely that the vote would reach your desired outcome and placed the burden on more-marginalised people to advocate for ourselves to maintain our existing defences - and encourage you to consider what subconscious bias might also have been a factor in this choice”

22:32 UTC 3wc: I have now proposed an alternative vote, “Grant an exemption to the social.coop federation abuse policy for threads.net” https://www.loomio.com/p/XsNQByhG/proposal-grant-an-exception-to-the-social-coop-federation-abuse-policy-for-threads-net
3wc: I apologise for the confusion caused by parallel votes. I hope we do not need to find out what happens if the results disagree with each other

12:44 UTC Flancian: 20% is also significant enough that, if it holds, we should probably discuss as a community how exactly we go through enacting the suspend to make sure people don’t lose significant data (as per the message above; but that is only one particular implementation plan).

Flancian: I’ve now called this out to the CWG and TWG so we can plan accordingly. the CWG is meeting on the 23rd and this is a topic of discussion (how to defederate if the vote holds). so people should not expect a suspend action before then, maybe before EOM. if anybody has any issues with this, please raise.

3wc: 85% of people who voted (in the second poll) have actively disagreed with making an exception to the policy based on scale. But you’re pushing for an exception to the policy based on scale?
if people want “how many ‘follow’ relationships exist between social.coop and the instance?” to be a factor in the implementation of the Federation abuse policy then let’s get a proposal for it to be added?

Flancian: “Pushing” is forceful language that does not represent what I feel.

Flancian: Finally, can we acknowledge I voted to suspend and not to grant an exception to our policies and I’m acting under the working assumption the first vote will pass and the second will not? In which way do you think I am misreading, mishandling or worsening the situation
3wc ~ they/them? Thank you for clarifying.

Timeline highlights / overview

F: Feeling very invested in things going into the situation. Suggested vote on the 8th, saw people worrying. 9th read more reaction, started changing my mind from “limit” based on lack of practical impact, to “suspend” based on emotional impact. 10th felt like the issue escalated. My POV: asked to wait. Felt like people were not OK with that. Suggested foolishowl create a thread. Didn’t see pushback against calling a vote. Started a vote 1.5 hours after sending draft. Felt like reaction that took place after was not as constructive as it could have been. Felt responsibility as CWG member to start the vote. Did not feel in a good position to manage the conflict. Assumptions about personal motivations. Led to feeling disappointed.

C: Felt disappointed as well when I saw the vote framed in this way. Felt that future at coop was uncertain. Suspicious about the shortness of the draft review. Felt unseen/heard.

Next actions

2024-01-13

2024-11-25

2024-11-04

2024-10-07

2024-10-07

2024-09-23

2024-08-26

2024-08-06

2024-07-29

2024-07-15

2024-07-01

2024-06-01

Here: [[flancian]] trying to bump to the latest security patch :)

cd social.coop/ansible
vi roles/social.coop/files/docker-compose.yml
. .env
ansible-playbook -CD rhizome.playbook.yml  # check the diff in dry run
ansible-playbook -D rhizome.playbook.yml  # -D means diff, omitting -C makes it stick

2024-05-20

Here: [[Calix]] [[flancian]]

2024-05-06 – Long time no see! (at least with notes?) :)

Here: [[flancian]], [[dphiffer]], [[evan boehs]]?

2024-04-13 – Tech Working Group Open House!

Here: [[Calix]], [[flancian]], Melissa (ansate), Jamie, Caitlin

2024-03-25

Here: [[Calix]] [[flancian]]

2024-02-27

Here: [[Calix]] [[edsu]] [[flancian]]

2024-02-13

Here: [[flancian]] [[Calix]] [[andrewe]]

2023-12-18 … [[2024-01-01]] … [[2024-01-15]]

Here: [[flancian]] [[Calix]] :)

Wish you all a great holiday season! Some topics:

2023-12-04

Here: [[edsu]], [[Flancian]]

2023-10-09

Here: [[Akshay]], [[edsu]]I’ll b, [[Calix]], [[Flancian]]

[[2023-09-26]]

Here: [[Akshay]] [[Flancian]] [[Calix]]

Mastodon upgrade party!

[[2023-09-25]]

Here: [[Akshay]] [[Flancian]]

[[2023-09-11]]

Here: [[Flancian]]

[[2023-08-28]]

Here: [[Calix]] [[Flancian]]

[[2023-08-14]]

Here: [[Flancian]]

[[2023-07-17]]

Here: [[Akshay]] [[Flancian]] [[Calix]]

[[2023-07-05]]

Here: [[Akshay]] [[Ed Summers]] [[Flancian]]

[[2023-06-19]]

Here: Akshay, Flancian, 3wc/calix

[[2023-06-05]]

Here: edsu, Akshay, Flancian, (a late Calix)

[[2023-05-22]]

Here: Akshay, Eduardo, Ed …

[[2023-05-15]]

Here: Akshay, Eduardo, …

[[2023-05-08]]

Here: Eduardo, …

[[2023-03-27]]

Here: Eduardo, Akskhay, Calix

[[2023-03-13]]

Here: Eduardo, Akskhay, Calix

[[2023-02-27]]

[[2023-02-13]]

[[2023-01-30]]

We agreed on 2022-01-23 to schedule a maintenance window to test the database restore on Hypha (our new Hetzner server). If all goes well with the restore and testing we may decide to leave it running there.

This checklist was copied from a comment that Akshay put in a GitCoop issue.

Cleanup:

log

[[2023-01-23]]

[[2023-01-09]]

[[2022-12-19]]

[[2022-12-05]]

[[2022-11-28]]

[[2022-11-21 18:00 UTC]]

sudo touch /opt/social.coop/var/www/maintenance_mode_on

sudo docker-compose stop web streaming sidekiq sidekiq-scheduler sidekiq-default-q sidekiq-push-q sidekiq-pull-q es

sudo systemctl start pg-dump-to-s3.service

sudo docker-compose exec db vacuumdb  -U postgres --all --full --analyze --verbose

sudo systemctl start pg-dump-to-s3.service

# validate that the backup is in the bucket and that we are able to retrieve it, otherwise move manually to [[hypha]]

sudo docker-compose exec db pg_dumpall -U postgres > ../../var/lib/postgresql/9.6.backup

sudo docker-compose down --remove-orphans

sudo git checkout 3_5_upgrade

sudo docker-compose up -d db

sudo cat ../../var/lib/postgresql/9.6.backup | docker-compose exec -T db psql -U postgres

sudo docker-compose logs -t db

sudo docker-compose run --rm -e SKIP_POST_DEPLOYMENT_MIGRATIONS=true web rails db:migrate

sudo docker-compose down --remove-orphans

sudo docker-compose up --scale sidekiq-pull-q=4 --scale sidekiq-default-q=12  --scale sidekiq-push-q=4 -d

sudo docker-compose run --rm web bin/tootctl cache clear

sudo docker-compose run --rm web rails db:migrate

sudo docker-compose down --remove-orphans

sudo docker-compose up --scale sidekiq-pull-q=4 --scale sidekiq-default-q=12  --scale sidekiq-push-q=4 -d


Done


==ROLLBACK==


sudo docker-compose down --remove-orphans

git checkout rebuild

sudo docker-compose up --scale sidekiq-pull-q=4 --scale sidekiq-default-q=12  --scale sidekiq-push-q=4 -d

[[2022-11-14 19:00 UTC]]

Several past instances had notes only on [[loomio]]

2022-05-27

2022-05-20