pjd3 🇨🇦 @pjd3@nalocal519.social

@coldacid

@coldacid "One of them, Nova Scotia’s Alexander Macdonald, was even ordered into quarantine despite the fact that he had never technically left Canada. Macdonald had been rejected at the U.S. border in July and immediately sent back to the Canadian side." 🙄

@Effortless@noagendasocial.com Which leads to stories like this:

Government exploring options to increase security for ministers after Freeland confronted in Alberta

Source: https://nationalpost.com/news/politics/government-exploring-options-to-increase-security-for-ministers-after-freeland-confronted-in-alberta

"Mendicino said he was concerned about the level of safety for all politicians and said everything was on the table."

@NAcroutonprivaterobotdistrict@noagendasocial.com Who knows? But they want you to ask the app what your supposed to do when you enter Canada 🙄

@NAcroutonprivaterobotdistrict@noagendasocial.com Here is a video with upbeat music to help answer your question: https://youtu.be/h5kmfVnrSoo

@Genen "If I do get Killary-ed I'm very glad that I have epic will to protect me..." 🙄

@adam @darrenoneill @Genen Adam thank you for adding the CDATA sections to the XML file, this really helps me a lot.

I'm experimenting with creating a shell script to remove the one enclosure tag that is causing the DoggCatcher application to fail. Currently the developer isn’t planning on updating the application to address this or any other issues.🙁

@adam @darrenoneill This is interesting when the XML file is hosted on Adam’s server Firefox parses it fine, but when it hosted on my server it has parsing errors.

@adam @darrenoneill Digging further into the application issue and it appears that it's failing to parse the rss/channel/podcast:liveItem/enclosure/@url element which was added in early June. Not sure if changes were made to the feed but it parses in Firefox now.

@adam @darrenoneill

@adam @darrenoneill If we put aside Dogcatcher for the moment, in my testing both the parser from w3.org and Firefox flag issues in the XML as well. The ampersand is a special character in the XML spec and should avoided. The other change is a minor change to the root element which I would be glad to share.

@adam @darrenoneill @Genen I've found a solution to the problem that will allow the application to work with only minor changes to the feed's XML file.
1. Declare the itunes and podcast name spaces in the root tag.
2. Replace all uses of the ampersand character with word and.
3. Replace all uses on &ndsp; with and actual space character.
With these changes the XML will validate correctly and the application work again. I've tested this solution by hosting the feed's XML file myself.