Getting started

[scripting]

The first thing I'd like people to try is logging on to feedland.org.

You should get an error message. This will help me get everyone's twitter accounts in one place.

I will authorize your account and you'll be able to past the authorization list.

Assuming everything works which would be incredibly optimistic. :smile:

[gwthompson]

Got the error as expected. Love the error code number! :)

[scripting]

@gwthompson -- what is the error code number? I must be missing something??

Do you mean No soup for you?

Originally that's all the dialog said.

Also -- http://scripting.com/nosoupforyou/

[gwthompson]

@scripting Here is the error I got when I tried to login to Twitter:

<?xml version='1.0' encoding='UTF-8'?><errors><error code="69">The given URL is considered malware</error></errors>

A bit of juvenile humor on my part.

[scripting]

That's a serious problem and should be reported as such. It's a mess with Twitter. Please no more jokes like that. I was just going to send out an email, and now that I know this is still a problem -- I won't.

[gwthompson]

I apologize.

[scripting]

not necessary. just know that i am not there with you and i can't see what's on your screen. that has to be factored into all communication.

[gwthompson]

I realized that I made an assumption that the error I saw was what you expected but I should have reported it no matter what.

[scripting]

Right. This was and apparently still is a fucked up situation where Twitter server incorrectly thinks that feedland.org is a malware site. I’ve actually been working with the people at Twitter to try to get this fixed, and I thought it was fixed. So you have to always be very careful about reporting what you’re seeing because there’s no way I would’ve assumed this is what you were seeing. And it’s a serious problem, and until it’s fixed on Twitters end we can’t go forward with testing the software. I’ll post another note here when they say it’s fixed and it’s time to try it again. Thanks for working with me on this by the way.

On Friday, July 22, 2022, gwthompson @.***> wrote:

I realized that I made an assumption that the error I saw was what you expected but I should have reported it no matter what.

— Reply to this email directly, view it on GitHub https://github.com/scripting/feedlandSupport/issues/2#issuecomment-1192984455, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAM32O44IVAOM7M274P7RALVVMPLBANCNFSM54MHRZZQ . You are receiving this because you were mentioned.Message ID: @.***>

--

[gwthompson]

My pleasure! I enjoy digging into new software.

[scripting]

Hopefully we'll be moving soon. I may have to work around it again. I've never had to deal with a problem like this before. But there are workarounds even if they can't clear the problem on their end.

It can't hurt to keep trying it every so often to see if the problem has cleared.

[gwthompson]

Will do. I just tried now and got the same exact error.

[scripting]

@gwthompson --

I just tried it again myself, and no luck. I have gotten a response from my friend at Twitter, which is amazing -- they are actually helping me -- something I've never seen them do for developers before. But they can't do anything until Monday.

I was planning on starting testing this weekend, and I could still do it, by changing the domain name, or shuffling around servers, but I decided instead to take it easy this weekend and let the process with Twitter run its course.

In the meantime I'm going to post the text of the first email I was about to send to testers, to give you an idea of what FeedLand is about.

Thanks for your patience.

[gwthompson]

@scripting --

Looking forward to testing and using the product.

Have a great weekend!

[scripting]

I posted the overview here.

https://github.com/scripting/feedlandSupport/blob/main/docs/overview.md

If you have any questions, please ask -- but I may say -- "You'll see soon enough."

[scripting]

@gwthompson -- let's try a new experiment.

1. Go to http://feedland.scripting.com/ and try to login.

2. You should get an error message saying that you are not validated.

3. Report here on the result.

If we pass that test, I will add you to the whitelist and we can get started with the next level.

[gwthompson]

@scripting -- When I tried to login I received this message:

Sorry, @gwthompson is not authorized to use FeedLand.

Was this what you expected?

[scotthansonde]

@scripting I'm following along here too, here's the message I got

[troutcolor]

Not sure if you want logon fails from everybody, but:

Sorry, @johnjohnston is not authorized to use FeedLand.

[scripting]

Ahhh I got three confirmations. Excellent. That was what I wanted confirmation of. That Twitter was letting you through and that the whitelisting system which is new, works. I will now authorize all three of you, with my thanks.

[scripting]

@troutcolor, @gwthompson, @scotthansonde --

I have authorized the three of you, so try logging on again.

    "whitelist": [
        "davewiner",
        "cluelessnewbie",
        "johnjohnston",
        "ScottHansonDE",
        "gwthompson"
    ]

Once inside, the first thing to do is to choose "Add a few feeds" from the testing menu.

Then read the overview if you haven't already. Once I have a few more people signed on, I'll start writing explainers.

Dave

[mterenzio]

I'm still seeing:

<?xml version='1.0' encoding='UTF-8'?>The given URL is considered malware

I attempted with numerous browsers and in private windows. Also tried from my mobile phone which connecting via a different internet connection.

On Mon, Jul 25, 2022 at 10:37 AM Dave Winer @.***> wrote:

Ahhh I got three confirmations. Excellent. That was what I wanted confirmation of. That Twitter was letting you through and that the whitelisting system which is new, works. I will now authorize all three of you, with my thanks.

— Reply to this email directly, view it on GitHub https://github.com/scripting/feedlandSupport/issues/2#issuecomment-1194135286, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAAAWDRCPDWOYA3IHNGC2KTVV2RBFANCNFSM54MHRZZQ . You are receiving this because you are subscribed to this thread.Message ID: @.***>

[scripting]

@mterenzio -- you have to read the instructions.

[scripting]

This is what I did this morning.

1. I left feedland.org where it is, unchanged, so the Twitter people would have something to test with.

2. I set up a new server, feedland.scripting.com, which is running the same software. I am able to do this relatively easily because all the data for the app, except for user prefs, are stored in a SQL database. My software can access the database from anywhere.

3. Then, in today's instructions I said to go to http://feedland.scripting.com -- I guess Matt didn't see this?

4. The reason this works is that Twitter's problem was with the domain and this is a different domain, one which presumably it knows well enough to let us proceed.

5. Meanwhile the original server is where it was, and hopefully will get this problem cured.

Anyway if you all get through, and get a chance to look around, I'd love to hear what you think. Not of the fit and finish of the software, but the overall concept of feeds and people.

[scripting]

I was looking for proof of life and here it is --

Note how the number of subscribers is now greater than 1.

For months all I've been seeing is 1. ;-)

[mterenzio]

Gotcha. Authentication for http://feedland.scripting.com looks like it worked for me

On Mon, Jul 25, 2022 at 10:58 AM Dave Winer @.***> wrote:

This is what I did this morning.

1.

I left feedland.org where it is, unchanged, so the Twitter people would have something to test with. 2.

I set up a new server, feedland.scripting.com, which is running the same software. I am able to do this relatively easily because all the data for the app, except for user prefs, are stored in a SQL database. You can access the database from anywhere. 3.

Then, in today's instructions I said to go to http://feedland.scripting.com -- I guess Matt didn't see this? 4.

The reason this works is that Twitter's problem was with the domain and this is a different domain, one which presumably it knows well enough to let us proceed. 5.

Meanwhile the original server is where it was, and hopefully will get this problem cured.

Anyway if you all get through, and get a chance to look around, I'd love to hear what you think. Not of the fit and finish of the software, but the overall concept of feeds and people.

— Reply to this email directly, view it on GitHub https://github.com/scripting/feedlandSupport/issues/2#issuecomment-1194162365, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAAAWDVAE7ENQ4IESW5HMCDVV2TPVANCNFSM54MHRZZQ . You are receiving this because you were mentioned.Message ID: @.***>

[scripting]

Things to look at.

1. My feedlist: http://feedland.scripting.com/?username=davewiner

2. You can hover over the green Info icon in each row or you can click on it to get more info, and to see who else is subscribed. The UI on this will evolve.

[scripting]

@mterenzio -- i just added you to the list, so you should be able to login now.

[mistersugar]

I received the message: Sorry, @mistersugar is not authorized to use FeedLand.

---

Anton Zuiker 919.923.9491

Blogging again at zuiker.com

On Mon, Jul 25, 2022 at 11:12 AM Dave Winer @.***> wrote:

@mterenzio https://github.com/mterenzio -- i just added you to the list, so you should be able to login now.

— Reply to this email directly, view it on GitHub https://github.com/scripting/feedlandSupport/issues/2#issuecomment-1194180962, or unsubscribe https://github.com/notifications/unsubscribe-auth/AA5LBHLJEPJDFOGZBHWZCKTVV2VFFANCNFSM54MHRZZQ . You are receiving this because you are subscribed to this thread.Message ID: @.***>

[scripting]

Here's another milestone. A feed wasn't added by me. But there appears to be a problem. When I look at his feed list, I don't see an unchecked feed. But a whole bunch of stuff was just validated, so that's progress. Basically everything that you do right now that works is important. I don't think I've ever tested so much fresh code for the first time in one shot.

[troutcolor]

Hi, I’ve added a few feeds both from rss and from others. AOK so far. not tried adding an opml list yet. I’ll make a wee one and try than.
I do like the “reader” view. Plain sailing so far👍

[scripting]

@mistersugar -- I added your twitter account to the list.

[scripting]

IMPORTANT -- I verified that the checkboxes aren't working properly.

This is an important feature. I wrote about it a long time ago --

http://scripting.com/stories/2007/04/23/tvNewsOfTheFuture.html

Fixing this is a high priority, since it seems that overall the software seems to be working. :smile:

[mistersugar]

Thank you.

Bug report below:

I added 2 feeds. I saw both in my subs list. I clicked on one of the titles (Without Bullshit) to see the reader view. I clicked Feedland to return to my list and the list is empty, that is both feeds I had added are no longer there. I added a new feed, waited for info to come up, then clicked Menu > View My Feeds, and I see only the one listed. I clicked on that feed, saw the reader view, clicked back to my list and the one title is there as expected.

I am using Vivaldi browser on Mac. I did not have the console open but will keep it open to watch for future error messages.

---

Anton Zuiker 919.923.9491

Blogging again at zuiker.com

On Mon, Jul 25, 2022 at 11:34 AM Dave Winer @.***> wrote:

@mistersugar https://github.com/mistersugar -- I added your twitter account to the list.

— Reply to this email directly, view it on GitHub https://github.com/scripting/feedlandSupport/issues/2#issuecomment-1194217559, or unsubscribe https://github.com/notifications/unsubscribe-auth/AA5LBHNAAPZX3QQLIGQFATLVV2XYBANCNFSM54MHRZZQ . You are receiving this because you were mentioned.Message ID: @.***>

[mistersugar]

Just remembered I had clicked one other link somewhere in that process: View Hotlist, for which I got the modal saying it is not available yet.

---

Anton Zuiker 919.923.9491

Blogging again at zuiker.com

On Mon, Jul 25, 2022 at 11:49 AM Anton Zuiker @.***> wrote:

Thank you.

Bug report below:

I added 2 feeds. I saw both in my subs list. I clicked on one of the titles (Without Bullshit) to see the reader view. I clicked Feedland to return to my list and the list is empty, that is both feeds I had added are no longer there. I added a new feed, waited for info to come up, then clicked Menu > View My Feeds, and I see only the one listed. I clicked on that feed, saw the reader view, clicked back to my list and the one title is there as expected.

I am using Vivaldi browser on Mac. I did not have the console open but will keep it open to watch for future error messages.

---

Anton Zuiker 919.923.9491

Blogging again at zuiker.com

On Mon, Jul 25, 2022 at 11:34 AM Dave Winer @.***> wrote:

@mistersugar https://github.com/mistersugar -- I added your twitter account to the list.

— Reply to this email directly, view it on GitHub https://github.com/scripting/feedlandSupport/issues/2#issuecomment-1194217559, or unsubscribe https://github.com/notifications/unsubscribe-auth/AA5LBHNAAPZX3QQLIGQFATLVV2XYBANCNFSM54MHRZZQ . You are receiving this because you were mentioned.Message ID: @.***>

[troutcolor]

Hi, I added a wee opml file, just 5 feeds. It work. But the first time I added it the dialog said 0 of 5 feeds added, I though that was a problem so hit cancel. I tried again and this time I waited long enough for it to could the feeds as they were added. I wonder if it would help for the dialog to read. Adding feeds... 0 of 5 feeds added, ect for folk like me who are too quick on the cancel button!

[scripting]

Checkbox news in FeedLand

I fixed the checkboxes. Here's a screen shot of what I see when I look at John's feedlist.

The feeds that are checked are the ones I am already subscribed to. To unsub, I just click on the checkbox as you would expect. The effect is instantaneous. No confirmation, no Save button. It just happens.

[gwthompson]

Here is what I just saw regarding the checkboxes:

1. In my list of feeds I unchecked one assuming it would be removed from my list at some point either immediately or on the next refresh.
2. Left the browser sitting on my feeds page and about 60-90 seconds the feed I had unchecked was rechecked so I assumed it was still part of my feed list.
3. Viewed one of my other feeds in the "email" view.
4. Returned to my feed list.
5. The feed that I had unchecked and then was rechecked was now removed from my list.

[scripting]

Everyone -- wait a while before reporting bugs.

I'm going to find the big ones on my own a lot faster than you will, and I have excellent diagnostic tools.

This is a community product, and this is the first time I've been able to debug its community-ness.

So everyone hold on to the bug reports. Just use it, try to understand the philosophy of the product.

[scripting]

Suggestion -- use it as a feed reader.

After a few days, does it work?

[scotthansonde]

I just tried out http://feedland.org and now Twitter lets me authenticate. I then got the message "Sorry, @ScottHansonDE is not authorized to use FeedLand."

https://user-images.githubusercontent.com/8681117/183240939-780229c2-2fd6-44b1-83cb-630c9c7d0c7d.mp4

[scripting]

Twitter fixed the problem with feedland.org, but as you can see I haven’t done the work yet to make it usable as a replacement for feedland.scripting.com.

[scripting]

@scotthansonde -- thanks for this report. To everyone else this is a fantastic report. I couldn't ask for better info, since in this case I am there with him.

Okay -- this is a very tricky situation. In theory I should just be able to redirect from feedland.scripting.com to feedland.org and that's it, we say goodbye to the interim domain. I have been keeping both servers updated, again in theory. But you found the exception, and according to Murphy's Law there are probably others. This is going to be hard to test.

Scott, if you want to be the guinea pig, go ahead and start using feedland.org. I authorized your account. The only feature you will not get, for now, is instant updates. You'll have to reload your lists pages and rivers to see the new items. This probably isn't that much of a hardship. I can only have one server doing the live updates, and for now that's the one we've been using.

I don't know how we'll find any problems -- but don't assume any problems you see are a result of using the different server. While it's likely there are problems, it's unlikely that you, from a user's perspective, will be able to tell that.

But if you're able to use it normally, then I'll feel more confident in switching myself, and then switching everyone. Let me know if you're willing to be the test case.

[scotthansonde]

@scripting Sure, I can try using feedland.org. However, it seems I'm not yet authorized. I still get the message "Sorry, @scotthansonde is not authorized to use FeedLand." after authenticating with Twitter.

[scripting]

@scotthansonde -- please try again and let me know if it works now. ;-)

[scotthansonde]

@scripting Yes, it works now, and my feeds on feedland.org are the same as on feedland.scripting.com (including changes I had made this morning). 😃

[scripting]

@scotthansonde -- it's almost like magic isn't it. the only thing you won't get are the realtime updates, otherwise it should behave exactly as if you were using feedland.scripting.com.

Actually there is one other difference -- the prefs won't carry across either. but we aren't using the prefs for much yet.

[scotthansonde]

@scripting It is magic! Changes made on one server show up immediately on the other.