Didn't really consider putting it out in public. Is there a viable product out of this? How much would you pay.

Simple totally offline ONNX models exist, whcih should make it trivial to categorize the right orientation. Acceleometer/magnetometer can feed this, but should not be the default.

Just do this and avoid the hassle of rotating at all!

With such an article, many (including perhaps google) get the ammo to disregard what fdroid says, by branding them as childish/not to be taken seriously. for eg: no reputable news org is going to post this.

PS: https://keepandroidopen.org/ is better done.

Many ways of adding friction to obtaining the updatable value - which a human owning a domain would be happy to do, but a squatter would not want to.

> You cannot transfer ownership killing any value you added

I think this is by design. The domain should be for personal use - hence free.

0) The actual intersting part of a new TLD can be growing reputation by post-facto taking away a domain without recourse in case of squatting. Instead of adversarial takedowns (which produce false positives as noted), let anyone challenge an inactive domain in the first year or two.

1) If they can figure out a mechanism for moving a domain from "assigned" -> "squatted".

2) Domain must match (or derive from) a verified identity - e.g. your domain is a hash/slug of your government ID. Makes squatting structurally impossible because you can't claim someone else's name / gov (Sign in with passkeys linked to a national ID).

3) Proof of human effort, reduced with time - require periodic renewal with proof-of-use (DNS TXt updates, through a flow hard to automate).

4) Kill speculative market - domains are non-sellable and non-transferable - always go back to the free pool, and stay there for 30 days mandatorily.

Some mix of these could be the right structure for a trule high-reputation, free domain.

- simply expose containers to the world directly - without having to go via workers.

- You have other amazing parts of the stack anyway (D1, durable objects, a great object store). These aren't considered "lockin".

- workers is "lockin" - not similar enough to lambda/cloud functions and so becomes CF specific.

Not having a simple container based compute piece has made me hesitate in taking up CF. (Fly or firebase won out)

It's not technically a translation, it's a re-implementation, with test suites acting as the destination. If it was a file by file translation your argument would have been valid.

Interesting - they're commiting to kickoff policy conventions to organize a world-slowdown of frontier LLM building. If they actually are able to crack it, this will give a much needed breather IMO. As exciting as the last ~6 months have been, there's some bigger questions to go answer now.

1) That LLM/Agents are being pushed and not adopted. I see plenty of deep adoption by junior folks.

2) The unit economics don't work out. From the details on every model so far - each model is wildly profitable over it's amotized time-frame. It's just that money is used upfront for the next model, and each next model is significantly more costly to train. The best case argument instead is - this will not last and we'll pour more on some models, than see in it's revenue.

I think realistically these form the core of the thesis, and IMO, and hence it's conclusions are a bit off the mark.

- Lesser overall engineers needed -> lesser demand of human engineers -> lower compensations

- insufficient training at junior levels.

- longer time to productive human engineering skill.

These are playing out right now, and a concern for all engineers in the industry. IronMan amplification don't address the above

https://github.com/Planet-Source-Code/anil-gulecha-bat-man-b...

VB6: What made a generation fall in love with programming.

I can completely empathize - sometimes some problems never leave us.. like that piece of food stuck b/w teeth. There's a force within us asking us to right that problem in the world.

All the best to your project.