TNY network https://i.tny.im The home of the TNY network Sat, 12 Jun 2021 21:23:46 +0000 en-US hourly 1 https://wordpress.org/?v=6.4.3 New status page https://i.tny.im/?p=660 https://i.tny.im/?p=660#respond Sat, 12 Jun 2021 21:23:46 +0000 https://i.tny.im/?p=660 Continue reading

]]>
After some hiccups with the old Cachet-powered status page, we are happy to present the new TNY network status page, which can be accessed at the same address: https://status.tny.im/

In addition to manually-filled incident reports and announcements, the new Statping-powered status page shows the live status of each service as automatically monitored by Statping. This should improve the accuracy and currentness of the reported information. It also provides detailed statistics about the response time for each service as well as visualizations of past unavailability periods.

As with the previous status page, this one is hosted in a completely independent system, logically and physically distant from the rest of our services (alas, maybe one day there will be sufficient budget for it to have its own top-level domain as well…)

]]>
https://i.tny.im/?feed=rss2&p=660 0
TNY network not affected by Cloudflare security incident https://i.tny.im/?p=642 https://i.tny.im/?p=642#respond Fri, 24 Feb 2017 19:27:59 +0000 https://i.tny.im/?p=642 Continue reading

]]>
A few days ago, Cloudflare reverse proxies were found to be leaking personally-identifiable information contained in requests handled by these proxies, into the data of other requests going through them, provided these other requests met certain conditions. This information included cookies, passwords, authentication tokens and encryption keys, and to make matters worse, it had already been cached by multiple systems, including Google’s web cache. See the Google’s Project Zero report, and also Cloudflare’s blog response. People have also compiled lists of websites that might be affected.

We use Cloudflare’s DNS hosting service on some of our websites. However, these are not directly affected by this security problem, because we never used Cloudflare’s reverse proxy features – and, most importantly, not during the “greatest period of impact”, which according to them, was between February 13 and February 18. Cloudflare’s DNS hosting was not affected by this issue. In addition, earlier today Cloudflare sent us an email, assuring that the domain for which we have DNS hosted by them “is not one of the domains where [they] have discovered exposed data in any third party caches”.

Still, if you used your dotAccount password on any other sign-in system, we heavily recommend that you change it immediately. Even though your password was certainly not leaked when in transit to our websites, it could have been leaked when signing in to other websites behind Cloudflare’s proxy service. From on now, use different passwords for each website.


Despite using some of Cloudflare’s services, we have always made a conscious effort to avoid their reverse proxying offers. While it is true that a large percentage of today’s web traffic goes through them, it is our understanding that the advertised increase in website availability and speed, do not make up for the potential security troubles and the need to trust yet another party.

Furthermore, a large part of the traffic handled by us, namely with the tny.im shortener, is not well-suited to caching, or would be hard to integrate with Cloudflare, to say the least. Any security or availability problem affecting Cloudflare will almost certainly affect all of the websites that use it, as could be seen with this incident.

It is also our belief that having a major portion of internet traffic going through one same entity poses a threat to the decentralized model of the internet, introducing a prominent single point of failure. This is true especially when said entity sells caching and request manipulation as one of their main features (see their “ScrapeShield” feature).

Their DNS hosting service was not affected by this issue, but it has had its share of availability issues in the past. We use it mainly because it is one of the few that can be controlled through an API, but we don’t need this at the moment. Migrating to another DNS hosting service is a possibility that was already being studied before this news broke, and which will now be considered more seriously.

]]>
https://i.tny.im/?feed=rss2&p=642 0
HTTP/2 enabled https://i.tny.im/?p=640 https://i.tny.im/?p=640#respond Tue, 03 Jan 2017 15:22:17 +0000 https://i.tny.im/?p=640 Continue reading

]]>
Today, we enabled HTTP/2 support on most websites of the TNY network – including tny.im, dotAccount and Clouttery. HTTP/2 is the latest major revision to the HTTP network protocol, used to access virtually every website. Most up-to-date web browsers already support this protocol, and will use it when accessing our websites through secure connections (HTTPS).

When using HTTP/2, users will notice that pages load a bit faster, especially over slower connections. It will also let us serve more users with the same resources, as HTTP/2 optimizes bandwidth consumption.

This move, together with the efforts to make HTTPS available on our websites, and make them available over IPv6, is part of a series of changes we’ve been making to ensure the best quality of service for our users. It’s possible, however, that the multiple configuration changes are leaving some people in the dark – people using old web browsers, old operating systems or improperly configured internet connections may have trouble accessing our websites. To these people, we recommend upgrading to more recent solutions (from browsers, to operating systems and, if necessary, hardware) to ensure they can remain connected to the world, as more and more websites drop support for obsolete technologies.

Last but not least, let us take this opportunity to wish all of our users a happy 2017.

]]>
https://i.tny.im/?feed=rss2&p=640 0
Last days for migrating tny. accounts https://i.tny.im/?p=602 https://i.tny.im/?p=602#respond Sun, 24 Apr 2016 12:01:21 +0000 http://i.tny.im/?p=602 Continue reading

]]>
On February 14, we discontinued the tny. accounts single sign-on service in favor of dotAccount. In practice, this means that dotAccount is now used to sign in to all TNY network websites and services, including the tny.im shortener. In order to keep using your account, you must migrate it to the new single sign-on service.

This is a reminder that, as announced on that day, on April 30 the remaining tny. accounts functionality will be shut down. You won’t be able to migrate tny. accounts to dotAccount accounts past this date. On April 30, access to non-migrated accounts will be effectively and permanently lost; in the case of tny.im, for example, you will stop being able to manage short URLs in your account.

If you are yet to migrate your account, please migrate it now. You have less than six days left. If you have any questions, you can contact us at the usual email address, admin -at- tny.im.

]]>
https://i.tny.im/?feed=rss2&p=602 0
tny. internet media is no more – long live TNY network! https://i.tny.im/?p=552 https://i.tny.im/?p=552#respond Thu, 11 Feb 2016 18:32:02 +0000 http://i.tny.im/?p=552 Continue reading

]]>
In an effort to improve our image, today we have gone through the biggest reorganization and rebranding in our history. The tny. internet media group is no more; now, two separate but very close entities exist: Segvault, and the TNY network.

Segvault, a software development group created a few months ago as a spin-off of tny. internet media, becomes the copyright holder of all of the existing tny. internet media works. All resources, like servers, domain names and transactionable goods, are now property of Segvault.

The TNY network is the home to all Segvault projects, plus other projects not owned by tny. internet media, but that were otherwise part of the group, like CPUVInf. The intention is to grow this network past the existing websites and projects, leaving the ownership situation more clear for all.

With this change, which was prepared in the last couple of months, we also made ourselves more marketable and literally more pronounceable. Should there be any doubts, the letters in “TNY” are to be spelled separately, and “Segvault” should be pronounced as a single word.

What are the changes to project funding and revenue sources?

The tny.im shortener is, more than ever, the main source of revenue. Currently, all other sources of revenue are negligible, so there are no changes here.

Previously, the proceedings from the tny.im operation would be managed by tny. internet media; now, they are going to be managed by Segvault, as it now owns tny.im. Segvault will use them, the ABB (Accumulated Bitcoin Buffer), and eventually personal contributions of its members, to finance operational expenses of the TNY network, as well as all the Segvault projects. Projects that are part of the TNY network but not owned by Segvault may apply to use some of this revenue and/or have access to ABB funding.

How does this affect existing services and projects?

With the exception of some renaming and minor graphical changes, everything stays the same. The tny.im shortener will use the old tny. internet media branding; it is now exclusively used for tny.im.

Segvault is currently concentrating its efforts in migrating services using the old tny. accounts Single Sign-On service to the more modern dotAccount; in some months, this service should be available for all the websites of the TNY network to use as they will, preferably as their main authentication method.

Certain existing projects, such as Casio Prizm add-ins, were not and will not be updated to the new branding and copyright situation. In these, depending on the context (i.e., whether expressing rights to them or not), “tny. internet media” should read “Segvault” (if expressing rights) or “TNY network” (if expressing affiliation or for marketing purposes).

Final words

We believe these changes represent an important step in the history of our projects. Everyone will finally be able to present the home to their projects without the need to explain how to pronounce its name. The age of names forcefully tailored to a domain name is over, as it well should and long ago. The changes also make it easier for people to join the TNY network and/or Segvault, and still clearly hold the full rights to their creations if they so wish.

If you have any questions, concerns or otherwise want to give your feedback, feel free to do so below or through the usual means. Long live TNY network!

]]>
https://i.tny.im/?feed=rss2&p=552 0
Goshify is alive! https://i.tny.im/?p=509 https://i.tny.im/?p=509#respond Thu, 31 Dec 2015 13:33:17 +0000 http://i.tny.im/?p=509 Continue reading

]]>
We just launched Goshify, a small web service that is like hashify.me, but without the need to have JavaScript enabled on the client side. Additionally, it also functions as a Markdown pastebin. Designed to be minimalist, we hope this small tool will come in handy the next time you need to put up a short Markdown-formatted document.

]]>
https://i.tny.im/?feed=rss2&p=509 0
New service status website https://i.tny.im/?p=457 https://i.tny.im/?p=457#respond Wed, 09 Sep 2015 10:47:50 +0000 http://i.tny.im/?p=457 Continue reading

]]>
Service status updates and scheduled maintenance information will, from on now, be posted on the new service status website at status.tny.im.

]]>
https://i.tny.im/?feed=rss2&p=457 0
Service availability issue https://i.tny.im/?p=448 https://i.tny.im/?p=448#respond Mon, 08 Jun 2015 23:07:48 +0000 http://i.tny.im/?p=448 Continue reading

]]>
An unexpected service unavailability event took place from 20:00 8 June to 01:00 9 June (times are UTC, approximate). Services affected were: this website, PrizmID and certain internal resources. The tny.im shortener may have suffered from brief unavailability problems, for some users, during this period. All of our other services were not affected. We apologize for any inconvenience this service interruption may have caused.

Finally, let us take this opportunity to inform that scheduled maintenance is planned for the month of July on the user accounts system (tny. accounts). This means the portions of our services that depend on user accounts, for mandatory authentication or additional features, will be unavailable for brief periods. A more detailed schedule for the planned interruptions will be announced on this website at a later date.

]]>
https://i.tny.im/?feed=rss2&p=448 0
Account management email sending fixed https://i.tny.im/?p=419 https://i.tny.im/?p=419#respond Fri, 20 Mar 2015 09:54:08 +0000 http://i.tny.im/?p=419 Continue reading

]]>
A problem with delivery of emails sent by the tny. accounts website, which prevented signups and password recoveries, was fixed yesterday. If you tried to sign-up or reset your password in the past few weeks, and received no email or an error message on the website, please try again now.

We are sorry for the inconvenience. If you run into problems on our websites, please make sure to contact us.

]]>
https://i.tny.im/?feed=rss2&p=419 0
tny.im IPv6 connectivity problem solved https://i.tny.im/?p=410 https://i.tny.im/?p=410#respond Tue, 10 Mar 2015 20:39:18 +0000 http://i.tny.im/?p=410 Continue reading

]]>
Due to a small error in the server configuration, tny.im was unreachable over IPv6 for an unknown amount of time, despite all the technical requirements for IPv6 connectivity to work being fulfilled. We have fixed the problem now and apologize for any inconvenience.

We plan to bring IPv6 connectivity to other tny. internet media websites in a matter of weeks.

]]>
https://i.tny.im/?feed=rss2&p=410 0