Tumblr is virtually dead

[Like Ra]

Interesting threads:

https://piunikaweb.com/2018/12/18/is-the...e-reviews/
https://piunikaweb.com/2018/11/16/users-...umblr-app/



Today I discovered that my tumblr was flagged as adult, and some clearly non-adult images were labeled as "inappropriate". I appealed, and this is the result:

Hello likera,

We’ve reviewed the classification appeal on your post and have determined that it does not contain adult content per our Community Guidelines.

As a result, your post has now been restored!

We apologize for the error but know that you’re helping to make these kinds of mistakes happen less often.

[Like Ra]

And my tumblr is unlocked now. Not bad... Now I need to find a way to unlock the RSS streams from the locked pages...

Now here's another interesting thing - far from being a porn free, vanilla only site it seems that Tumblr is still a reasonable source of fetish fun.

Yes, some posters have moved away to other sites, but the feed from many I  'follow' is still very active (or maybe I'm vanilla compared to the ones who incurred Tumblr's wrath?).

The one thing I have noticed are more adverts - now call me a cynic, but....  😋


MJ

[Like Ra]

I read somewhere, that Tumblr made an exception for FeedBurner, but it's not working - just tried. Trying other things with curl (a good opportunity to learn how it works and what it can 😊 ).

The one thing I have noticed are more adverts

Ads? Never seen any on tumblr... Seriously... Ah, I use Firefox wit AdBlock 😁

far from being a porn free, vanilla only site it seems that Tumblr is still a reasonable source of fetish fun.

The pron is still there, but hidden behind various confirmation walls. The problem is to get a direct access to the content. Even saving and resharing is very tricky.

[Like Ra]

Whatever I'm trying I'm getting:

Code:

error:14094410:SSL routines:ssl3_read_bytes:sslv3 alert handshake failure

😟

OK, let's leave it for the moment.

Whatever I'm trying I'm getting:

Code:

error:14094410:SSL routines:ssl3_read_bytes:sslv3 alert handshake failure

😟

OK, let's leave it for the moment.

is that error-message from curl? You might have luck with exporting the certificate in your browser and either add it to your local keystore or use curl's --cacert option with the exported cert...

[Like Ra]

You might have luck with exporting the certificate in your browser and either add it to your local keystore or use curl's --cacert option with the exported cert...

Yes, tried that as well. This is the command from my last attempt:

Code:

curl -i -v --cacert cacert.pem --resolve restricted-senses.tumblr.com:443:66.6.32.21 --tlsv1.2 --ciphers TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 --tlsuser Myusername --tlspassword mypassword -I -L  --user-agent "FeedBurner/1.0 (http://www.FeedBurner.com)" https://restricted-senses.tumblr.com/rss

As you can see, I've tried pretty much everything, including SNI 😁

I’m not much on IT code, but I think your missing something.
I wish I could point it out, but I’m an old coder, but it looks like that a command is missing somewhere in the stream. Is it possible to backtrack and see where in the stream the code dies?

[Like Ra]

where in the stream the code dies?

In the TLS negotiation, as far as I understand. The whole output:

Code:

* Added restricted-senses.tumblr.com:443:66.6.32.21 to DNS cache
* Hostname restricted-senses.tumblr.com was found in DNS cache
*   Trying 66.6.32.21...
* TCP_NODELAY set
* Connected to restricted-senses.tumblr.com (66.6.32.21) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* Cipher selection: TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
* Using TLS-SRP username: Myusername
* successfully set certificate verify locations:
*   CAfile: cacert.pem
  CApath: /etc/ssl/certs
* (304) (OUT), TLS handshake, Client hello (1):
* (304) (IN), TLS alert, Server hello (2):
* error:14094410:SSL routines:ssl3_read_bytes:sslv3 alert handshake failure
* stopped the pause stream!
* Closing connection 0
curl: (35) error:14094410:SSL routines:ssl3_read_bytes:sslv3 alert handshake failure

Also, for some reason it keeps complaining about SSLv3, which is even not supported, and despite TLSv1.2 is explicitly requested.

So it thinks SSLv3 is there, and it wants or demands TLSv1.2 even it’s there.
Can’t you add a file or a subroutine/Micro that would fit somewhere so that the requirements would be met?
Like I said, I’m not an IT guy, but if the program wants something that doesn’t exist, write a routine that will provide the file when requested?