Re: Twitter clients. Re: Read Feeds add-on

Laurie Mehta

Hi Brian and others,
Quoting Brian from his post (below)
"Looking at it selfishly from their revenue point of view, I suppose they have to make money somehow"

Indeed they do. Apart from the fact that it is a for-profit company, they have obligations such as employee salaries, facility and product maintenance, and stuff like that to pay for with the money that ads brings in. (smile)


On Mon, 5/21/18, Brian's Mail list account via Groups.Io <bglists@...> wrote:

Subject: Re: [nvda] Twitter clients. Re: Read Feeds add-on
Date: Monday, May 21, 2018, 11:13 PM

This is th4e second time this has occurred,
of course, they did say they
would delay it for consultation but
really the blind are the  smallest part
of it. Its everyone else they want to
come back to their web site or their
own app. Its very similar to what the
BBC did with the tv I player some
times ago, removing all the metadata
needed to construct the off browser
experience, so the companies making
third party access tools had to resort
to screen scraping which as you can
imagine besides being slower is also
going to mean a new version every time
the web site is changed in any way.
As far as I can tell from what the
various twitter campaigns say is that
Twitter never intended the api to be
use to avoid paid for adverts and
content, as this is how they keep the
platform free for the public.
They have mooted a paid for service
with no adverts, but also from reading
between the lines they can detect ad
blockers and won't let you use the site
with one turned on, if not now but
Looking at it selfishly from their
revenue point of view, I suppose they
have to make money somehow and with the
possibility that in the states the
loss of net neutrality  possibly
meaning sites be paying carriers to not
delay their packets, they are just
minding their backs. as always the
undesired result  of poorer access
for disabled is just collateral damage.

Sent via blueyonder.
Please address personal E-mail to:-
putting 'Brian Gaff'
in the display name field.
----- Original Message -----
From: "Shaun Everiss" <sm.everiss@...>
To: <>
Sent: Monday, May 21, 2018 10:20 PM
Subject: Re: [nvda] Twitter clients.
Re: Read Feeds add-on

> Well someone on one of my forums
has allready got one of those change
> pititions to twitter to stop
breaking it for the blind.
> Since I know these things are only
feel good things and non binding I am
> unsure what the point is.
> I did sign it but then I sign
everything but bar all the extra spam I
> doubt things will change.
> On 5/22/2018 4:11 AM, Travis
Siegel wrote:
>> This link:
>> talks about why they are
discontinuing support for one of their SDK
>> tools. It will still continue
to work, it's just hat twitter themselves
>> won't be contributing to it
>> On the link:
>> you can get details on exactly
what they're charging for, and how much,
>> though it's not laid out in a
straightforward method, you need to select
>> the various features, and
their level to see what the fees are.
>> It actually looks like twitter
has been targeting fee based services for
>> quite some time now. As far
back as 2010, twitter was charging for access
>> to historical data for
researchers, commercial developers who wanted back
>> history, and the like, so this
isn't anything new. Last march, twitter
>> had run a series of surveys,
asking if users would be willing to pay for
>> different components of the
twitter landscape. I didn't find anything
>> breaking down what those
responses were, but it isn't surprising that the
>> questions were being asked.
After all, every company has a need to make
>> money, or they won't remain a
company for very long.
>> But, as far as the impending
charging for access goes:
>> seems to indicate that the
fees for a standard twitter client aren't
>> trivial, and seems to
contradict what I read earlier about clients simply
>> not being able to get realtime
updates. It appears more digging is
>> necessary.
>> Apparently, twitter is trying
to herd users into using official twitter
>> clients only, (or the web
site), but as of now, I can't say whether this
>> is true or not, since there
seems to be more knee jerk reactions to the
>> announcement than actual
facts. I suspect truthful information will
>> slowly filter it's way into
the general populous over the next few
>> months, then we'll know for
sure what the deal is, but for now, just keep
>> using the client of your
choice, and wait until it breaks ... (if it
>> breaks) ... before spreading
possibly untrue information about the
>> change.
>> .

Join { to automatically receive all group messages.