neuroscr

Also a dev on loki-network, we have $4.1+ million USD so far invested in relays (and potentially exits). It's layer 3 (so think more like i2p) but newer crypto and much better latency.

A good overview of the project is here: https://github.com/loki-project/loki-network/blob/master/doc...

other docs here: https://github.com/loki-project/loki-network/blob/master/doc...

Join our test-net now: https://discord.gg/eB8k6xQ or #llarp on freenode

I thought that about their keyboard too but they just opened it up in iOS8. I believe things are changing.

Bunch of z-machine games here: http://ifiction.org/

Pretty neat project. I love seeing the base integration with the Android OS. And I think it's a wise move to have some sort of app on iOS. I'm an iOS user myself, however I can't run your app since I'm still on iOS6. I hope Apple allows this type of integration in the future (but I'm sure the carriers will take some type to get used to the idea of making money off Data instead of voice.) Good luck!

I can confirm they did lay-off most of their staff though.

The parent company is still there. It pretty much means, they're pivoting with all the money they raised.

Taking PHP Seriously is a great presentation that talks about why FB is using PHP: http://www.infoq.com/presentations/php-history

>pure PHP will become a less-tested second-class citizen on HHVM

Not really true because HHVM has to run basic PHP before it can apply the Hack annotation. You can pull out the annotations and it's still PHP.

>Someone's got some code for moving file handles around on GitHub but I can't seem to Google it up:

https://github.com/sharvil/flingfd

Sending your random seed over the wire doesn't sound like the right direction. For those listening, it always makes sure they have your seed. Did the NSA get them too?

Excellent point.

And as an app.net 3rd party dev, I wouldn't mind paying in BTC however I'm already paid up for the next year. I'm not going to prepare several years in advance either.

So giving a 30 day window for ~$10k when they're not really actively marketing for new users just is asking for failure.

Art can be interpreted in may ways. Just because the author reads it one way doesn't mean it was the intent.

It was actually part of their original plan (See the beginning of http://blog.app.net/2013/02/25/introducing-a-free-tier/)

First they charged and crowd-sourced for marketing and proving their concept. Paying early adopters allowed them to pay developers which attracted the developers who made apps. Then they had the apps and content to attract the users, so they made it free.

I believe they embraced of open standards like RSS and WebFinger (http://blog.app.net/2013/08/07/response-to-brennan-novak-par...) to make sure developers would choose them for implementation.

I think App.net maybe trying to become the identity platform for the web (maybe not the only one but a damn good alternative to the rest).

As a developer given the choice between Twitter's 100k token limit or App.net's almost 200k users (plus a chance to get paid by app.net) it's a no brainer.

I think their main competitor now is Facebook Connect. And there are plenty of users out there that are refusing to use FB.

It doesn't require a 3rd party app at all. For an invite an 3rd party app will give a bonus to the person that invited you.

http://blog.app.net/2013/02/25/introducing-a-free-tier/

Isn't DropBox's data api more granular (record-level). Where App.net is more coarse (file-level) and not really ideal for changing data. In fact App.net only has one primitive that you can edit and it can only store up to 8k of data.

This is app.net to Push. There are several was to get data on app.net and as well out of App.net. Mainly via 3rd party software and their open source PourOver app.

I've written an IRC and IMAP bridge to get data off app.net personally.

Sometimes the article isn't that great but the comment threads are amazing. I don't want to up vote the article but I do want people to read the threads. It would be nice to be able to up vote just the comments of a link.

Ah in that context, this makes more sense. Thanks for the reply.

It's not clear if the wallclock savings was consistent over multiple runs.

And by moving one look-up out of redis into ruby, doesn't seem like the right thing to do. That increases complexity by now requires an application layer to process the data source.

I'd like to see how this compares with just simply increasing list-max-ziplist-entries.

What group chat app is that? If you're talking about photos in patter chat, there's an established annotation for it that most clients can read and use.

Are open standards not important? Just the source?

They have been starting to release the source code of the client applications they've built: https://github.com/appdotnet/

They've embraced open standards: http://blog.app.net/2013/08/07/response-to-brennan-novak-par...

And they have started releasing client source code: https://github.com/appdotnet/

a16z is already getting a return, since App.net has been profitable for a while. It's all gravy since they've made it free to sign up. The user base is about 10 times bigger than last year. It's true we don't know how many new users are paying but since that fixed costs are covered, it doesn't really matter.

It was a big mistake. Clinging on to the twitter model gave them something tangible to model after and improve on but the result of that is the API is largely for micro-blogging. They have some file storage now but the primitives for a broad web application building platform aren't there yet. So from reading the API from a developers point of view, it's obvious that it's for micro-blogging. It takes a lot of imagination and effort to repurpose their API into something new.

Early adopters aren't tired yet because App.net's continually releasing interesting updates to the platform. And there's even a great example of 3rd party developers working together on their system to extend and support one 3rd party developer's chat system (patter). So each developer's project help retainer interest as well.

So as long as App.net keeps releasing new APIs and developers stay interested in the platform. I don't think early adopters will get tired.

Funny you should mention that. I feel that crowd-sourcing user interface development by given an open access to an API will lead to new experiments with UI/UX.

I believe when Twitter was more open, we saw an explosion of clients and UI/UX. A couple of these innovations we hadn't easily seen before.

One of the hopes is that the App.net platform continues this experiment.

Users care because it's easier to pay $5/mo, than to set up and maintain your own infrastructure. Especially if you don't have any experience with servers (Think Grandma, Mom, Dad, non-techies etc).

Well, I think they captured some imaginations, to the point where they were told it's impossible. So it's an interesting experiment. Especially since they've been success and on-target to deliver most of their promises so far.

It's a huge risk, that not many investors would take. The financial returns are questionable, but what it could do for the Internet as a platform is disrupt the current mega social providers and IMHO I think that's worth trying.

App.net does provide an account export. But more important they've embraced open standards, see: http://blog.app.net/2013/08/07/response-to-brennan-novak-par...

This type of interoperability combined with sections of their API that are public (tokenless) provide a way to consume App.net content without needing an account unless you want to participate.

Then there are 3rd party apps and additions that bring even more open interoperability.

For development, there is Dev-Lite, so if you want to play around with the API, you don't need to spend $100/year until you're ready to join their Developer Incentive Program. And most Developers that have built anything for app.net have made their $100/year investment.

And App.net's annotation are another great example of creating new open standard of interoperability. These attachments can be added to any App.net API primitive to provide additional structured data to enhance interoperability between developer applications. Here's a link to their document repository for this: https://github.com/appdotnet/object-metadata

App.net's API does providing more than a microblogging API. They have a file hosting (each user has their own quota), permissive messaging (point to point or group), and a search API so you can easily find anything on their system. They're planning to add more useful APIs, such as billing.

Twitter only allows you access to 100k users or so (tokens), and your business is at risk of being turned off. or App.net providers you access to 150k+ users growing user base. Plus an a free sign up, access to hosting for file storage, and permissive messaging.