Recent Comments

There is a nice journal explaining what happened to SN. tl;dr - an SSD failed and due to USA Thanksgiving holiday no one got around to looking at the problem for a couple of days. Then it was a few hours to restore from backup.

Any word on what happened to it?

Ha, great minds think alike(?) Came here to say that SN is down right now...
[a different AC]

Pipedot is the past; Pipedot is the present; Pipedot is the future.

SoylentNews is down right now.

Pipedot is eternal! :D

It is now 2025 and the RSS feed still works.
Content from the Articles page is being referenced by search engines - https://pipedot.org/article/

Given the amount of .. unusual.. search results.. that search engines return these days, perhaps they detect this as a viable trustworthy source.

And now it is working again, Feed shows the latest /. stories. Yea!

Hello Bryan,
Still using your nice Feed page, but in the last few days Slashdot has not been updating, the Feed still shows the top story from a few days ago. This could well be something /. changed, but I thought I would -pass it along.
Carguy

And now the most visible member of the staff is leaving according to this. He is also taking his "anti-sock-puppet" and "anti-spam" measures with him. They've seemingly gotten the technical things under control, too bad that was never the worse of their problems.

Testing

The Utah Cookie Wars have officially come to an end as Crumbl has settled its trademark lawsuit with Dirty Dough. The legal battle, which made headlines in the cookie industry, has been resolved, allowing both brands to move forward. For cookie lovers, this means the delicious Crumbl cookies you love will continue to be available, and you can stay up-to-date with their latest flavors on the https://crumblcookiemenu.com/
. Keep checking back for the freshest cookie options and exciting weekly updates!

Tesingt

In this world human beings are doing a fine job of screwing up, it's nice to know this little place is still alive and present!

Thanks for the heads up. The point release for Ubuntu LTS is next week so I've been upgrading things.

Hello Bryan,

In case you haven't seen it, an odd message popped up on my Feed page just now -- at the top of the page:
Deprecated: explode(): Passing null to parameter #2 ($string) of type string is deprecated in /var/pipedot/lib/tools/tools.php on line 2021

The rest of the Feed still works fine, it's a great feature--thanks as always.
- carguy

To be fair, Letsencrypt wildcard renewing over DNS is kinda annoying.

Six-ish months later and the SN drama continues, but SN manages to keep on going. Latest is cert expires and takes a couple of days until one of the valiant volunteers is able to renew it. In parallel, yet another draft of bylaws (#9, I think) is in play, and appears to be one of the last hangups before a change in ownership/management.

Yet more SN drama, an offer to buy out current owners - archived in case of more site damage,
https://web.archive.org/web/20230729022406/https://soylentnews.org/~AudioGuy/journal/15410

Thank you! Works now.

Thanks. The favicon code needed to be rewritten anyway. Should be working better now.

As for The Intercept feed, the code currently has a one-to-one relationship of articles to feeds. This means that if you add the feed for "All" and the feed for "English" then articles will show up in one or the other, but not both. This is unfortunate, since quite a few sites have overlapping feeds like this. Just add the main feed for now...

Hello Bryan,

No idea if you want to keep playing with the Feed page. If so, here's one I just tried that didn't work for me.
Available feeds listed here: https://theintercept.com/feeds/
I tried adding variations of these two and got a handful of error messages,
https://theintercept.com/feed/?lang=en
https://theintercept.com/feed/?mk=fl_is_on_feature_page&mv=1

The final error message was:
Fatal error: Uncaught Error: Class 'Imagick' not found in /var/pipedot/include/image.php:665 Stack trace: #0 /var/pipedot/include/feed.php(265): save_favicon() #1 /var/pipedot/post/user/feed/add.php(39): add_feed() #2 /var/pipedot/www/index.php(128): include('/var/pipedot/po...') #3 {main} thrown in /var/pipedot/include/image.php on line 665

As always, thanks for the Pipe!

Heh, I had actually pre-ordered Diablo 4 a good while back. But now that the game is finally out, I can't seem to bring myself to play it. If I want to play a game I just start another play-through of Oxygen Not Included.

We got a PS4! Right before PS5 came out. Lots of games available on the cheap. We really like Diablo 3, such as it is. Sadly, the box says it comes with the expansion but the game didn't. It's a pity as it looks good. The PS4 has never connected to the internet so I may never play it.

It's a real shame that the PS4 won't backup to an external drive. Looks like it wants internet access first.

Perhaps this was for the best. Game comes out, people finish it, cheaters wreck it, expansion packs get added, and then maybe it's on sale for cheap and playable :)

Yep, working all day.
One site I'd been following hadn't updated in a couple of years (and is now gone from the web). With your update it disappeared from my Feed page.

The Slashdot, Engadget, Gizmodo, SoylentNews, and other feeds should now work again. ExtremeTech is still broken because it downloads using IPv6 by default but their server only likes IPv4. I think...

I'm not entirely convinced about airless tires. I think the expectations might be a bit over inflated.

Ouch!!
Thanks for the complete explanation and good luck squashing that bug.

That's a known bug that I've been meaning to look at. It's not just the slashdot feed but several others as well and it's quite annoying to me too. I'm using a third party library called SimplePie that is supposed to parse the RSS / atom text into usable data, but the library often bombs out instead of returning anything. It's a pain because the fatal error in that library causes the whole feed process to completely stop until cron restarts it again. This causes not only the offending feed to not get data but all other feeds afterwards to halt. Feed parsers are complicated because a lot of sites return malformed data with stray tags all over the place. In an ideal world you could just parse an article with a strict xml parser and everything work! But far too many sites forget to close their html tags or use some invalid unicode strings that cause the parse to fail.

Off topic, not sure where the best place is for this Pipedot & Green Site question?

On my Pipedot Feed page I've had Slashdot for years, always worked fine, used it occasionally. It locked up about two weeks ago and hasn't offered any new stories since then.
https://slashdot.org/faq has some information on Feeds including RSS, which notes:
> Please don't request feeds more than once every 30 minutes.
Any chance that is the problem?
Or maybe the /. RSS feed is broken?

Jesus Christ those people need to just talk to each other.

They are right that NCommander seems to be acting like a dictator by putting up plans with a "my way or the highway" attitude, but rightly or wrongly he and Matt basically are dictators from the legal point of view. They are also right that NCommander has made serious errors technical and socially throughout this process.And they are right that NCommander has done serious damage to the trust and reach of SoylentNews itself.

NCommander is right that the rest of the staff don't seem to have a plan, at least one on the website for all to see. He is also right that technically the site has languished with open vulnerabilities for years and no one stepping up either to work on perl or replace it.

This whole thing is like Mom and Dad fighting and I'm starting to get a feeling that another "beta" divorce is coming.

More SN drama,
SoylentNews PBC Will Formally Continue Operations + Site Overhaul Status
posted by NCommander on Monday June 05, @09:00AM

There is no such setting at the moment, but I'll keep it in mind and may show the IDs again in the future.

Another for the list of "SN future" links up top,
All good things must come to an end...

Speaking of UIDs, where do you see the UIDs? How can we keep the 4-digit UID 'you must be new here' memes going without the UIDs promptly displayed next to our user name? Can you point me to the setting to turn this on?

The blue site could do it this way.

All in all accounts might be the best way to go. We can't have summary account bans. Let the karma system work. We need transparency. Moderation should be public. One account should be able to /ignore mods from another account. Let the usual suspects have their mod wars. The rest of us can /ignore them. Echo chambers might have interest effects, if it's merely a mod echo chamber, so the runaway and khallow see themselves at 50 karma but the rest of us see them at min_karma. All accounts can mod, n number of points per 24 hours. Have them regenerate like some shitty arpg at 1 per 2.4 hours if you don't want to tie yourself to UTC. Tongue in cheek: sell microtransactions to get buffs to mod regen, then the rest of us can mod /ignore him.

Requiring an email address was not effective mitigation for UID inflation caused by so-called aristarchus, so why not just set up a REST endpoint for allocating UIDs?

Public moderation means that when A starts posting at -1, B can know who thought they should post at -1. If C is a mod troll, B can set up a personal mod /ignore for C, revealing A's comments at whatever score the moderators B does trust have determined.

Ya, just tried on gmail and it marked the email as spam. But as soon as I moved that first message out of the spam folder, all further messages went to the inbox.

Thanks so much bryan. I'm amazed I remembered my password. FWIW the forgot password thing didn't work. Not sure if it's not sending emails right now or if it's my email provider shunning them!

I like the Edit function.

I like the blue theme, I guess it would be nice too in a dark mode. :-) .oO( now with an ASCII emoji, as the real ones do not yet work )

Soylent News has had many problems with bad users and gaming the moderation system. Does pipedot aim to have the same free speech values that rely on community moderation? Please elaborate on how you intend to manage the site.

For some reason I can't reply directly, so... just to say glad you're still here. Cuz I didn't forget.

I submitted a story in the pipe: SoylentNews Shutdown
They contacted me briefly, but I'm not sure what their plans are going forward.

kazzie,
The "Notifications" button in PipeDot seems to be working, I received one (1) for your post above.
As well as SN (where I usually post as AC), I've kept a login here since the beginning because of the nice "Feed" page for RSS notifications.

It appears (from posts over there) that initial contact has been made, and this is one of many possibilities being considered.

I've just wandered back here today, and rediscovered that I made an account here two years back when SN had that big server-burp moment. So I'm ready to go if this is the direction the community decides to drift in... :)

You guys are welcome to come over here if you want. I'm not going anywhere.

SN did come back, but currently it looks like June 30 is the end. NCommander's post gives his side of the story.
Saw at least one post about a contact to Bryan (here, Pipedot) about picking up the pieces (and the community), but haven't seen any response or more details.

Yeah baby!

SN not out of the weeds yet, see this thread for a few updates, https://soylentnews.org/~nostyle/journal/12862
Since then the site has been running without various features like mod points, also the regular IRC is still broken.
It doesn't seem like NCommander has done any further maintenance in the last week or so(?)

See comments here for recent repairs https://soylentnews.org/~NCommander/journal/

The shrinking community at SoylentNews.org is suffering from a variety of system problems. And, nearly no one able to work on them.

Anybody read these?

Just some ongoing issues due to using an over-complicated database cluster setup. It'll be back soon, though likely with a few records missing.