y0ghur7_xxx

Why "hijacked" TLD? It would be a standard TLD.

If two orgs merge, and they both happen to use the same hostnames for some things, like say git.internal, they just refactor those hosts, or merge them since they merge.

related discussion:

http://serverfault.com/questions/17255/top-level-domain-doma...

nothing. the rfc talks only about the localhost tld.

Then you have a gazillion of "Open source licenses", that can be less "free" to more "free", like BSD, GNU, MIT, Apache, the free source license, ...

one downside was that it didn't work on things like airport access points, but those break regular tls too.

an other downside was the fact that google didn't want to integrate it in chrome because the notaries would have to be always up. now they run transparency logs that have to be always up anyway. so.. what's the difference?

The Perspectives Project piked up the idea, and it seems less dead that Convergence: https://perspectives-project.org/

Really awesome to make a quick app for someone who is already good in making webapps and needs the power/access/network rights of a desktop app.

¹https://github.com/S2-/http-client

²https://github.com/electron/electron/blob/master/docs/api/au...

Wanted to share this, maybe someone else finds it useful. And it's really easy to hack: just one html file and one js file.

email: I run my own server. After the initial "reputation building" for my domain, it now works reliably well.

calendar/files/photos/contacts: nextcloud on my home server. It's not really on par with the google offerings, but it works well enough for me. And when I need more storage I just get a 2TB usb disk off amazon.

play store: f-droid. It has everything I need. I understand that not everyone might be happy with just the apps on f-droid, but I was bored with downloading crappy games and uninstalling them after 2 minutes anyway. f-droid apps are all well done, and I trust them not to invade my privacy.

I may be overreacting on this, but this sounds like "you who found bugs in our code: document them better next time". I think the reporter does not owe freebsd anything. If someone owes someone else something, freebsd developers should thank the reporter for finding those vulnerabilities, and not ask for even more of him.

    navigator.getBattery().then(function(a) {console.log(a);})

Fail gracefully was over the moment the "disable javascript" checkbox was removed from the options menu in every major browser.

¹https://www.linickx.com/monitor-for-fake-certificates-with-c...

edit: my ifttt recipe: https://ifttt.com/recipes/444453-get-notified-when-a-certifi...

Probably. But is that really my fault?

There is CouchDB, CouchIO, CouchOne, Couchbase, Couchbase Server, Couchbase Mobile, Couchbase Lite, CouchApps, BigCouch, Touchbase, Membase, Memcached, MemcacheDB... all different and yet related in a way not at all obvious from the names alone.

First there was CouchDB, a database created by Damien Katz, a former IBM developer. Its official name was changed to Apache CouchDB after it became an Apache project.

A company named CouchIO was founded to work on Apache CouchDB and later changed its name to CouchOne (by "its name" I mean the company name - not the database name).

CouchOne (formerly CouchIO) merged with Membase (formerly NorthScale) to form a new company called Couchbase. Membase (the company) developed Membase (a product of the same name). Membase was created by several leaders of the Memcached project and it used the Memcached protocol. After the merger of CouchOne and Membase, Couchbase continued the development of the Membase software and later changed its name to Couchbase Server.

Today I think most people believe that Couchbase Server is a new version of CouchDB but it is in fact a new version of Membase. It still uses the Memcached protocol and not the RESTful API of CouchDB. Meanwhile CouchDB is still CouchDB, actively maintained and enhanced as an Apache project.

http://stackoverflow.com/a/15184612/512324

    function(newDoc, oldDoc, userCtx) {
        if (userCtx.roles.indexOf('can-write-sessions') !== -1 || userCtx.roles.indexOf('admin') !== -1) {
            return;
        } else {
            throw ({
                forbidden: 'can-write-sessions role missing'
            });
        }
    }

¹https://news.ycombinator.com/item?id=11757015

(couchbase sales people came answering, even if couchbase is a completely different product that covers different usecases)

     LogLevel dumpio:trace7
     DumpIOInput On
     DumpIOOutput On

¹http://httpd.apache.org/docs/current/mod/mod_dumpio.html

The only thing I can think of is the initial setup I had to do to get everything done, but that's a few hours of work and it's here now. Using it for years without having to do anything. Some friends of mine use it, and my family, and nobody complains. Ever.

Personally I am really happy that we have someone watching over our privacy, and that the use of our personal data is regulated.

because the message can be sent to different devices (resources) the user is connected with. This is not accidental complexity like you make it out to be. It is needed and wanted.

Or are you advocating a binary protocol? Personally I really like the messages exchanged with xmpp: they are easy to understand and easy to craft. I think the success of http too, lies a little bit in the fact that it is human readable.

> It's easy to blow off complaints like mine, because everyone on hackernews has a Samsung Universe S2000 or an iPhone 128 Plus, but these are real concerns that real people have in the real world.

I am using Conversations with my family and friends on a prosody server I put on a kimsufi server. It works like a charm, and we don't have all super awesome android phones (but I have to agree, nobody has an S40. Do they even exist anymore?).

I think your experience is outdated and not correct anymore.

you restore backups even if the server is still ok? why?!

when someone using conversations writes to me, what i expect is that i get the message on my desktop, as well as on my mobile client. but conversations will ALWAYS ask the user where he wants to send the message, if on my phone or on my desktop client. this should not happen. it should just send it without the resource set, and let the xmpp server figure it out.

If you have a github account the script could also get the pubkey directly from the github api...

¹http://superuser.com/questions/576506/how-to-use-ssh-rsa-pub...

Mozilla, Google, Apple and Microsoft should remove this CA ASAP. If it breaks some sites, even better. Maybe it will make some noise and fix all this CA bullshit for good.

   0.9  Works