Recent comments in /f/Ramble
ngmm OP wrote
Reply to comment by BlackWinnerYoshi in Upvoting without JS enabled by ngmm
What the hell, you're right. Just tried in another browser and it worked perfectly. I still don't know what causes this, guess it's time to dive into my about:config...
BlackWinnerYoshi wrote
Reply to Upvoting without JS enabled by ngmm
What do you use that returns 405 Method Not Allowed when upvoting? I just upvoted this post without JavaScreep and without any errors. It only refreshed the page.
Wingless wrote
Reply to We're back up! Here is what happened. by Rambler
I wish somebody would rewrite the Internet from scratch, and shitcan any software feature with an IQ over 85. Also, have a 200-mile exclusion zone for corporate flunkies, enforced by heavy artillery.
Rambler OP wrote
Reply to comment by J0yI9YUX41Wx in We're back up! Here is what happened. by Rambler
Usually it's me pushing untested stuff into production because, "Of course it'll work. It's simple." that breaks stuff. I care a little more about this site and even tested it first, confirmed it worked, and still broke it all.
Eh. It happens, I guess.
J0yI9YUX41Wx wrote
Reply to We're back up! Here is what happened. by Rambler
If it's any consolation, fancy pants professional programmers like me also push an update to production that breaks everything. It's a part of the process. :)
smartypants wrote (edited )
Reply to We're back up! Here is what happened. by Rambler
I felt sad when I learned it was corrupted lost and down.
I now feel much happier with the world.
I am glad you are back.
awdrifter wrote
Reply to We're back up! Here is what happened. by Rambler
Glad to see it's back.
Rambler OP wrote
Reply to comment by Wahaha in We're back up! Here is what happened. by Rambler
Should be able to. If it doesn't, drop me a line and I can at least look into. May not be immediate but I have a to-do list of stuff I work on even if some things are super old on it, haha.
Wahaha wrote
Reply to comment by Rambler in We're back up! Here is what happened. by Rambler
Cool, thank you very much. Then I can enable IP spoofing again without running into issues again.
Rambler OP wrote
Reply to comment by Wahaha in We're back up! Here is what happened. by Rambler
It may be, I see no specific setting for it on my end. There are some config settings available to whitelist certain IPs, which I have to use so Tor Onion, I2P, Loki network users don't get rate limited since they share the same IP of the network connection they're using...
I can individually whitelist accounts which does: "Whitelisting will allow this user to bypass IP bans and some flood protections. Additionally, their IP addresses will no longer be stored." So I've gone ahead and done that for you, but no sort of global "X posts per 1 hour" type of rule to be set.
IPs are merged automatically on a cronjob schedule anyway for everyone so whitelisting really only prevents you from getting stopped by the spam filter that has no configurable settings anywhere.
Wahaha wrote (edited )
Reply to comment by Rambler in We're back up! Here is what happened. by Rambler
I think it's more of a global thing. I get three submissions per hour (independent of where I post), after that: https://i.imgur.com/MQ89QxW.png
Thought it's to prevent spam.
Rambler OP wrote
Reply to comment by Wahaha in We're back up! Here is what happened. by Rambler
Wait, this happens?
Send me a PM with details if you can and I'll review it further as able.
Wahaha wrote
Reply to comment by BlackWinnerYoshi in We're back up! Here is what happened. by Rambler
On a technological level I might agree, but other than that it's just a different experience. Voat didn't limit me to three posts per subverse per hour, like Ramble does. And Voat had some privileges attached to the Internet points you could collect. Above 100 points or so, all restrictions were lifted and beyond that it didn't matter, anymore.
This was a measure against bots and shills. Not sure if it accomplished anything. But since the original Voat is now dead, everything will be better, so there's that.
BlackWinnerYoshi wrote
Reply to comment by Wahaha in We're back up! Here is what happened. by Rambler
At least [RAMBLE] is not Clownflared, doesn't require JavaScript, doesn't limit you to one post per day. You know, it's just better than the now defunct Voat.co.
Wahaha wrote (edited )
Reply to We're back up! Here is what happened. by Rambler
This may not be Voat, but it sure as hell feels like Voat.
Don't stress out too much, if it's down, it's down.
Rambler OP wrote
Reply to We're back up! Here is what happened. by Rambler
Okay, now we're back. I posted this prematurely.
Rambler wrote
Reply to by smartypants
The clearnet IP of the server isn't hidden and the hosting provider is well aware of the site and supportive of free speech.
The anonymity features are to protect the users, not me.
And the email reset has never worked, I've never enabled it. I need to remove mentions of it from the code.
I'll review this in more detail when not on mobile.
boobs wrote
Reply to by smartypants
ramble's servers are not supposed to have anonymity as i understand it.
Rambler OP wrote
Reply to comment by not_bob in Discussion: Striking a balance. by Rambler
Unfortunately there is little I can do in terms of modifying the code. I'm not a developer so custom development to the software is beyond the scope of what I can offer as a solution.
Best I can do is manual tagging of NSFW content that makes it to the front page. Though lately I've not really seen much content that is that concerning on the front page.
not_bob wrote
Reply to Discussion: Striking a balance. by Rambler
I was one of the ones to contact you directly via #saltr. My main focus is on growing the i2p network. I run an i2p site tracker that provides nearly real time status of any i2p website. http://notbob.i2p
This puts me in a similar situation as you. Being forced to say "Yeah, no" from time to time. IE, ground rules.
What I've done is to outright ban anything that involves the exploitation of real children. Then, I put a warning on things that I would think the community as a whole would find offensive. But, that's all it is. A warning. I still provide the keys to get to those sites. It's more of a "Do you really want this?" And, if the person does. Whatever. Not my worry.
And this is where the problem lies, and why I contacted Rambler. I'm an active user on ramble. I enjoy some of the content here. But, there is some that I'd simply rather not see. I don't care if it's here. I just don't want to have to look at it. Neither do new i2p users who are looking for cool stuff to find on the network.
One day I loaded ramble.i2p and my session had expired. I saw things that made me tempted to put the warning tag on ramble.i2p. I didn't Instead I contacted Ramble directly.
Apparently I was not the only one.
I had suggested a more curated approach to what appears on the front page. Note, I am not saying limit free speech. I'm just saying limit what the entry experience is. The first page really matters to new users.
There was discussion in this post about a NSFW tag. I think that would work nicely. With the only real effect of the tag is it preventing said items from appearing on the front page.
Wahaha suggested a few posts from each forum at random. I like that idea. This prevents any one group from taking up the entire front page.
In the end, a mix of the two would likely be the best solution.
It's a hard call. It really is.
spc50 wrote (edited )
Reply to Discussion: Striking a balance. by Rambler
There is a need for free speech.
1st Amendment protection in the States is followed by 2nd that says I have a weapon to force back when you take my right.
Note, the founders didn't put speech first and the gun right tenth.
That said, lots of stuff I am not fond of. Lots of content that doesn't interest me.
All that content if lawful (and very little isn't) has right to exist, especially on an open platform.
Moderating or curating the front side main view --- that typically is popularity based. I'd stick to that approach. Whatever people are upvoting and active commenting on rises to front.
If long term that is NSFW content and "hate" speech then might need to reconsider the approach.
Front page placement should be the best of. Nothing wrong with decent researched, breaking content, funny stuff, original content, etc. Just don't want NSFW, CP, gore, and overt ignorant hate stuff up front.
Hate speech I mean in truest form. Advocating harm to people because of their anything --- isn't good. Labeling whole race un-salvageable cause of pigment or origin, yeah, that's hate speech or at least on the fringe of it.
beni_hull OP wrote
Reply to comment by Rambler in Request old.reddit layout option by beni_hull
Thanks for addressing that.
It's great to hear that you too prefer "old reddit" layout. Maybe it is quicker and easier to start with the newer reddit style (?), but a change later or a toggle switch could really boost the utility for some. I ran into a group on one of the many reddit clones that preferred the new style, but it seems obvious that some of the larger subs with long discussion threads at reddit should have the old format.
Toxicant wrote
Reply to Discussion: Striking a balance. by Rambler
while I do support speaking your mind you do have to be careful tolerating the intolerant or the next thing you know you are the new daily stormer.
Rambler OP wrote
Reply to Discussion: Striking a balance. by Rambler
Weird. Some folks were very vocal on both sides of the coin in private. Not so much in public.
Today the front page looks fine to me. Sometimes it gets a bit vile.
I think the solution moving forward is proper tagging of posts with [NSFW] which I can add to submission titles if users don't do it themselves. If any particular default forum is too heavily NSFW it may be removed as a default forum simply for the fact that newcomers to the site don't always want to be met with that, but they're free to seek it out or post it themselves.
Rambler OP wrote
Reply to Downtime 04-16 / 04-17 by Rambler
We're back up, again. Similar thing. Planned maintenance followed by me needing to be around to unlock the disks so that site is reachable. Full Disk Encryption is a blessing and a curse.