Anonymous ID: b73a9c June 28, 2022, 10:53 a.m. No.16546797   🗄️.is 🔗kun   >>6812 >>6941

3619

Nov 21, 2019 10:18:33 PM EST

Q !!mG7VJxZNCI ID: 000000 No. 7359408

Nov 21, 2019 9:39:58 PM EST

Ron ID: 000000 No. 7359370

Nov 21, 2019 9:16:49 PM EST

Q !!mG7VJxZNCI ID: 000000 No. 7359354

https://twitter.com/CodeMonkeyZ/status/1197692575915757568

/CM/

Platform not fully functional / stable.

Pic uploads not secure / functional.

Suggest update delay to prevent IDEN re-check re: trip update failure until platform stabilized.

Q

>>7359354

Images that are served via TOR broke yesterday, we are checking why and should have it fixed up soon.

Caching is still a bit buggy, and likewise we should have that fixed up soon.

I will do my best to have these things fixed up before the end of the weekend.

 

An easy way to verify yourself after the upcoming SALT rotation is:

  1. Migrate /patriotsfight/ before the rotation

  2. Post with current tripcode on /patriotsfight/

  3. After SALT rotation, post with new tripcode on /patriotsfight/

  4. Qresearch BO adds your updated tripcode to the /qresearch/ whitelist

 

Let me know if you want to migrate /patriotsfight/. The login credentials will be the same as back in August, and you can login via tor at this url:

http://sys.jthnx5wyvjvzsxtu.onion/mod.php?/

or via clearnet at this url:

https://sys.jthnx5wyvjvzsxtu.onion/mod.php?/

 

The SALT rotation is an important maintenance task, and will help improve overall site stability.

 

Our current tasks to get back to full stability:

  1. SALT rotation

  2. Fix quality-of-life bugs (caching, images, etc)

  3. Launch project odin (checkmate against deplatforming)

  4. Finish board migration

  5. Migrate to a new ISP currently being setup (will improve site access speeds and stability)

  6. Bring back board creation (with a simple vetting process)

  7. Install the new captcha system that we are building

  8. Extinguish fires that pop up

>>7359370

/pf/ was taken down [cleared of content] just prior to platform TERM [specific reason].

NAT SEC [charter] prevents use of 'keys' to establish IDEN via public utility/domain - non_reg.

Formation of 'clean' board possible to lock in trip(s) issues w/ safeguards.

Q