That's not possible in lemmy currently. It's either full hiding (so hiding from local/all, searches and the community unless they subscribe) or not hiding
Theoretically could be added in a pr though
Theres technically a code review community at [email protected] although ive seen some people also post code reviews in the language/engine communities
we also host an instance of opengist at https://blocks.programming.dev/ as an alternative to those if wanted
I had @icon there and the cache didnt fully update yet
Ah yeah I need to refresh the data, ill do that later
Nobody reported it as down to me, I can bring it back up
Been working on some other projects recently so havent really looked at that site much
Useful to not need to tab back to it after changing one thing in the inspector
We just added a couple more people to have server access and ideally that situation wont happen again
That problem specifially could only be reproduced on the main server so fixes couldnt be tested without taking the entire site down and at some point after the 0.19.5 upgrade (when the issue happened) it became too late to roll the server back since there was too many activities that came in but if it happens again after an upgrade we would roll back pretty much instantly)
dbzer0 does seem like a better option for general privacy discussion though
Useful for things you don't edit but still would need to scroll past
lemmygrad isnt defederated from but many of their communities are hidden from the feeds by default (so you dont see them unless you subscribe to them)
same thing for some other instances like lemmynsfw
ones that are more recent wont be hidden since I havent been able to due to the issues but I should be doing another hiding round soon
Capitalized will also put a space when swapping between letter and nums
Sites back. I reindexed every table although the only one that seemed to be affected by the issues was the comment table (it had duplicates I had to remove similar to what I did for the post and community tables before)
Site will slowly catch up in activities over the next couple hours so youll see posts, etc. that were made in the few hours it was down slowly come in
No votes or comments were connected to the duplicates but yeah if there was some you would move it over to the other one
The posts that had comments were the posts that were uniquely on the other community and those moved over with the post when I updated the community of the post
Sites back, communities that previously had their community page not vieweable are now viewable
An example of this is https://programming.dev/c/a11y
Basically what I did was before the maintenance exported every single post in the post table and use a js script to check for duplicate ap_ids (checking using sql itself didnt work due to broken indices so it was always missing some). Then I generated sql statements to remove duplicate posts that had higher ids than the other posts theyre a duplicate of. Ran all those during maintenance and since all duplicate ap_ids were removed I could now reindex the table to fix the broken indices
Did the same for communities after the posts (but also did some statements to move posts from one version of the community to the other)
Site might be slow for a tiny bit as it processes the 2 hour of activities that were generated while it was down
Export range (used to create a box in the inspector for choosing a number within a range) can have extra things added to it in any additional arguments after the main 3.
One of these is the addition of a suffix that can be set to whatever you want
Then you can easily move to bookmarks using the go to button at the top or using ctrl+b and ctrl+shift+b
If you also just have a large block of text it lets you see a large amount of the text instead of only a small part at a time
you cant nest export_subgroups within each other but you can use slashes for nesting
You will need to close and then reopen the node to see the changes and icon must be put before the class declaration
It was put under the wrong category looks like
I originally hid it due to it being primarily bot content (but seems like the community changed at some point to not be bot spam)
Heres an example of what the community used to look like