Green Site, Red Site, Blue Site (Score: 3, Informative) by bryan@pipedot.org on 2023-05-23 23:33 (#6BWB6) You guys are welcome to come over here if you want. I'm not going anywhere. Re: Green Site, Red Site, Blue Site (Score: 1, Informative) by Anonymous Coward on 2023-06-06 02:46 (#6C2M9) More SN drama,SoylentNews PBC Will Formally Continue Operations + Site Overhaul Statusposted by NCommander on Monday June 05, @09:00AM Re: Green Site, Red Site, Blue Site (Score: 1, Interesting) by Anonymous Coward on 2023-06-06 06:43 (#6C2PM) 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. Re: Green Site, Red Site, Blue Site (Score: 1) by carguy@pipedot.org on 2023-06-14 20:30 (#6C6S8) 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? Re: Green Site, Red Site, Blue Site (Score: 1) by bryan@pipedot.org on 2023-06-15 17:59 (#6C77W) 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. Re: Green Site, Red Site, Blue Site (Score: 1) by carguy@pipedot.org on 2023-06-16 03:46 (#6C7F0) Ouch!!Thanks for the complete explanation and good luck squashing that bug.
Re: Green Site, Red Site, Blue Site (Score: 1, Informative) by Anonymous Coward on 2023-06-06 02:46 (#6C2M9) More SN drama,SoylentNews PBC Will Formally Continue Operations + Site Overhaul Statusposted by NCommander on Monday June 05, @09:00AM Re: Green Site, Red Site, Blue Site (Score: 1, Interesting) by Anonymous Coward on 2023-06-06 06:43 (#6C2PM) 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. Re: Green Site, Red Site, Blue Site (Score: 1) by carguy@pipedot.org on 2023-06-14 20:30 (#6C6S8) 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? Re: Green Site, Red Site, Blue Site (Score: 1) by bryan@pipedot.org on 2023-06-15 17:59 (#6C77W) 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. Re: Green Site, Red Site, Blue Site (Score: 1) by carguy@pipedot.org on 2023-06-16 03:46 (#6C7F0) Ouch!!Thanks for the complete explanation and good luck squashing that bug.
Re: Green Site, Red Site, Blue Site (Score: 1, Interesting) by Anonymous Coward on 2023-06-06 06:43 (#6C2PM) 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. Re: Green Site, Red Site, Blue Site (Score: 1) by carguy@pipedot.org on 2023-06-14 20:30 (#6C6S8) 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? Re: Green Site, Red Site, Blue Site (Score: 1) by bryan@pipedot.org on 2023-06-15 17:59 (#6C77W) 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. Re: Green Site, Red Site, Blue Site (Score: 1) by carguy@pipedot.org on 2023-06-16 03:46 (#6C7F0) Ouch!!Thanks for the complete explanation and good luck squashing that bug.
Re: Green Site, Red Site, Blue Site (Score: 1) by carguy@pipedot.org on 2023-06-14 20:30 (#6C6S8) 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? Re: Green Site, Red Site, Blue Site (Score: 1) by bryan@pipedot.org on 2023-06-15 17:59 (#6C77W) 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. Re: Green Site, Red Site, Blue Site (Score: 1) by carguy@pipedot.org on 2023-06-16 03:46 (#6C7F0) Ouch!!Thanks for the complete explanation and good luck squashing that bug.
Re: Green Site, Red Site, Blue Site (Score: 1) by bryan@pipedot.org on 2023-06-15 17:59 (#6C77W) 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. Re: Green Site, Red Site, Blue Site (Score: 1) by carguy@pipedot.org on 2023-06-16 03:46 (#6C7F0) Ouch!!Thanks for the complete explanation and good luck squashing that bug.
Re: Green Site, Red Site, Blue Site (Score: 1) by carguy@pipedot.org on 2023-06-16 03:46 (#6C7F0) Ouch!!Thanks for the complete explanation and good luck squashing that bug.