postActiv user group (postactiv) group
-
Annah (maiyannah@community.highlandarrow.com)'s status on Tuesday, 11-Jun-2019 19:26:58 EDT 
Annah
FYI: The new canonical !postactiv repository is at: http://git.postactiv.com/postActiv/postactiv #postactiv -
Annah (maiyannah@community.highlandarrow.com)'s status on Monday, 27-May-2019 22:03:37 EDT
Annah
So, the git repo hosting software (gitea) for !postActiv has developed a crashing problem which appears to be as a result of a bug that has been open and unfixed in gitea for a significant amount of time now, so I am probably going to end up having to set up gitlab again.
In the meantime, you can find the current working dir zipped up here: www.postactiv.com/postActiv.zip (284 MiB)
Reposts appreciated, since other federating software don't really do groups.
!postActiv #postActiv -
Annah (maiyannah@community.highlandarrow.com)'s status on Sunday, 11-Nov-2018 14:56:42 EST
Annah
Note to self: when I do make a !postActiv theme thing, make sure that it works without Javascript to an at least minimum degree. Its annoying as piss browsing all these other instance where you cant even see shit but a blank page without it enabled. -
Annah (maiyannah@community.highlandarrow.com)'s status on Thursday, 04-Oct-2018 00:54:31 EDT
Annah
Deleted ~1000 spam accounts from the !postActiv gitea instance, if yours was accidentally caught up in it, sorry. No one with a repo or commits was removed. -
Annah (maiyannah@community.highlandarrow.com)'s status on Monday, 03-Sep-2018 12:33:55 EDT
Annah
Providing information like MediaWiki's block list as to when, how long, and why someone was sandboxed or silenced, is something that would probably be quite helpful for !postActiv - even if an abusive admin will just not use it, or misuse it. It also provides a canary in the coal mine for those kinds of instances (you can see they're not really taking care with that) And for a properly-governed instance, it helps establish the fairness of these blocks. -
Annah (maiyannah@community.highlandarrow.com)'s status on Thursday, 02-Aug-2018 06:52:53 EDT
Annah
@bob One of things I am going to do with my new styles for !postActiv when I get to it is allow a user to save their own CSS overrides. -
Annah (maiyannah@community.highlandarrow.com)'s status on Monday, 30-Jul-2018 20:40:17 EDT
Annah
Pushing a change to nightly !postActiv that adds a configuration variable to enable nodeinfo - it's disabled by default (making it opt-in, not opt-out)
Set
config['nodeinfo'] = 'enabled'
to opt into nodeinfo
#postActiv -
Annah (maiyannah@community.highlandarrow.com)'s status on Monday, 30-Jul-2018 17:51:38 EDT
Annah
Next change to add to !postActiv is to make nodeinfo stuff configurable. -
Annah (maiyannah@community.highlandarrow.com)'s status on Monday, 30-Jul-2018 07:14:40 EDT
Annah
I really do want to wrangle in proper templating for !postActiv but ots such a large project to disentangle all the hardcoded HTML from statusnet/GNU social -
Annah (maiyannah@community.highlandarrow.com)'s status on Sunday, 29-Jul-2018 21:12:07 EDT
Annah
Going to try to put to rest the myriad niggling little problems and add a few convinence features to !postActiv before I get heavy into doing Disapora federation For Reals.
I think I have that federation down in a test environment save for a few strange edge cases that I can't reliably replicate, but those have me thinking it might fall apart spectacularly when I go to actually try it in production. We'll see I guess! -
Annah (maiyannah@community.highlandarrow.com)'s status on Sunday, 29-Jul-2018 16:58:14 EDT
Annah
Reminder that you can submit both bugs and feature requests for !postActiv at http://gitea.postactiv.com/postActiv/postActiv/issues -
Annah (maiyannah@community.highlandarrow.com)'s status on Sunday, 29-Jul-2018 16:46:03 EDT
Annah
If someone wants to beat me to implementing the Diaspora protocol in !postActiv, too, incidentally, don't be afraid to work on that also. -
Annah (maiyannah@community.highlandarrow.com)'s status on Sunday, 29-Jul-2018 16:08:16 EDT
Annah
Diaspora federation is the big thing for 1.0.5 in !postActiv and I will consider that version complete when it has it working. #postActiv -
𝕞𝕒𝕣𝕜 (mark@social.heckin.tech)'s status on Wednesday, 11-Jul-2018 10:48:11 EDT 
𝕞𝕒𝕣𝕜
Is there a recommended way to block access to things like https://social.heckin.tech/INSTALL? I don't want to just delete them and it's all tracked in Git anyway so they will show back up when I pull. Think .htaccess is the best way? -
Annah (maiyannah@community.highlandarrow.com)'s status on Thursday, 14-Jun-2018 22:08:05 EDT
Annah
Part of the problem, especially with ActivityPub, is that you have so many ways to display the same information that it becomes impossible to support everyone's different use cases and you have so many edge cases they tesselate together to become a nice little circle Bob Ross would be happy with.
I will probably dictate a specific format with specific endpoints for different things in !postActiv 's new API when I get there, but I'll have to think on what I think would be the most efficient thing in that regard.
I will also hasten to note the old API isn't going anywheres (but the new one is probably what will get development in the future) -
#ApocalypseParty (takeshitakenji@gs.kawa-kun.com)'s status on Friday, 01-Jun-2018 06:05:17 EDT 
#ApocalypseParty
Logging off for the last time now. Leaving the server up for a couple hours so everything can federate before I finally actually pull the plug. !fediverse !gnusocial !postactiv http://u.daggsy.com/1Pf -
Annah (maiyannah@community.highlandarrow.com)'s status on Sunday, 22-Apr-2018 21:54:02 EDT
Annah
I think what I'll do in !postActiv with regard to content warnings is have a default list of ones that are displayed below the fold (ie you need to expand them) that you can override at the instance level, (something like config.spoiler-words = "list of content warnings here") and then each individual user can further tailor it to their own wishes. -
𝕞𝕒𝕣𝕜 (mark@social.heckin.tech)'s status on Wednesday, 11-Apr-2018 07:55:51 EDT
𝕞𝕒𝕣𝕜
!postactiv FWIW, here's a (potentially useful?) infographic from the site the seems to capture the gist of the whole thing. https://social.heckin.tech/attachment/391831 #GDPR -
𝕞𝕒𝕣𝕜 (mark@social.heckin.tech)'s status on Wednesday, 11-Apr-2018 07:51:28 EDT
𝕞𝕒𝕣𝕜
Based on my initial reading of the #GDPR https://www.itgovernance.co.uk/data-protection-dpa-and-eu-data-protection-regulation it seems like the only potential concern for any !postactiv instance admins is with IPs in web logs being retained. It seems like this stuff applies even if your instance is outside of EU but has EU users. -
𝕞𝕒𝕣𝕜 (mark@social.heckin.tech)'s status on Tuesday, 10-Apr-2018 20:59:29 EDT
𝕞𝕒𝕣𝕜
Are there any GDPR concerns for running !postactiv instances?
All Jonkman Microblog content and data are available under the 
