somishere

Have to disagree here. "History mix" is a super common use case for me, as is a "clip slip" scenario - where I fumble and erase the future.

The technique as described works fine for this. I use it in the terminal all the time (an interface where state is saved on execution rather than keystroke). You go up through the history, copy the part of the command you need and head back to the present to use it.

I think it just comes down to the point at which state is modified. I wouldn't expect an implementation to modify state just by viewing the history, only by editing it. Suffice it to say your use case is fine.

Edit: tho, reading some of your other comments I agree that a better interface for this use case (e.g. a "revert to last meaningful edit" action) would be useful. Tho its slightly tangential to the discussion.

Was snorkeling with my 4yo in July and came across a decent sized octopus curled up under a small bit of coral substrate on the reef flat, in about 40cm of water. Wasn't able to id it properly, but we sat there for 15 minutes watching each other. Longest the kid has ever sat still in one spot. Cephalopods are without doubt the coolest fish in the sea.

Might be wrong, but looks like the body text is just using the mono font. They've named the fonts Alliance1 (mono) and Alliance2 (hubot) in the stylesheet.

There's an issue with the editable / interactive section on Firefox, might be what you're seeing. Otherwise mono is slightly rounder than hubot (look at the "t")

Thanks for the kind words - though not certain too many would share your enthusiasm! Good luck with the tinkering.

Lucky, that could have been an uphill battle

Replied. Cheers!

Thanks for the heads up. There's nothing mind blowing on the demo page, but password has been unexpired if you still want to take a look.

Biggest advantage I find is pre-scoped request-level control over everything. When someone loads your page, every single asset request hits your worker. It's both extremely simple and exceptionally powerful. Choose which responses to modify, authenticate, proxy, redirect, or let through. All in a single file with a few dozen LOC. No complex pre-app devops, middleware or routing policies required (i.e. oh sorry that route is proxied by a lambda, or you should check the cloudflare dash there's a worker sitting in front of that).

Yes, there are a bunch of limitations - but in practice I quite appreciate the boundaries and the reasoning. There's also the portability question, but we're talking about PaaS. As someone who was using Firebase for many years, and static AWS + lambda prior to that I find this evolution entirely refreshing.

I've pushed 5 personal projects on pages since Jan and working on more. Most recently https://thesom.au/gh/cvms

AIMS are the main org I know of that are doing lab-based synchronised spawning in Australia, and more interestingly IMO spawning/survivorship under future conditions. SeaSim is fairly well known here and tends to get national media attention around the annual mass coral spawning event (expected early next month).

https://www.aims.gov.au/about/facilities/national-sea-simula...

I should add, obsidian value add here is the android client which IMO needs a lot more focus due to input / storage considerations (constraints). If just syncing across desktops then sublime/similar with it's folder display would likely suit my needs.

Just converted all my completely random unsaved (30+ permanently open) note taking tabs/windows from sublime into an obsidian document structure, synced to android with syncthing. Took about 10mins total. Love it.

If anyone's interested ... two very (very) minor things I've noticed in my 20mins of usage (apologies if these are solved - I haven't got to the literature yet):

- same-same appearance of sub-list markers (I prefer alternative icons for tiered lists)

- Headline / filename special characters conundrum. Many of my docs had headlines in them that weren't suitable as filenames, I found myself repeating the non-filesafe headline on the first line. I wonder if there's some kind of front-matter setup that could resolve this?

Parent comment probably not worth engaging with .. but mentioning yarn / npm / node feels like some serious flamebait overkill here too :?

If it were my project I'd just be assuming contributors had internet access and advising in the readme to "search for a good 'bookmarklet generator', paste in your code, then test it". I'd then test their tested bookmarklet code before accepting any PRs. Thus reducing the repo to two files and 1% of current complexity, most of that being in the readme itself.

Totally agree there's no hard and fast rules here. That said, this person probably lucked out with a dependable team, and no doubt relied on intra-leadership (from yourself or peers I would assume!) to manage - and deliver - effectively. This kind of dependability doesn't usually appear out of thin air. It's also a bit of a catch 22 to replicate.

I've worked with similar people and there is definitely a place for them (tho probably not at the peak of the structure). But it's also nice to have someone that can critically discuss a solution and sign off on decisions that they fully understand. IMO.

I live in a place with cassowaries and come across them in the wild every now and then. They're usually extremely dangerous, except for this one particular bird that lives at a rainforested beach called Etty bay. I have been chased by this bird, around a table while he tried to get my bag full of fruit - but generally speaking he/she is usually pretty chill and content to just stroll up and down the beach amongst the families, seeing what's up. Obviously this is a total tragedy .. she'll certainly end up getting killed because of the familiarity, but it's also entirely fascinating seeing this 1.5m tall wild bird just stroll out of the rainforest and start interacting with everyone.

No dashboard, or web interface even - the idea is that you just use CF's worker analytics for usage stats. There's no storage / db sitting behind it, just a single file to deploy as a worker.

Logical next step would be to hook it into KV and include a basic auth/admin API for editing routes and retrieving stats. But even that would add a bucket load of complexity to what is essentially 20-30 lines of obtuse logic currently.

Definitely no plans to deploy as a service with custom domains and enterprise offerings :)

I built a very, very basic one of these a month ago to shorten a couple of unruly domains I had. Supports static and dynamic endpoints that you define.

https://thesom.au/gh/shorturl

Intended to self host for free/minimal cost on CloudFlare, thus comes with built in analytics, BYO domain, etc.

Also cat food. They invest in a reef conservation technique too, and named a reef in Indo - where they were trialing said technique - after one of their catfood brands. The logo says "more coral today, more fish tomorrow" and there's a picture of a cat.

https://www.forbes.com/sites/johannaread/2021/05/05/the-sheb...

Thanks, appreciate the insight! I think client pub/sub is the feature request, not firebase clone :)

To that point there's definitely a few OSS solutions out there that provide this kind of functionality out of the box (recent YC alumni among them). But then who knows what problem you're trying to solve. Sounds like this is just rain on the tip of the iceberg.

So is that to say it's just an unintended consequence of the data being hosted on Firebase? That's wild. Especially as I'd be surprised if most integrations aren't using this feature (IMO it's by and far the best feature of the API).

To demonstrate, here's an example in 18 lines of code that v. efficiently listens to live updates to a profile (yours): https://codepen.io/theprojectsomething/pen/xxWBOWN?editors=1...

Switch to Supabase?

Yes. At the very least some kind of pub/sub interface? Also worth noting that, if it's the data depth issue that's looking to be resolved, the Algolia API is often useful in places the Firebase structure falls short.

The great thing about the Firebase API is that it's live, so you can subscribe to updates to a post/comment/profile and see them as they're made (no polling, just websockets). I'd hope any future version would retain this feature.

I'm reluctant to lose it as I'm about to release a browser extension that relies on it pretty heavily :)

[Edit]: this feature is undocumented in the link above, but it's a standard feature of FB and works as expected in all client libraries https://firebase.google.com/docs/database

This is cool. I've been using tinypng.com (a service that uses "their" servers!!) for years, even with PS, IM and the rest installed locally .. basically due to - until very recently - superior compression, especially of png. It's entirely useful. Will take this newfangled local effort for a test run at my next rodeo :)

Came here to say the same thing. Great article btw. Finished it with examples/js disabled :)

I'm sorry but I'm not sure I follow. Are you suggesting that the nutrients that get washed out via catchments in NSW end up on the GBR? I didn't realise this. Certainly water quality is a massive issue, and the current mess going on in the Murray-Darling is highly concerning in a general way. Also regards the nutrients, yes we have exactly the same issue with e.g. sugar, bananas, graziers up here.

Yep totally agree with your statement. My point was that there isn't a lot of cotton being grown in GBR catchments, so it wouldn't be one of the main industries directly effecting water quality on the reef.

AFAIK not a lot of cotton farming going on in reef catchment areas. There is lots of sugar cane and bananas however. Also lots of deforestation for grazing. Plus major resource export ports (LNG, coal). Regardless, runoff remains a major topic and there is some progress being made in the space [1].

Regards the article. If you look to the report itself[2] you'll see that this isn't a "she'll be right" triumph of science over scare campaigns. Climate change sits at the top of a growing list of concerns. The summary specifically mentions increased frequency of both marine heatwaves (that lead to bleaching) and major destructive weather events like cyclones. The other serious concern is crown-of-thorns starfish (a sea star that eats coral) ... and while the jury may still be out on the cause of their outbreaks (overfishing of predators? excess nutrients? changing environment?), the effect of this single species on the broader ecosystem is beyond frightening to witness.

It's extremely difficult to have a meaningful conversation about the threats to the reef without getting into the weeds. The "scare" campaigns may be light on detail, glossing over (or ignoring) much of the important nuance, but (for the most part) they aren't wrong.

[1] https://www.gbrmpa.gov.au/our-work/threats-to-the-reef/decli... [2] https://www.aims.gov.au/monitoring-great-barrier-reef/gbr-co...

No offense, but whoever you were speaking to was telling whoppers. Conservation efforts on the Great Barrier Reef are extremely limited in both scope and success.

[Edit] Sorry, not meaning to be overly negative. Happy to provide further detail of the efforts in place if you let me know where you were!

Cool video! I'm based in Cairns and work on and around the reef. Definitely appreciate the sentiment of the point you're making here (generally speaking it's true), but the argument is nuanced.

It's nice to see visual evidence that backs up your personal beliefs. That said, it's also problematic to take a video of one tiny, tiny part of the great barrier reef and use it as evidence as to the state of the broader ecosystem (a system so large it would run almost the entire length of the US West Coast, consisting of over 4,000 reefs, some as large as 90km² with widely varying conditions). In fact, there are many groups who deny climate change, the science around it, and the decline of the GBR. In Australia, the IPA are one of these ... who visit pristine reefs (there are many pristine reefs) and take video to further these kind of bogus claims.

On your video. First place was Fitzroy Island, which has a shallow, fringing reef around it. I've been visiting Fitzroy since the 80s and it has certainly changed over the years. That said, in-shore fringing reefs are not a good indication of much, as they are susceptible to pretty much every kind of disturbance. There is an area around the corner from where you were filming on the Island called Shark Fin bay that has 100% coral cover, probably due to slightly better currents (it's just outside of the lee of the island and few people go there). Your dive site was probably Milln or Flynn reef which are both outer reefs, about 40km off the coast. They are both in fairly good shape as far as tourist reefs go, with great visibility and decent coral cover. There's another reef very nearby called Hastings, which has good coral cover (and a lot of life, people often sight Mantas and other bigger stuff there) but the visibility is terrible due to sediment being picked up by currents. On all these reefs the condition would be entirely variable on different aspects of the same reef alone (i.e. north, south, east, west, windward / lee).

Long story short, the science here is about data. Big data. And while highly local, anecdotal evidence can definitely play a part it has to be considered within the correct context.

If you're interested, I built a tool[1] a couple of years ago based on surveys we were doing across the length of the reef. It gives a sense of coral cover, health, and the importance of individual reefs to the broader system.

[1] https://greatreefcensus.org/detailed-reporting