jschlesser

Your legs are moving but your head / vestibular system isn’t experiencing acceleration that it expects with those leg movements. Think of it this way, if you are holding a pendulum and take a normal step forward, the pendulum will start to swing. If you take a step forward on the magic floor tiles, your legs move normally but since your body stays in the same place, the pendulum is motionless.

The article says its SSMB which is a hybrid of synchrotron and a linear free electron laser. https://www.quora.com/What-is-a-Synchrotron-SSMB-generated-E...

A self replicating supply chain is obviously the basis for success and scalability of the ‘replicator program’.

I've been working on a little project that uses D1 and have been hoping that is how D1 will evolve. A db per customer in my case. Is the colocation in a durable object so 'business logic' and sqlite can live in the same isolate for performance and security? Would that be a post 'out of beta' feature? Ive been building as a monolith thinking that the number of databases in the alpha was indicative of the future.

I grew up in Oxford, MS. circa 1980. Kudzu didn’t blanket the roadside landscape at that time. It does now. Every time I go back, it is the blanket over everything. I love the flowery language of the article (takes me back a bit), but it really has overtaken the landscape. If you grew up there, you know.

Unrecorded phrases from the approval meeting.

It looks 'sturdy'.

I didn't know they made LEGOs at this scale.

I knew ChatGPT would affect a lot of professions but I didn't think it would be this fast.

Future proof, It blends in seamlessly to the Bladerunneresque environment we imagine the future will look like.

We already removed all the 'slack' from the project.

They have a business plan that is predicated on people signing up for a service that they want to use but don’t and fail to unsubscribe because it’s like giving up on reaching their perceived potential best selves. It’s simple.

Daleks!

My team is 100% remote and we work with other teams that aren't. We use Google's Jamboard. All members of my team have iPads and 'pencils' and there is a dedicated app, and our conference rooms have special Jamboard devices mounted on our walls. It can be used from a browser too. They all work pretty seamlessly together. I don't work for google but I like Jamboard.

Shrug? I can’t remember the last time I needed source forge. What is there and why is it important to preserve that business model? I’m genuinely curious.

Thank You, I agree that explanations for people that already know are close to worthless.

Suppose it is mostly "professionals"

1. is it bad for individual "professionals" to invest capital on a small scale to provide services that people want at a greater or lesser price? Be it cars or houses.

2. If it is bad, why, and who for? Is it bad for consumers or bad for existing businesses?

true

It is a cloudflare subdomain but it doesn't show that way in the URL, I dont know how that works though. Can anybody explain why this works? I dont have a naked domain with ssl with them but you can check this one out to see what it looks like https://www.luckybolt.com (also thats my brothers startup, if you are in SF, check it out). As you point out though, GAE is $10 / Mo. cheaper. I'll check that out for new projects.

$20 a month for basic ssl. I have 2 criticisims of cloudflare and im a paying customer, which arent even close to making me look for alternatives. 1. They have had a few outages (but everybody does, amazon included). 2. Ive made their page rules engine do what i need but i felt their docs were not deep / technical enough about how their engine works. I had to play a bit to get exactly what i wanted. I have largely been happy though. Im not affiliated with them in any other way.

Also, though cloudflare allows it specifically for this purpose, cnaming a naked domain isnt technically in spec for dns. Every device / browser ive tried deals with it just fine though. If you are a stickler for rules go with a www. subdomain.

Try s3 + cloudflare. You will have to pay for ssl but barring that s3 + cloudflare will let you host a naked domain for almost free. Suppose you want some cheap static publishing, set up a dev heroku instance (free) and have it publish to your s3 bucket.

I think its an interesting concept if you can get JBoss to replicate the functionality of the OS and hardware behind most COBOL running on big iron but on low cost 'distributed' servers. Running COBOL is possible in non mainframe contexts already. Running COBOL with all the benefits of a mainframe without the mainframe cost and mainframe OS has not materialized. Its been surprisingly resilient to disruption so far. If you could offer all the functionality at a significant decrease in cost per mip, you would have a winner and a lot of fans (eventually as it became proven and big CIOs started to trust it). There are plenty of less critical workloads out there that could be migrated out though if they could access the same data cost effectively. What do you think the big challenges are?

I guess it really is just news here, in case you want to have a discussion that might help people, lets discuss over here: http://branch.com/b/nosql-vs-rdbms-how-to-decide as long as you are willing to keep it constructive, you are invited.

Dalton did back standards

http://daltoncaldwell.com/a-response-to-brennan-novak

I think the $50 model is going to get changed. My bet is that businesses building social into their sites off of the app.net infrastructure will end up paying. That was just to see if it was pursuing. Its not better support for 3rd party devs, the entire focus is 3rd party devs.

Also, by using it I mean both keeping in contact with people I met in Alpha.app.net but using a different UI which somebody already built, but more importantly, using the apis to build new social stuff and helping to form the apis.

Yes, but not how you might expect. I don't conceive of it as something where Dalton has to build this 1 big social network to eat the rest of them. Its going to allow a lot more context sensitive (in product/app/content) social networks to form that will be smaller but way more relevant. I think even after the apis are all baked there will be a robust services industry around it, collecting filtering graph walking analysis services etc. I think people looking at alpha.app.net and thinking thats it are totally off base. Not even wrong, misled by internet echo chamber.

Actually there isn't a UI really to App.net per se, its an infrastructure play, more twilio than twitter. They built a UI for demo purposes to let people know that it wasn't vapor. They don't even refer to the UI as app.net, its called Alpha to differentiate it. App.net is the apis on git hub, some of which are baked, enough to build Alpha. If you get a dev subscription you get api keys. Ive seen some pretty cool stuff already. The idea is that you build whatever social experience you want for your product. here is a for instance. Suppose you are the new york times, you could build social into your website and apps. subscribers could then see their social interactions and data in context rather than crammed between a cat photo and a belly fat ad on or underneath an unrelated tweet. Sane people could go have a convo and exclude trolls by forming ad hoc groups etc... tailor to the audience and the site to enhance the experience.

Also, there are/were cool people in Alpha and it wasn't so crowded a few hours ago that you couldn't talk to them. Famous VCs, internet celebs like Gruber and McCracken and Siracusa, regular celebs like Stephen Fry etc... I don't know what the plan is for Alpha but the point is the infrastructure not Dalton making an ad free twitterbook clone. Other people have already made better UIs than Alpha even. Apis pretty easy to use.

Note, got a reply from an insider @orian that this is not off base and how they are thinking too. More social infrastructure and not ad free twitter clone.

I think thats a narrow short term view of it but easy to assume given the surface information. Messages need to be succinct and understandable in familiar contexts and i think Ost of the opinions are based on 'ad free twitter' which isnt the big excitement in the app.net community. Im cross posting. Im a supporter but not an employee. I have read a lot more in depth and here is my take. http://news.ycombinator.com/item?id=4373394

Any reader of my comments should know im a supporter but not employed or beholden to app.net in any way and my opinions are solely based on my interpretation of publicly available info and informal interactions with people inside the app.net community. The actual apis and rules arent final but dalton has made many public commitments and has a history of doing what he says he will do. The work behind app.net didnt spring up overnight. I assume some vc money is in there somewhere so i wouldnt necessarily go vc bashing either. It looks a lot more like a pivot and if there are vcs involved, good on ya for backing it.

Disagree about network effects. It helps but its not about social graph monopoly. Its about not needing to chase that goal and the opportunities that open up when that isnt the goal. I will agree that large network effects are good for the effort but not a must and there is a public commitment to support interop and the ingress and egress of info to drive value to the users and support the devs.

Its not about destroying or replacing twitter or fb. Thats unlikely and not the goal. Its about new uses. T and FB have defined their contexts and rules. The infrastructure may look very similar but the universe of contexts and possibilities for non T and FB contexts is the point. The space of uses outside of T and FB is vast when publicity and ad focused mining isnt the core driver of business. FB and T have decided to compete for belly fat ads, thats the real shame. However they are both still revolutionary in terms of societal impact, they are just going to coerce their usage to fit their business model. Egyptian protesters and new moms posting baby photos could care less about belly fat ads. I truly sincerely hope both services find a more relevant way so that all models flourish.

I think how you concive it now is about spam free twitter or fb and thats what everybody is talking about. I dont think thats the real story. Imagine what you could do with real time syndication infrastructure with privacy and ownership controls built in. BP monitors, blood glucose monitors, runkeeper data, music listening streams, all kinds of data streams and a robust community of app builders to build all kinds of streaming and where desired sharing. If i dont want to see your spotify listens, i can turn that off, if i dont want you to see my health info but want to share with my doc, that can happen too. Go nuts, imagine the future without having to be forced to cram it into a timeline or public feed mined for ad relevance.

I agree that its not explained well by a paid real time social feed. Im a backer, here is what it is about for me.

1. Platform. Its not about 1 canonical interface or usage. Its real time social information network plumbing. Build your own idea on top of it. In the beginning it will be twitter clones, eventually it will be hooked into all sorts of information generators and consumers in different contexts.

2. Its about incentives. The incentives are for app.net to build the apis to support things twitter of fb never would, due an incentive to drive innovation, not stifle it.

3. Its about users control and choice. Use the interface or apps you want. Control where your information goes and who is mining it.

4. Its about friction. There is friction to blatant abuse via a pay model and there is a lack of friction to develop frictionless sharing with things like instagram.

5. Its about ownership. Your data is yours unless you choose to give it away to others.

6. Its also about alternatives to a single model for success (winner take all ad based strategies). I think its a mistake to think that its only successful with huge network effects. The infrastructure can service uses and apps that export information to other networks as well as in network uses. Its successful if it has paying users that pay for opex and capex and generate some profit.

The counter to this is that its difficult to explain to grandma in omaha until the new apps and usage models get built. If its just a paid twitter, it will fail in its ambitions. If it leads to safe private frictionless sharing in ways that couldnt realistically be contemplated before, its a success. The alpha proof of concept that is in place now is twitterish, no denying, but people are already working on things that just arent possible with facebook and twitter today.