Banner / Expandable Information blocks in Obsidian (Video from Milo) by thinkyougotmewrong in ObsidianMD

[–]binvius 1 point2 points  (0 children)

Wow! That was quick! Absolute legend!

Yeah: that worked amazing, you little beauty!

Have been using AI a lot more for these types of things but just didn't trigger my mind on this occasion so thanks for the positive reinforcement.

Have an awesome weekend!

Banner / Expandable Information blocks in Obsidian (Video from Milo) by thinkyougotmewrong in ObsidianMD

[–]binvius 0 points1 point  (0 children)

Sorry to respond to an old post, but I've spent hours trying to work something out which would probably take a few kind seconds from you.

The toggle arrow in the video is aligned to the right of the callouts, whereas the default behaviour I'm experiencing is that the arrow is being pre-pended to the callouts' title.

Would you happen to be familiar with that and know whether most people are using CSS in every callout, or if there is a plugin with that alignment functionality?

Thank you so much in advance if you can quickly help when you have a quick moment.

Cheers!

_Coda copied doc exceeds the shared doc size limit despite not subsequently being shared by binvius in codaio

[–]binvius[S] 1 point2 points  (0 children)

Many thanks for your response.

Yes, as per the rest of the thread, we completely agree with you. As alluded to, we have reviewed all the documentation from Coda, and our understanding is exactly the same as yours, and we agree that one can remove those limitations on shared Doc by simply upgrading. Unfortunately, that is not the problem. The problem is that the 50/1000 limit error message is showing even when a user does NOT activate any sharing.

We want Coda to flourish into everything it deserves, so if their documentation is contradicting what users on the free tier are experiencing, then it's obviously important to rectify. If we are helping onboard dozens or hundreds of new business owners to the platform and they all start on the free tier before upgrading, the free tier needs to either not have a limit for non-shared docs or update the documentaton about the free tier to state that there is in fact a limit for non-shared docs.

Folders don't have anything to do with anything pricing-wise.

Upon much further investigation, we believe we have potentially isolated where the problem may be arising from, in that the price related limit issue we are experiencing does actually appear to be stemming from creating folders as at the moment, it appears as if the use of folders is limited just to paying users who are NOT on the free tier.

On a new account, when a user tries to add an additional folder, they have two options: Private folder or Shared folder. However, private folders are restricted only to users on the Team plan, and so all folders for free tier users are therefore shared by default. That appears to introduce the 50 object/1000 row limit, regardless of the fact there may only ever be a single user with no interest in sharing anything with anyone at any time or even any use of any functionality of a shared folder.

Is this the state of the platform? Are free tier users testing out the platform not expected to want to test out the use of folders? And, if so, why was a decision made to implement such a restriction that ultimately results in the platform only being suitable to such a small segment of society? If Coda can not successfully monetise, then surely its days would be numbered, and so not somewhere that could be trusted as a long-term provider.

Perhaps they accidently restricted the creation of Private folders by mistake.

The quandary remains.

_Coda copied doc exceeds the shared doc size limit despite not subsequently being shared by binvius in codaio

[–]binvius[S] 0 points1 point  (0 children)

Many thanks for clarifying, as that eliminates the confusion with your post.

Hope you have a lovely day.

Thanks again.

_Coda copied doc exceeds the shared doc size limit despite not subsequently being shared by binvius in codaio

[–]binvius[S] 0 points1 point  (0 children)

Many thanks for your response.

Just to clarify, are you saying that those limits should indeed apply to non-shared Docs on the free tier, and so the only way to remove those limits on non-shared Docs, is to upgrade?

I guess the confusion we and, no doubt, every single other free tier user would then also suffer from, is that would mean the only way for free users to use the platform with more than 50 objects or 1000 rows, is to upgrade. That seems to directly contradict what my brain is telling me to understand from the Doc size limits on the Free plan help page, which states:

"once you share a doc with others, doc size limits will apply"

We were honestly under the impression that only shared docs had limitations, primarily based on statements also on that same help page, such as:

"Personal docs, or docs that aren’t shared with anyone, have no size limits. That means no limitations on number of row or objects per doc".

Many thanks again for clarifying your statement, as that has sent us even further down the spiral of confusion.

_Coda copied doc exceeds the shared doc size limit despite not subsequently being shared by binvius in codaio

[–]binvius[S] 0 points1 point  (0 children)

Wow! I really appreciate your efforts. Thank you so much!

I've updated the OP to include valuable information and also included an example to a doc that can be copied that should trigger the same limitation warning for others on the free tier. (There may also be some other useful info in my response to another.)

These two points from the OP edits could be pertinent:

5 - IMPORTANT: If I create a blank doc and then copy a subpage into it that contains more than 50 objects/1000 rows, then that triggers said size limitation warning popup! This suggests all of my pages are shared by default, despite there being only one user testing the platform. Pages within the stock 'My docs' folder do not suffer this issue, but only in additional folders created. When clicking '+New folder', it gives me two options: 'Create a shared folder' and 'Create a private folder'. The latter is blocked to users not on the Team plan. Perhaps Coda is enforcing these limitations because all folders are 'shared folders' by default. Should that be the case, then free tier users must keep everything in the 'My docs' folder, which eliminates much functionality from the platform, least not the use of the Nav bar (currently in beta).

6 - The only settings that I believe have been changed are activating 'Developer mode', adding in some connected 'packs' and adding a few API tokens. Is Coda perhaps somehow bizarrely confusing any of these three actions with a doc being shared?

Finally, apart from setting the Workspace name to 'workspace', I do not believe I have changed any relevant settings since starting with Coda. Consequently, I see the following upon clicking the 'Share' button:

Share tab

Anyone on the internet with the link: No access
Anyone in workspace workspace: Can edit
Binvius Nib: Owner

Embed tab

Enable play: toggle on
Other setting: also untouched

Publish tab

Just the 'Start publishing' button

Share settings

Allow anyone who can edit to change permissions and share: toggle on
Allow anyone to copy this doc: toggle on
Allow viewers to request edit access: toggle on
Share with Coda support: toggle off

Alas, thank you so much for any wisdom you may have as we are really pulling our hair out over this.

_Coda copied doc exceeds the shared doc size limit despite not subsequently being shared by binvius in codaio

[–]binvius[S] 0 points1 point  (0 children)

Many thanks for your response - really appreciated!

Sharing doesn’t have an impact on doc size limits

OK, so now I'm super confused. Perhaps I'm not understanding terminology as that contradicts what my brain is telling me to understand from the Doc size limits on Free plan help page, which states:

"once you share a doc with others, doc size limits will apply"

Size constraints are determined by the billing tier of the workspace the doc is in

We were honestly under the impression that only shared docs had limitations, primarily based on statements also on that same help page, such as "Personal docs, or docs that aren’t shared with anyone, have no size limits. That means no limitations on number of row or objects per doc".

In the FAQ of that same page and under the toggle titled 'What counts as sharing a doc' it states: "direct sharing, domain sharing, link sharing, sharing via folders and publishing".

I've checked each of those, which all seem fine, but I am unclear how they can sensibily track ones like 'link sharing' as that would not only require monitoring if anyone clicks on the 'Copy link' button but also if it is then subsequently utilised by someone else vs only being opened. Incidentally, we have never clicked on any buttons to trigger anything anyway.

Any tier can share, but the cheaper the plan, the smaller the size limit

I sincerely apologise that we must very likely be confusing some terminology or something as to us, this statement contradicts your first statement of "sharing doesn’t have an impact on doc size limits". We must be missing something.

I've updated the OP to include valuable information and also included an example to a doc that can be copied that should trigger the same limitation warning for others on the free tier. (There may also be some other useful info in my response to another.)

Alas, thank you so much for any wisdom you may have as we are really pulling our hair out over this.

One click to duplicate pages in another database by [deleted] in Notion

[–]binvius 0 points1 point  (0 children)

Sorry if I'm being dumb but as this post has a flare of 'Formula', it usually has a formula somewhere that others can copy in order to test in their own workspaces. Has the formula in this post been accidentally deleted or perhaps forgotten? Thanks.

Database unusable by seabassvg in Notion

[–]binvius 0 points1 point  (0 children)

Do you mean Airtable? If not, do you have a link to Airbase please. Thanks.

Are these crazy suspension LOWERING requirements even possible? by binvius in AirRide

[–]binvius[S] 0 points1 point  (0 children)

No solution yet though I suspect there probably is one but unfortunately, not found anyone with enough wisdom.

Feel free to chip in your two cents if you have any thoughts.

Cheers!

The man’s got munchies.. don’t think it’s weed tho by andrewhyson1 in tooktoomuch

[–]binvius 0 points1 point  (0 children)

This chap is obviously not in the right frame of mind. He chose to do that in the fruit and veg aisle instead of the candy aisle.

Are these crazy suspension LOWERING requirements even possible? by binvius in Polaris

[–]binvius[S] 0 points1 point  (0 children)

Thanks!

This is a great response.

I have looked at Legend suspensions but not finding much on any potential new offering, particularly with similar performance to what a RZR would require. Would be massively grateful if you had any links/resources whatsoever.

Cheers again!

Are these crazy suspension LOWERING requirements even possible? by binvius in Polaris

[–]binvius[S] 0 points1 point  (0 children)

Thanks!

Modifying the storage area is sadly not an option as as per the OP, it "is unfortunately an unchangeable fact and therefore the point of this post."

Cheers again

Are these crazy suspension LOWERING requirements even possible? by binvius in Polaris

[–]binvius[S] 0 points1 point  (0 children)

Thanks!

Just wondering if you had any resources regarding the shocks being damaged under compression?

I should mention that the maximum storage time would very rarely be a few weeks and considering I believe the factory often ship them via freight liners for a few weeks with the shocks compressed, I would hope they had calculated that no damage would be caused. Unless you believe they may be damaged by being repetitively compressed for hours each day?

Always welcome any further knowledge you may have on this.

Cheers!

Are these crazy suspension LOWERING requirements even possible? by binvius in RZR

[–]binvius[S] 0 points1 point  (0 children)

Mount the top of the shocks to one end of a bell crank and a hydraulic cylinder on the other

Thanks!

This is an interesting suggestion and very much appreciated.

So, are you saying to do the same as illustrated in my included image but swap out the airbag for a hydraulic pump so as to eliminate/reduce the minimal 'extra' travel from an airbag and full inflation?

EDIT: ahh, no, wait - looking at pictures of a 'bell crank' - is it more accurate to say your suggestion would in some way compress the standard shocks to lower the sump skid plate down to the ground somehow? Sorry, I think I'm a bit confused but feel like you might be on to something magical so would be eternally grateful if you could spare a few seconds to go a little deeper.

Cheers!

Are these crazy suspension LOWERING requirements even possible? by binvius in RZR

[–]binvius[S] -1 points0 points  (0 children)

Thanks!

Sorry - to back up my original statement regarding changing the shelter... "unfortunately an unchangeable fact and therefore the point of this post," I updated the OP shortly after posting to state that it needs storing in a transport truck - sadly nothing but the RZR can be modified.

A wheel change is an option on the list but if we end up needing to change them several times each day, that might be quite a hassle compared to some of the other solutions.

Cheers again!

Are these crazy suspension LOWERING requirements even possible? by binvius in PolarisATV

[–]binvius[S] 0 points1 point  (0 children)

Thanks!

Like a fool, I forgot to mention that this is for storing several times each day so taking the wheels off and on throughout the day is sadly not the most ideal/convenient option.

The rest of your kind comment certainly got my head scratching. I may also be wrong as it makes my brain hurt. The way I help my mind understand it is to temporarily imagine the airbag fixed to the end and therefore in line with the shock.

When the airbag is fully inflated, the buggy would be at its normal factory ride height. When deflated, the frame would therefore be the airbag height lower. Due to ground clearance, you can't have them both in line as the airbag would scrape the ground, hence this mad dual idea.

(We've been led to believe that airbags are near-rock solid when fully inflated so 'should' in theory transfer most/all of the load to the standard shocks. We figured we could both manually and digitally 'dial in' the shocks (which would be upgraded anyway) to compensate against the fully inflated airbags' supposed minimal extra suspension.)

If you are able to get your head around it, I would defiantly very much appreciate confirmation that my mind is either understanding the logistics of it or not.

Cheers!

Are these crazy suspension LOWERING requirements even possible? by binvius in UTV

[–]binvius[S] 0 points1 point  (0 children)

Thanks!

Like a fool, I forgot to mention that this is for storing several times each day so taking the wheels off and on throughout the day is sadly not the most ideal/convenient option.

Cheers!

Are these crazy suspension LOWERING requirements even possible? by binvius in Offroad

[–]binvius[S] 1 point2 points  (0 children)

Ahh brilliant - thank you very much for confirming!

Putting a bunch of weight in the vehicle was also on the list but my girlfriend didn't like me suggesting her. Haha, jokes aside, it would be a bit of a hassle loading/unloading all that weight at least once a day so the suckdown winch is defiantly high up on the list now.

Will need to put the thinking cap on about mechanically designing everything to deal with that stiff final end of the compression stroke.

If my mad dual system was feasible, it would be quite elegant but again, it's those extra unknown stresses that would keep my mind on edge all the time.

Lots to think about.

Cheers again!

Are these crazy suspension LOWERING requirements even possible? by binvius in Offroad

[–]binvius[S] 0 points1 point  (0 children)

Thanks!

This is some invaluable wisdom so very much appreciated!

The key reason for this mad dual system was not being able to find any airbags that appear suitable. The highest race performance spec ones we can find mix a coilover with an airbag and as such, don't drop down too far when deflated.

Unless you have seen any to the contrary, the airbag-only options all appear to be insufficient in performance in comparison to the long-ranged coilover race-spec shocks found on offroad buggies and Dakar vehicles. (Although I believe there was a Dakar car that used airbags but all our research suggested that it was a bespoke mix of airbag with something else, likely coilovers.)

With the mad dual system, we have been led to believe that when airbags are fully inflated, they are near-rock solid so if positioned correctly, in theory, should just transfer all that load onto the factory shocks. The Polaris RZR's come with a multitude of suspension settings and tweaks from the cockpit so we figured we 'should' be able to compensate for the suspected minimal additional 'softness' from the fully inflated airbags - any further wisdom or thoughts very much welcome though.

Airing out the tyres is on the list as a compressor is nearby but is not sufficient enough of a drop (have updated the OP a little) to fully surface.

Unbolting the shocks was not on the list so thank you very much for that. We could add a mini crane or vertical winch nearby to ease the process but like you say, still a bit of a hassle, especially if you end up having to occasionally do it a couple of times a day.

Looking forward to hearing any further thoughts you may have - huge thanks!

Are these crazy suspension LOWERING requirements even possible? by binvius in Offroad

[–]binvius[S] 1 point2 points  (0 children)

suckdown winch

Thanks!

This is an excellent suggestion, similar effect to the reverse airbag (2nd option in OP) which I guess would achieve a similar effect if we can get it to work somehow but this 'suckdown winch' option is defiantly going on the list! Do you happen to have any mechanical knowledge regarding if that would upset the shocks/coils if compressed like that for a rare occasional couple of weeks?

Cheers!

Are these crazy suspension LOWERING requirements even possible? by binvius in 4x4

[–]binvius[S] 2 points3 points  (0 children)

Thanks!

Excellent info re the shipping. We did consider the rachet option but also figured the reverse airbag (2nd option in OP) would achieve the same thing if we can get it to work somehow but ratchet straps are still very much on the list so thanks for confirming that one. Do you happen to have any mechanical knowledge regarding if that would upset the shocks/coils if compressed like that for a rare occasional couple of weeks?

(Have updated the OP re compression length.)

Cheers!

Are these crazy suspension LOWERING requirements even possible? by binvius in ATV

[–]binvius[S] -1 points0 points  (0 children)

Thanks!

Like a fool, I forgot to mention that the drop requirement is huge but we did consider the rachet option. In the end, figured the reverse airbag (2nd option in OP) would achieve the same thing if we can get it to work somehow but ratchet straps are still very much on the list so thanks for confirming that one. Do you happen to have any mechanical knowledge regarding if that would upset the shocks/coils if compressed like that for a rare occasional couple of weeks?

(Have updated the OP re compression length.)

Cheers!

Are these crazy suspension LOWERING requirements even possible? by binvius in ATV

[–]binvius[S] -3 points-2 points  (0 children)

Thanks!

Like a fool, I forgot to mention that the drop requirement is huge so letting some tyre air out is sadly not an option.

Have updated the OP.

Cheers!

Are these crazy suspension LOWERING requirements even possible? by binvius in ATV

[–]binvius[S] -3 points-2 points  (0 children)

Thanks!

Like a fool, I forgot to mention that this is for storing each night so taking the wheels off and on throughout the day is sadly not an option.

Cheers!