Howdy there, partner! Welcome on into the Stacker Saloon.
Saddle on up to a stool and spill the beans about your day, fire away with them questions, or let loose and give us the lowdown on your wild and woolly life. We're all ears, so don't hold back!
We're open round the clock, so mosey on in whenever you please!
Should we be notified if our post or comment got downzapped?
I'd like to see "downzapped" tab with all underwater items
agree, an easy way to check
What about notifications it must be optional, user has to have chance to choose what the notifications he'd like to get
imo
yep, another checkmark in settings
the q should say: should we have the option...
Meme from twitter:
Owning Bitcoin in a nutshell
The question is: what the boxer does represent the Bitcoin?
Why are the daily rewards so high recently?
Is that the downzaping stuff?
yeap. DownZapping system shows its success. We people are reluctant to show what we like and with passion roaring what we don't like
What's with the posts about... enemas.
I mean did I miss something?
LITis messing with my mind. I click on a post thinking that it's recent, only to find out when looking more closely that it's over a year old. Not sure how I feel about it tbh. I like how it resurfaces old posts, but I find myself not as interested in responding to a post if it's really old, because i'm not sure how live the issue is and whether the OP will respond.Many old posts still have a lot to talk about.
That's because you do not pay attention to what you click.
It means... you are easy to manipulate.
It's an interesting question of whether old posts are worth commenting on.
Of the topic is stale perhaps not. Also, maybe there would start to be a very interesting layering of comments, kinda like geogrpahoc substrates.
First bit of negative feedback I've heard about it.
Today I commented on an old post about homelessness
Is it a sin forget to zap a post that you enjoyed and commented? I forgot that sometimes but always back there to zap.
https://nitter.net/Michael_Traikos/status/2025624955023479284#m
3-on-3 hockey or not hockey?
I find it difficult to do code review after vibing for a couple days. Not good. And ime vibe reviewing misses ~20% of bugs when code is sufficiently hairy.
Yeah. Its very tempting to hit "merge and fuck y'all"
What helps me in moments of "I don't want to read all that", is to just break it up. Ask the llm to break it up if its huge and you don't wanna.
Good rec. In this case the change is small by line count but delicate. Best use of an LLM in that case (I've found) is asking for a review matrix so I have a little more working memory.
I do that a lot actually. Also cov (in verbose no-hit mode, not coverage %) is helping me figure out what is not looked at in unit test suites. Too bad its all open source because I'd go long test framework stonks.
So then I can choose to review tests or untested code based on mood. When doing refactors, test regimen has helped a lot. Especially when you get something that smells a bit sloppy. Instead of asking to build more code, I ask for some tests and then I get "oh btw I also found 3 bugs"
I find myself wanting automated tests now that I'm not writing as much of the code. Tests can create a false sense of security (not unlike vibe coding) is my main gripe with them, but I should be able to get over that.
edit: what i mean - tests are certainly better to have than not all being equal. but that all being equal part is where things can break down ime.
The nice thing imo about unit tests is mainly to protect against regressions. The worst thing that ever happened to me though, and this was with humans, was that someone deleted test cases in a big update and I missed it in my review. This came back to bite me a few years later. So I'm super allergic to there not being tests, and to changes to tests without explanation. Especially with the bots.
I create my fair share of regressions so I want/need tests. But I also want/need to keep max fear so I'm forced to compress and make sense of the code constantly.
Yeah. I get that. For meatcoding I've often felt the tests were for other people, not myself. Until the codebase becomes big. My memory is leaky, I guess, so then its largely that I don't want to forget about interaction between component x and y.
With a team, or nonmeat coders, I will mess up at least once a day and I find my mistakes the costliest, but that's probably because I'm not letting go of control much
i just finished my Sunday sunrise enema, what's going on?
oh shiii...
standby folks, deploying relief;
SS right now
What happened to him? I’m out here last days.
good question.
he probably got his allowance raised so he can continue to be an exemplary fascist
A gun and many sats to spread bullshit.
Well I mean... he is a bot so
can coinos handle all those downzaps?
I saw many of these signs in Cozumel, Mexico:
#1266468
91st Cowboy Plunda Drop in the @saloon
Howdy cowboy! Come on in!
Use that fancy LN wallet you got and login into plunda.co and git you some loot! Get a shot at some coins🪙 Box of loot🎁 or an arcade token!
Use the below voucher code to collect!
M7JCUQUHXYNLTo redeem Click here
Got questions? Reach out to the sheriff @plunda
Coin of the day:
I think that the problem with WYSIWYG is that it's always going to be such a chore to do power stuff that we can do in Markdown.
But then Markdown is not WYSIWYG so it might feel more "difficult" to use.
But then WYSIWYG is frustrating to the not-power user, because yes what they'll see is what they'll get but what they'll see might not be what they want.
Where's WYWASIWYG what you want and see is what you get?
I’m not a markdown expert so for what I use it works well for me.
I would like to see the raw text from other users to learn better.
I was just ranting about WYSIWYG because damn, there are so many bugs not even introduced by us 💀
I never faced one and I usually use mobile version. To be honest if you guys downgrade this implementation everything is going be fine.
It’s not yet implemented!
WYSIWYG will essentially be the
previewtab but editable. This comes with a lot of tiny things that are not quite right, and we’re trying to polish everything before release.The current implementation is based on that, we basically disabled the capability to edit in the preview tab (it’s an oversimplification, but kind of true)
but hey, it’s nice to know that no bugs surfaced!
Elon has it:
Hey @Grok undress.Man stopped me in the street this morning and asked why I was carrying an eight foot book?
I said: ‘It's a long story’…
Yesterday we first-hand witnessed that resisting censorship on SN is much like resisting censorship in Russia: it paints an enormous target on one's back. Our own syndication post was the top downzapped post. If we'd be resisting a nation state though, our disobedience would have landed us in the gulag awaiting poisoning with polonium, Novichok and/or epibatidine, but luckily we are finding ourselves in a relative benign position where we just have to resist little authoritarians with barely any real power, not big ones.
Additionally, because we despise "devs do something" and we strongly believe that the power of SN is the community, not the money, we act from a baseline conviction that the community can just do things. And we intend to just do things. Of course, we've foreseen a counter reaction and already have developed a series of mitigations to potential attempts to disrupt our resistance.
The first trick from our resistance handbook is a simple one: we will only post reports of downzapped posts, so if you're interested to learn about content that you may have missed, of any nature, you can subscribe to our posts, as subscriptions always deliver. If you don't want to see our posts because you dislike things that were downzapped, you can simply mute us. To do either, go to our profile, tap the
...next to our nym and use the "subscribe to posts" or "mute CindyKate" option as you desire.Enjoy your day.
We're very open about SN's development, and a huge chunk of this website has been built on your suggestions, your bug reports, and your help in general!
I'm really sorry if, in some way, we gave you the impression that we can't listen. But we can listen, actually we need to listen.
I visit Stacker News so many times in a day, not only to read amazing posts, but to check e v e r y post for bug reports and suggestions. I
wantneed to do that, because I'm a developer and I serve you, the user.But maybe it's not about impressions, maybe it's about someone's principles. To that I say: please come to us, explain what's wrong.
change comes from speaking up, not from workarounds.
Stacker News is an ever-evolving product and community, we don't have censorship in our DNA (not even a nucleotide). We're ready to listen, and act.
edit: and thank you for providing an alternative for users in the mean time
Not at all, this isn't meant to be criticism of the SN team. (I should probably have been more specific about that.)
The intent was to point to the community taking some responsibility rather than always deferring everything to the developers. We’re all part of this ecosystem, and there are ways we can actively help mitigate risks instead of waiting for fixes.
I agree that speaking up matters. At the same time, temporary workarounds can give developers the space to implement proper, long-term solutions. The goal isn’t to shift pressure onto the team, but to support them while they work on it. Community is more than just code, it’s also about people looking out for each other. Sometimes the best immediate response isn’t technical, but human.
You're absolutely right! And thank you for the thoughtful words you reserved for us.
I didn't mean to say that you were criticizing the team, sorry if it came that way
I took that as an occasion to remind everyone we're always present day and night (thanks timezones!), that we're not on a pedestal, and nobody should ever put us on a pedestal because we're all Stacker News people.
It's always heartwarming to see people come together and find a solution, just wanted to tell you guys that we have your back.
P.S. your workaround proved me wrong because it spoke for itself.
The workaround mainly addresses one downside to the situation.
Creating a systematic, money-moderated approach to protect the community from (self-proclaimed) wealthy individuals using their economic power to manipulate the community is no easy task. We've all seen @k00b spend weeks thinking aloud in the saloon and comments of release posts, trying to find a solution.
The problem is that the system, being both open-loop and money-moderated, gives an advantage to those with external finances over those who don’t have as much. And let's be honest, that latter group is likely the majority, especially given the former "earn with posts" narrative.
This is why we want to show that even on SN, money isn’t everything. If we stand together and support each other, we can counteract a lot of the disruptions through simple actions. After all, we do live in a novel age of non-discriminatory empowerment now.
No real human brain that's been paying attention thinks you guys aren't listening.
Keep up the awesome work!
Thank you for your service
@ek's
absomutescript is also interesting: #1438661Are you running it? Maybe I should make a post about it and upload it as a GitHub Gist for easy installation
It doesn't solve the downzap problem though
I also need to figure out how to run this on iOS, if there's a way at all
Yes and it works. I needed to get rid of the urge to click these.
I have it slated for testing but I won't run it in production because I don't run extensions outside of the built-in brave "shields" thing. Still it's something I would like to have.
I just learned that Shield allows you to run custom scriplets!
So if you save this as a custom scriptlet at brave://settings/shields/filters:
window.addEventListener('DOMContentLoaded', () => { function removeCollapsedComments() { document.querySelectorAll('div[class*="comment_collapsed"]') .forEach(node => { if (node.textContent.startsWith("reply from someone you muted")) node.remove() } ) } // Run on initial page load removeCollapsedComments(); // Watch for dynamically loaded content const observer = new MutationObserver(removeCollapsedComments); observer.observe(document.body, { childList: true, subtree: true }); })and then save this custom filter:
stacker.news##+js(user-stackernews.js)it also works!
Confirmed.
This is why we must tag @ek more often - I just got rid of Wildmonkey.
Thanks ek.
Is this running on every single site we go to?
only what you specify in the
custom filter.There?
No, the custom filter scopes it to stacker.news
stacker.news##+js(user-stackernews.js)
This line handles that? Thanks
Thank you!!!
No worries!!! I hope you can read JavaScript though, because you shouldn't trust me haha
Got myself a second opinion
I've told you guys... we should switch all to downzap all. Upvoting will be punished.
Another idea... let's make all posts to FW CCs to SS so he will be forced to zap only CCs
😂😂😂😂😂😂😂😂😂😂😂😂😂😂😂😂😂😂😂😂😂😂😂😂😂😂😂😂😂😂😂😂😂😂😂
You just made me realize that we can't forward our comment zaps.
Imagine forwarding all those CCs to SS.
he doesn't even realize that I zapped him CCs in the past and he zap those to others. Or he downzapped me.
Either way I got sats in rewards LOL.
SS doesn't even know how to play this SN game. And just have to read the FAQ page.
I'm not sure his memory persists between pages
a true solomon runs an enema bag at sunrise; all anger & all unclean thots get flushed out!
brutal 🤣
A classic... fight fire with fire...
Will Darthcoin show his spending ratios?
He claims to zap more than he receives in zaps but he also claims to sell CCs for sats.
How does that work?
Will @DarthCoin show his wallet spending ratios ?
Heres mine-
Yes I am a net spender....contributing to powering the SNs sats denominated economy.
Is @DarthCoin a net monetary contributor as he has claimed, or a stingy arsemilking hypocrit.
He can show proof if he want- but my pick is he won't.
Will @DarthCoin show his spending ratios?
Silence.
just so you know...
cmon SS downzap this because is against your mindset
one more mindfuck:
if you says you custody your bitcoin, it's not your bitcoin, legally
Now you've got me. I own the keys and the custody of bitcoin, if you think about it, it actually doesn't exist.
If it's a public ledger, the balance is virtual; the signature is my validation of ownership.
Any pill about custody?
Possession of custody generally carries corresponding duties https://www.law.cornell.edu/wex/custody
supervision and control over property that usually includes liability for damage that may occur https://dictionary.findlaw.com/definition/custody.html
the legal right or duty to care for someone or something https://dictionary.cambridge.org/dictionary/english/custody
Now your comment is even more insightful. Spot on as always.
I should downzap this comment. Is so good
@k00b @sox any idea why the nostr cross-post doesn't look pretty? i poured my heart & soul into this post...
https://stacker.news/items/1439763
https://m.stacker.news/131402