Hey guys, it’s been a long time. I was sick for awhile, so sick I have 2 hospital visits which almost landed me 6ft under. This is why I’ve basically been entirely absent the past few months. This has left Burger all alone to do both the public facing PR type stuff (which used to be my territory) and the backend.
Well, my situation is returning to normal, and thus I am also returning to Burggit. I’d like for you to voice your feedback and what you would like to change and any issues you have specifically.
Something I will be changing is, and I hate to be this guy who comes in and does this. I will be removing the 3Dloli community as I personally believe that community violates our at-a-glance policy. I can not tell the difference for most of these images “at a glance” and since I will be the one looking through these sorts of things for moderation. It’s best for everyone involved that I am able to make good accurate decisions.
I also know that there’s been issues with the Lemmy-NSFW fork being used, some people want us to fork it, make modifications to it and use that. I’m going to shoot this idea down now. Burggit is just me and Burger, there’s no one else here, and we do have other things we like working on. We’re not maintaining an entire special fork. It’s likely that we will just go back to the main Lemmy branch, though I would be open to arguments against that or maybe even suggestions for already existing forks to use.
However, I think The Entire Circus made a good point in this post and personally, I agree with his points.
Anyway this is just kind of an initial post letting you know that I am returning and things will be changing. Hopefully this will be overall a good thing for everyone involved. Happy to be back.
Got the reverse proxy banner replacement working:
I do not wish to maintain a git fork of the software. If someone else wants to take on that mantle, they’re more than welcome. I already have enough on my plate. I’m already maintaining the Matrix, Kbin, and this very instance. The few times I used git, I found it frustrating to use.
Thanks for taking the time to wrangle and update it, I think your updating of the banner text is definitely the right step.
For the 2 visitor UX changes that were generally supported (not auto-expanding NSFW posts and blurring thumbnails), I’m admittedly not familiar with Git myself. Based on the Github discussion of this, would changing both settings at the backend to “false” help to change the default/visitor view? If it’s just changing these two settings, would that constitute a fork that needs long-term maintenance, or could it just be a one-and-done setting change?
If it’s a fork that needs long-term maintenance, I’ll try asking around and see if anyone has the necessary skills to maintain a UI fork with these two changes made. I do think it’s important, it seems to be broadly supported based on the comments in discussions thus far, and the current problem seems to be a lack of capacity rather than will, so if that can be overcome, it may be possible to enact the changes.
NSFW images blurred and no longer auto expand.
The relevant patches need to be applied in lemmy-ui’s source tree (https://github.com/lemmynsfw/lemmy-ui) :
#src/shared/components/post/post-listing.tsx --- post-listing.tsx 2023-12-26 03:43:17.871725423 +0000 +++ post-listing.tsxd 2024-01-04 20:29:53.433999085 +0000 @@ -96,7 +96,7 @@ export class PostListing extends Component<PostListingProps, PostListingState> { state: PostListingState = { showEdit: false, - imageExpanded: true, + imageExpanded: false, viewSource: false, showAdvanced: false, showBody: false,#src/shared/components/common/pictrs-image.tsx --- pictrs-image.tsx 2023-12-26 03:43:17.859724985 +0000 +++ pictrs-image.tsxd 2024-01-04 20:25:41.355154850 +0000 @@ -26,7 +26,7 @@ render() { const { src, icon, iconOverlay, banner, thumbnail, nsfw, pushup, cardTop } = this.props; - let user_blur_nsfw = false; + let user_blur_nsfw = true; if (UserService.Instance.myUserInfo) { user_blur_nsfw = UserService.Instance.myUserInfo?.local_user_view.local_user.blur_nsfw;If at any point this proves to be a headache to maintain, then we’ll have to explore other options.
Better yet, let’s make this more universal. I have no idea what I was thinking using a patch for a codebase that frequently changes.
sed -i 's/imageExpanded: true/imageExpanded: false/g' lemmy-ui/src/shared/components/post/post-listing.tsx sed -i 's/let user_blur_nsfw = false;/let user_blur_nsfw = true;/g' lemmy-ui/src/shared/components/common/pictrs-image.tsxFor some reason I didn’t receive a notification about this reply, but thanks for making the changes!
Hah: I actually wanted the opposite, it annoys me how by default Lemmy blurs all NSFW thumbnails by default. Why the devs can’t make this a simple user preference is beyond me.
That’s been added as a user preference in 0.19.
Oh nice: Thank you for that! Much better now.
Is that disclaimer necessary? It even uses annoying browser alerts and makes everything look broken. I presume people can see it’s NSFW from the description if it’s not obvious otherwise: Having to tell people what to do or not do based on who or where they may be behind their computer screen has gotten so old and weird for the modern day internet. Other than that I’m sorry you went through a rough time and am glad you’re okay, take care and thanks for everything you’ve been offering the internet!
The disclaimer is not necessary, however removing it without touching the code would be fairly difficult due to the way the LemmyNSFW fork is setup. Makes everything super hard to navigate and modify. All the code is minified and otherwise obscured beyond human comprehension. This is why we replace the text as opposed to removing the actual disclaimer altogether.
It’s less work for me. Since all I’m doing is a text replace at the reverse proxy level. I’m not having to change code for this since I’m just replacing what gets sent out. It’d be one thing if this breaks apps, but afaik apps just use the Lemmy API.
Welcome back Disa
Happy to be back!
That girl looks so adorable and ready for sweet loving plap plap plaps,
please tell me who she is?
That’s a shota. Not a loli.
Goddamn.
That is the cutest boy I’ve ever seen.
100% agreed, @Disabled@burggit.moe is cute!
Good to have you back, Disa.
I also know that there’s been issues with the Lemmy-NSFW fork being used, some people want us to fork it, make modifications to it and use that. I’m going to shoot this idea down now. Burggit is just me and Burger, there’s no one else here, and we do have other things we like working on. We’re not maintaining an entire special fork. It’s likely that we will just go back to the main Lemmy branch, though I would be open to arguments against that or maybe even suggestions for already existing forks to use.
If compromise modifications aren’t an option, then I think it’s crucial that we stick with the NSFW patched version as it is. I conjecture that allowing NSFW posts and communities to be seen without logging in will make the difference between this place slowly growing vs slowly dying. I don’t have access to numbers to back this up, and we’d likely need a longer trial run of the NSFW patched version to judge whether there’s an inflection point. However, the “ghost town” effect that has been mentioned is real. People largely will not go through a registration process before they have an idea of what the site has to offer.
I missed you!
Aww, thanks! Feels good to be appreciated! 🥰 It’s good to be back!
Anyone have alternative to burggit? Obviously doesn’t have to be lemmy, as this didn’t take off.
It is kind of bewildering how there isnt more lolisho on lemmy, considering how big it was on reddit before they banned it.
I think I’ve mentioned this before, but I believe the reason why lolisho communities havent taken off on lemmy is because they were already exiled from reddit a long time ago and have already found new homes before the fediverse was a viable alternative; laces like lolicit (R.I.P.) and ATF.
ATF remains one of the top online communities for such content and there is little reason as yet for a mass exodus to the fediverse.
Honestly the only reason im here at all is because I dont like mobile webpages so I come here when on my phone instead.
Welcome back, it’s been a while.
In my opinion burggit should return to a official lemmy version, its not worth the trouble, as the patch messes up some apps as well. Its not hard to make a account here and it may help keeping burggit out of trouble regarding age verification.
(kinda thought you went 6ft under after your pfp turned black and white)
I’m not familiar with any apps, we’ve always suggested use of the web app as we found other apps were lacking in multiple ways.
I also think with the patches applied it kind of makes the best of both worlds, since people can see NSFW posts, but they aren’t immediately flashed with NSFW content if they don’t want to look at it.
Apps have pros and cons, i personally use connect, its good for me.
Yeah i see where you come from but let’s be real, when you search for burggit you already know what it is about, Noone just finds us.
While that might be true, people have many different tastes and there’s lots of fetish content on this site. What might be appealing to one person could severely disturbing to another. It’s best not to flash people (in my opinion) with a ton of expanded NSFW images if they do not want to expand them. Back when we had things auto expand and unblurred, I personally saw some things that I was not personally ready for. Not like they outright disturbed me or anything, but they were just more than I was bargaining for in that very moment.
And having no NSFW shown at all unless you make an account makes the site seem like it’s way less active than it is. We’ve actually noticed a few new faces show up since we implemented the patch, I don’t exactly know if it’s due to the patch or not, but it’s definitely noticeable.
We tried an app called Boost and didn’t have any issues. And it’d be very difficult for us to make sure the site (which we are prioritizing the desktop experience for) worked on all the apps. Since they all might have their own little quirks as to how they grab/display content.
Connect had a patch today, seems to work better now, less broken, only problem is that i cant open profile pages on burggit, wich is acceptable.
And if its working good now i don’t have any problem, its just that i don’t think of people that don’t make a account here to customize their experience, my content is pretty tame compared to the other stuff for example. Its definitely good that the auto expand is off and the stuff stays blurred on web. (wich is one of what i like the apps for, as you can blur more specific than unblur all or blur all)
Thanks for creating this pinned feedback post. I think the post linked covers my thoughts, so there’s no point pasting it again here. Since that post, I think the suggestions by RA2lover (“blurred NSFW thumbnails” and “non auto-expanded images” for visitors/non-registered users) would be a good compromise. This seems to be broadly supported from those that replied in the thread, and it would be on par with Reddit’s approach towards NSFW content visibility for visitors.
However, I’m not sure if this requires modifications that have been covered above - if it does and it isn’t possible, then I’m in favor of a reversion to the original login/registration-gated NSFW posts and communities.
It might be a ghost-town (for now), but I suspect that’s better than rolling the dice on whether a visitor and potential joinee sees something they quite dislike splashed across their screen on their first visit, and associates that with the entire branch as a whole. Given the ratio of NSFW to SFW posts already noted, I reckon that dice doesn’t need too many rolls for that outcome. This place might still end up ghost-town, but with a significantly worse off reputation among those that hear horror stories of “Could you believe I saw ___ on the front page? God only know what they’re hiding behind locked doors for registered members if that’s what they show to the public” and visit for themselves to find out it’s true.
a significantly worse off reputation among those that hear horror stories of “Could you believe I saw ___ on the front page? God only know what they’re hiding behind locked doors for registered members if that’s what they show to the public”
This ship sailed long ago. There’s no point in trying to appeal to those that are intolerant of the existence of fetish content.
That’s a fair statement. Imo there would still be gradations of fetish content (with some being more extreme than others), and I think if the main concern (which led to the changes) is increasing the userbase, having the more extreme content equally as visible as the less extreme content would be counterproductive to that end.
That said, I think this has been covered to death already, and much of it is just discussing hypotheticals without any data to lead to a conclusive conclusion, so I’ll leave it at that.
