Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Proposal to make /tiny provider configurable or remove it #1370

Closed
pmaziere opened this issue Jun 22, 2020 · 9 comments
Closed

Proposal to make /tiny provider configurable or remove it #1370

pmaziere opened this issue Jun 22, 2020 · 9 comments
Assignees
Milestone

Comments

@pmaziere
Copy link
Contributor

The /tiny command sends the URLs to shorten to tinyurl.com, a website whose goal is to gather and sell to third parties its users data as stated in their privacy policy :

We may share aggregated information, Non-Identifying Information and Log Data with third parties for industry analysis and demographic profiling and to deliver targeted advertising about other products and services.

In order to remain neutral according to the service that provides this functionality, the URL shortener feature must propose a mechanism that allows profanity's users to define which third party service to use, how to submit a URL to this service and how to retrieve the shortened URL from this service.

Should this feature be kept, it should propose, as default provider, a libre software based equivalent, preferably instantiated by a non commercial entity.

@jubalh jubalh added this to the 0.10.0 milestone Jun 23, 2020
@jubalh
Copy link
Member

jubalh commented Jun 23, 2020

Personally I would just remove the behaviour. I always thought that this should just be a plugin in the first place.

But now that we have it already, maybe it's best to just alter the behaviour like you suggested:

  • make it configurable so that the user can decide on the service being used
  • use a privacy friendly service by default

@pmaziere
Copy link
Contributor Author

pmaziere commented Jun 23, 2020

I do not use it myself, and I think URL shorteners are something to avoid since it breaks the web once these services are offline.
So, if we could remove it all along, I'll be fine with it:

  • first step: deprecation with a clear and loud message in the window where the shortened link is displayed to let users know that this feature will disappear if someone who cares does not make the necessary changes:
The /tiny command, as currently implemented, is deprecated.
The right way to implement this feature is described here:  https://github.com/profanity-im/profanity/issues/1370
If nobody steps up to develop a plugin according to the requirements linked above, the /tiny command will be definitely removed in next release.
  • second step: if nobody steps up, let's go for full removal

@mdosch
Copy link
Contributor

mdosch commented Jun 23, 2020 via email

@jubalh
Copy link
Member

jubalh commented Jun 23, 2020

What's the use of URL shorteners in XMPP?

I guess the use was the following: Very long lines will be not clickable due to breaking the URL. Probably people used the url shortener so that a short URL is produced so it is more likely to be clickable.

@jubalh jubalh changed the title An online service that sells profanity's users data to third parties should not be forced as default url shortener Make /tiny provider configurable or remove it Jun 25, 2020
@jubalh
Copy link
Member

jubalh commented Jun 25, 2020

We don't need such a dramatic title but what it is actually about ;)

@jubalh jubalh changed the title Make /tiny provider configurable or remove it Propoasl to make /tiny provider configurable or remove it Jun 25, 2020
@jubalh jubalh changed the title Propoasl to make /tiny provider configurable or remove it Proposal to make /tiny provider configurable or remove it Jun 25, 2020
@jubalh
Copy link
Member

jubalh commented Jun 25, 2020

Should this feature be kept, it should propose, as default provider, a libre software based equivalent, preferably instantiated by a non commercial entity.

Like which one?

@wstrm
Copy link
Contributor

wstrm commented Jun 27, 2020

I vote to remove /tiny.

As @pmaziere says:

I do not use it myself, and I think URL shorteners are something to avoid since it breaks the web once these services are offline.

URL shorteners are just bad, even if they do not sell anyone's data. If long URL's are an issue, the application should be improved to handle them in a better way instead.

@mdosch
Copy link
Contributor

mdosch commented Jul 5, 2020

+1 for removing /tiny
If you really, really want shorter URLs and send around URLs which do not tell others where they are leading to than use a tool that can do this and paste the result into profanity.
Profanity itself shouldn't support this behavior of breaking the internet by using URLs which do not indicate where they are leading to and which might be provided by services tracking the user.

@jubalh jubalh self-assigned this Jul 5, 2020
@jubalh
Copy link
Member

jubalh commented Jul 10, 2020

Should this feature be kept, it should propose, as default provider, a libre software based equivalent, preferably instantiated by a non commercial entity.

Which one? I don't find any.

@jubalh jubalh closed this as completed in 3931548 Jul 10, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants