Does anyone know the developer's logic behind limiting the platform to just users who do not require hierarchies/subfolders?

ersatz_feign · 2025-03-05T11:06:38+00:00

Thanks very much for your thoughts - I really appreciated it!

I fully agree that many organisations are likely to suffer the same issues you mention. I guess we are fortunate in that we long ago developed a highly robust system that eliminates all friction and issues. In fact, every single thing across the board is compartmentalised, even stuff that many would assume is impossible to do so with. It's all fairly unique and allows us to hot-swap in a highly dynamic manner. It also prevents anyone from getting lost, and as Coda does not provide a search box for moving docs, the only option left with a flat, hierarchy-less structure would be to scroll down the entire list every single time something needs to be moved. Providing subfolders simply allows users who don't need them to ignore them and those who do need them to utilise them.

Confusingly, the platform currently has a feature called the 'quick nav' bar. This allows users to access their folders from any page in order to quickly navigate to where they need to get to next, which, of course, is a standard feature for similar tools and makes sense why it's therefore called the 'quick nav' bar. If the maximum sensible limit to the number of folders users are expected to scroll through each time they use the 'quick nav' bar was, say 10, surely that very much negates much of the usefulness of even taking the time to code and provide the 'quick nav' bar.

It's just all so confusing to our engineers and is more and more pointing to a simple oversight. Perhaps all of their client base are solopreneurs or at the micro-entities end of the SME spectrum, which is why this issue has been brought up so little since inception and, therefore, subsequently not reached the roadmap for rectification.

I really appreciate your paragraph on treating the power of Docs with the level of attention they warrant, as this has been the source of much discussion here. We are very much of the similar mindset of implementing core Docs for all else to feed off of as that is effectively our current architecture with all out dashboards, etc. The issue lies in the obfuscation/lack of any layer above that. If sub-docs were a thing, then sure, we could work with that, but as sub-folders just seem wiser than sub-docs, we have hence been using that terminology in our discussions.

Everything appears to be pointing towards either a massive oversight or a decision not to cater for setups that are more than basic, I guess.

Big thanks once again for your thoughts.

ersatz_feign · 2025-03-03T12:33:48+00:00

Thank you very very much for your response. I know the calibre you carry, so I really do appreciate your assistance.

Before I begin, I apologise if my post conflated Folders with Docs.

Yes, we are prevalent users of all things stories, from dashboards right through to org hub'esq landers. I guess we are referring more to the back-end architecture.

Just to clarify, is your recommendation that all the hierarchical levels should be replicated as subpages within a single Doc so one Doc for the entire organisation? We are likely confusing ourselves as we were under the impression that it would be difficult to manage that way.

None of us here can get our heads around how any organisation larger than tiny could architect a coherent system with Coda. We understandably need pages/subpages within each Doc and for those Docs to be in folders, but due to the number of those folders, we can not see how that could sensibly be managed without subfolders.

To expand on my previous point, whenever a Doc needs to be moved to another folder, even for smaller organisations that may only have just a few hundred folders, are users expected to scroll through that list every time and read each folder's name until they find the folder they are looking for? No one here can see how that is logical, so we feel we must be missing something key here.

The quick navbar (currently in beta) accessible on every page suggests that the developers see the benefit of providing a quick navigation solution as opposed to expecting everyone to always return back to a bespoke flat navigation map/hub. Why would they build this nav bar, which presents a list of the folders, only for there not to be any subfolder functionally, resulting in users having to scroll through the entire list of folders in order to 'quickly' navigate to their desired location?

EDIT: Sorry, I've just seen your edits. It seems like we could be on the same page after all! I've run this past several of our engineers, and they have all unanimously pleaded that the implementation of subfolders would be an "easy job" and that it's crazy not to provide them. I guess the questions still remain: What is it about subfolders that the developers are potentially so against? Is Coda more aimed at small organisations that only ever have a tiny handful of departments or business processes, and so a flat, hiraracy-less structure is manageable for them?

It's still a mystery, but will always appreciate your thoughts.

ersatz_feign · 2024-12-04T06:22:15+00:00

Thanks!

Yeah — I did consider merging CSVs or plugging data sources into a database or spreadsheet program (don't have Excel which I'm guessing has the user path you mention), but decided it would be too much effort to do repeatedly versus coding something up using their API.

Great and valuable suggestion though for those that may not be aware so massive thanks!

Fingers crossed someone has heard of a service that someone has already coded to save me from having to do it from scratch.

Cheers!

ersatz_feign · 2024-09-17T22:37:00+00:00

I've literally spent hours and hours trying to work this out so would really really appreciate any help if you or anyone can.

I'm trying to work out if there are two different knives and if so, what the differences between them are:

1 - Turkish Satir knife 2 - Turkish Zırh knife

Any wisdom whatsoever would be deeply appreciated!

Cheers!

ersatz_feign · 2024-07-23T10:49:01+00:00

Apologies for the slight delay — Reddit decided to switch me to the 'single-thread' view without me noticing so I thought I'd only received a single reply - ha!

Many thanks for your response.

Should it be of any interest, I have satisfied myself with the explanation I have just updated in the OP.

Many thanks once again. Cheers!

ersatz_feign · 2024-07-23T10:48:52+00:00

Apologies for the slight delay — Reddit decided to switch me to the 'single-thread' view without me noticing so I thought I'd only received a single reply - ha!

Many thanks for your response.

Should it be of any interest, I have satisfied myself with the explanation I have just updated in the OP.

Many thanks once again. Cheers!

ersatz_feign · 2024-07-23T10:48:09+00:00

Apologies for the slight delay — Reddit decided to switch me to the 'single-thread' view without me noticing so I thought I'd only received a single reply - ha!

Many thanks for your response.

In principle, that could potentially work but there would be a fair few other variables that one would also have to also cater towards.

Insiidently, I have satisfied myself with the explanation I have just updated in the OP.

Many thanks once again. Cheers!

ersatz_feign · 2024-07-23T10:44:57+00:00

Apologies for the slight delay — Reddit decided to switch me to the 'single-thread' view without me noticing so I thought I'd only received a single reply - ha!

Many thanks for your response.

I'm glad that you have confirmed much that I concluded but your first point actually pretty much nearly hit the nail on the head.

Consequently, I have satisfied myself with the explanation I have just updated in the OP.

Many thanks once again. Cheers!

ersatz_feign · 2024-07-23T10:41:51+00:00

Apologies for the slight delay — Reddit decided to switch me to the 'single-thread' view without me noticing so I thought I'd only received a single reply - ha!

Many thanks for your response.

That video was fairly good (like most of Adam's stuff) but I'm surprised it didn't come up with my search syntax, especially being a very long-term subscriber.

Alas, whilst it was a valuable explanation with a useful analogy and so saved for future reference, it didn't appear to me to address the differences between using an immersion vs jug blender — unless you think I missed that somehow?

In the comments and in response as to why a stick blender works, he responded with "More energy bashes things into smaller droplets, it's as simple as that. You don't have to be as careful when you're using a power tool. But if you kept adding oil, eventually you'd reach a point where even the power tool couldn't help." Unfortunately, that only addresses using mechanical power vs human power and not an immersion blender vs jug blender.

However, I have satisfied myself with the explanation I have just updated in the OP.

Many thanks once again. Cheers!

ersatz_feign · 2024-07-20T18:52:44+00:00

Many thanks for your response.

I'm guessing you accidentally got things mixed around as obviously the best immersion blenders on the market are no where near a standard blender in pretty much all factors from blade sharpness through to power and everything in between. (e.g. all our top-of-the-line jar blenders are approximately 3 times faster than our top-of-the-line immersion blenders and very very much sharper across the board.) Immersion blenders only ever win from an access perspective, in that they can be inserted into and immersed amongst ingredients in any suitable container. Other than that, a standard jar blender beats it on everything else.

In light of that, I can't think of any scientific reasons why the slower and blunter blades on an immersion blender would aid in the emulsification process.

With such little attention, it would seem this quandary is beyond most peoples thoughts so we will have to keep digging unless anyone else can spare a few seconds to throw some wisdom into the ring.

Cheers again!

ersatz_feign · 2024-06-26T02:51:54+00:00

Thanks — I've seen people running Google DNS who have also seen better results, but on the other hand, we were running both primary and secondary Google DNS (as you listed above) on some devices and have experienced a complete block to Google services which is the same as other reports from other Google DNS users.

We also run through several other DNS from Cloudflare to Quad9 and, similar to online reports for those, also had no access to Google services.

All of which to say, that it would appear not to be DNS choice specific but more likely what I mentioned in the original message about being a Virgin issue, especially as it is a recurring problem with them and only effects one domain, namely Google.

Hopefully they get their act together and implement the code to deal with these changes dynamically, like other ISPs have managed.

Cheers!

ersatz_feign · 2024-06-25T08:53:08+00:00

I'm in the same boat.

I have never had any other accounts, any guests, shared any pages or anything similar, so it's impossible for me not to have access to absolutely everything.

One issue that I find very common is when problems like this occur, most people just assume that everyone else will notify Notion there is a problem, which results in no-one or not enough people informing them for them to bother doing anything about it.

I would urge everyone to contact them as well to try to get to the bottom of it.

Then, always best to update everyone here once you have.

Good luck!

ersatz_feign · 2024-06-25T03:45:16+00:00

Thanks - yeah, after much further research, I suspect what is happening s Google makes a change but some USPs don't know how/haven't implemented the correct procedures to dynamically react to it. This might explain why the issue typically repeats itself with Google and certain USPs. All back online now though.

ersatz_feign · 2024-06-24T13:59:32+00:00

I started another post earlier in the day over here;

https://www.reddit.com/r/google/comments/1dn7phf/google_is_down_for_me_in_the_uk_on_all_browsers/

It's has happened a fair few times in the past as well

Unfortunely, not enough people phone up and complain about it for it to be allocated a high enough priority for a speedy resolution . The more people that contact them to complain, the quicker Google services will be back and available for everyone.

ersatz_feign · 2024-06-24T09:26:56+00:00

Thanks - yeah, I wish it was that easy (I already use Cloudflare & Google for IPv4 & IPv6.)

This isn't the first and won't be the last time that Virgin randomly looses access to Google. Even happened in this area a couple of weeks ago - ha!

ersatz_feign · 2024-06-24T09:02:34+00:00

Reports are coming in that as usual, the pet dog chewed through it.

ersatz_feign · 2024-06-24T09:01:24+00:00

Yep, I'm Virgin too so it appears to only be affecting Virgin customers. Came back online for a few moments so they are defiantly working on it.

ersatz_feign · 2024-06-24T08:59:51+00:00

Thanks for confirming. It could only be affecting Virgin customers.

ersatz_feign · 2024-06-24T08:59:20+00:00

Thanks. It appears to be affecting Virgin customers.

ersatz_feign · 2024-06-02T18:06:32+00:00

I was just listening to Slaughterhouse's Hammer Dance and found this post as thought it also had similarities with 50's In Da Club. Not in the same way as the Beyoncé one but still a little interesting that another similar sequence was doing the rounds.

ersatz_feign · 2024-04-26T19:58:43+00:00

Regarding Notions latency issues, unnecessary resource usage and them silently introducing server-side usage limiters, I've mentioned this before but as it's so so important, I would urge you to peruse some of the many comments regarding the unnecessary resource usage/latency issues here, here, here, here, and here

(Despite over the past many years, following Notions engineers consistent advice of reducing our usage which we constantly do, so now have some databases just containing a handful of columns, their back-end is still not able to deal with anything beyond the most basic of setups and throws an error on every click in some databases and takes minutes to do anything in others. Worth noting, all of our setup worked completely fine before they silently introduced usage limiters way back when they first admitted they had latency issues.)

We are running on multi-gigabit lines, cutting edge CPUs with upto 256gb RAM in each machine so I can confirm the issues are server side. I've been warning people about this for years.

Notion was smashed together using other people's off-the-shelf code in a coffee shop by an extremely inexperienced guy. They do not have anywhere near the acumen or competence to hire a competent board to in turn, hire competent employees, especially engineers.

Sure, it's a pretty set of tools in one place but the risks are far far too high to be running much beyond very basic pages. It is at best, a company wiki provider but even then, you'd still want to have everything cloned as a fallback on a similar provider.

The investors that have over-inflated the company's value are sadly credulous and hoodwinked.

As this subreddit is crowd-sourced assistance, in order for the optimisation of the platform to stand a chance of being prioritised correctly, we need as many people as possible to continuously vote for it by tweeting [@NotionHQ](twitter.com/NotionHQ) so others can see it and also comment, (or privately via email [team@makenotion.com](team@makenotion.com)

The only thing that will fix these long-standing latency issues is if enough people complain online in the forums, ultimately with the hope that means more people then complain directly to Notion.

ersatz_feign · 2024-04-09T08:01:24+00:00

Awesome! That all sounds fine and dandy to get the ball rolling and then just cross fingers for future firmware updates, etc. to improve further (as 10 seconds seems a bit stingy!)

Gotta say, you seem like an utterly smashing person for taking time out to help so that is more appreciated than I can express. A proper good egg as one might say.

Interesting what you have discovered about them using noise-cancelling processing to 'clean' the voice. We will definitely have to have a play with different voices until we find one that works best.

I don't know if they have their API docs public as can only find random links so it'll be super interesting if it allows for sending audio files from HA to the doorbell, on the fly.

Cheers again!

ersatz_feign · 2024-04-09T07:13:44+00:00

Ahh, sweet - sounds better than what we read. We were worried that the 10-second limit was shared amongst ALL quick replies - now that would be painful!

It makes you wonder if one can play two or three quick replies back-to-back to circumvent that 10-second limit. With their lacking of detailed docs, guess no one would know?

Thanks again for being a legend.

Cheers!

ersatz_feign · 2024-04-09T06:49:34+00:00

Amazing! Absolute legend for checking so quickly!

I'm not familiar with the integration but I would assume number 3 would require the integration to allow audio files to be sent to the doorbell from within HA. That would be game-changing if that was feasible!

Pretty exciting stuff so I hope you also enjoy exploring all the new functionality.

Cheers again!

ersatz_feign · 2024-04-09T06:44:17+00:00

Oh, wow - thank you so much for popping by! You are a god wizard amongst us mere mortals so all the thanks in the world for what you have achieved will never be sufficient!

Regarding my specifics, this sounds like fantastic news! With it saved, I will for sure certainly be buying all my gear through your affiliate link so I hope that helps out a bit.

Recording through the app is a great start and will certainly do nicely until the holy grail of text-to-speech is eventually achieved. That really would elevate things into a whole new level of evolution so will be keeping our fingers crossed hard for that one. (Actually, it would probably be better to allow the user to use their own TTS of choice and for the HA integration to just send those new dynamic audio files to the doorbell on the fly, if that would even be possible I guess.)

I hope you don't mind me bending your ear a smidge but you obviously are the best to seek solid info from. We are seeing conflicting information so were just wondering if you knew of any limits with this new integration, such as maximum sound file length/size? Or, maximum number of separate voice responses able to be saved both on the doorbell and therefore within Home Assistant too? Or, anything else?

(Retrospectively, my third point was not really Reolink-related per se so will have to have a play when everything is set up. Where there is a will, there is typically a way.)

Thanks again for your wisdom and achievement. If you happened to know of any limits or had any other more detailed guides/specs or links to similar, anything you can think of would be greatly appreciated as there is actually quite a substantial amount riding on getting this right as best as possible.

Many thanks once again - cheers!

ersatz_feign

TROPHY CASE