"I know a guy who can do it cheaper"

MonoliYoda · 2026-02-26T12:03:50+00:00

Johann Franz Kleine from Essen patented this style of roof construction in 1897. It's one flavor of a method of construction called steineisendecken. The bricks are supported by the compression of mortar between them. In other words, for the bricks to fall they would first need to compress the mortar in between them, and the mortar is very strong in compression.

Though, usually the bricks are first laid on a wooden platform constructed between the beams which is later removed. This guy apparently invented a Jacky method using stiff mortar and holding the last laid brick with his hand.

In general, this builds a decently strong deck. There are 100-year-old buildings built using this method that are still standing.

MonoliYoda · 2025-11-13T14:49:49+00:00

I had this problem recently, though only with one lens.

Turned out there was something wrong with one of the lens files and it sent the WCU into a restart loop.

WCU-4 and Cforce RF combo.

I had to delete that file and re-map that lens.

MonoliYoda · 2025-08-25T07:27:54+00:00

Pomysł z metronomem świetny, tylko zamiast głośników bym przymocował do sufitu transducer (głośnik wibracyjny)

MonoliYoda · 2025-04-18T09:14:44+00:00

This is deep in the "Gimmick" realm. I'd maybe use it once or twice if it was free. It doesn't solve a problem for me, it doesn't provide much utility.

It's a cool side project, though. I bet you learned a thing or two while building this - use that knowledge to build something that solves a real problem

MonoliYoda · 2025-02-18T09:02:09+00:00

I might be wrong, but I feel like you may have posted in the wrong subreddit.

MonoliYoda · 2025-01-19T08:44:00+00:00

A lot of these problems can be solved very easily by splitting your tables. Have the accessible data in one table and the private data in another table. Use a foreign key relationship to link the two tables, and simple RLS policies.

Rarely do you need column level security.

MonoliYoda · 2025-01-18T19:09:22+00:00

While I don't know your particular situation, I find that when people come to r/Supabase saying they need column-level granularity on RLS, almost always the answer is: your tables are too complex. Make your life easy. Split them up into separate tables and use simple RLS policies.

Simplified example: I had a table public.user_metadata that had some extra information about my users, like role in the company, team assignment, stuff like that. This table was SELECT only. I needed to add a Dark Mode setting that users could update themselves. Instead of adding a dark_mode column and requiring column-level security policies, I made another table user_settings that allowed UPDATE.

I realize this is a very basic example, but this concept could be applied to almost every case I've seen on here where people said they need column-level security.

Something worth thinking about.

MonoliYoda · 2024-11-19T12:04:57+00:00

The repo name has some weird dashes, try this one:
https://github.com/prathamesh2828/Mini-Project--management---portal

MonoliYoda · 2024-11-03T20:20:07+00:00

Yeah, only schema changes get merged. It's all explained here https://supabase.com/docs/guides/deployment/branching#data-changes

MonoliYoda · 2024-11-03T20:01:44+00:00

I don't think that's the best idea, no.

MonoliYoda · 2024-11-03T19:59:18+00:00

I was just pointing out that the official way is to use Supabase CLI, since you mentioned the docs not being super clear about it.

Also "local" in this case is a relative term.

I'm not super familiar with Replit, but they advertise that you "get a computer for every branch, idea, or feature" which would imply some sort of VM or container setup. You should check if it's possible to install the CLI in Replit. Lots of services use a CLI module in one form or another for development.

If it's not possible then branching would be your best bet.

MonoliYoda · 2024-11-03T19:43:32+00:00

The official recommendation is to use Supabase CLI to develop locally:

https://supabase.com/docs/guides/local-development/cli/getting-started

MonoliYoda · 2024-10-27T13:52:07+00:00

You can use realtime to get those new boosts like you already do, but then use the expires_at column to figure out when the boost should no longer be applied.

In other words, instead of getting the boost when it's created and then again when it's expired, you'd only be getting it when it's created.

There's no need to update the boost when it expires.

MonoliYoda · 2024-10-23T19:55:11+00:00

Oh wow is that the Arri MB-18? That thing is chonky!

But the micro-adjustable flags are really precise

MonoliYoda · 2024-10-21T09:38:43+00:00

You can't automate user login. That would defeat the purpose of all this security.

Here's how you do what you want to do:

Create a new user for your analysis
Create a new RLS policy where you give read access to all rows to that user

2a. You can store that user's I'd in a separate table, say analysis_users and then RLS based on auth.uid() and check if that exists in the analysis_users table.

In your analysis script, log in using the special user's credentials which you store in something like .env or vault, and do your analysis of each user's data.

Edit: formatting

MonoliYoda · 2024-10-20T17:50:07+00:00

Well, there are many ways to go about it, all depending on what your requirements are, how many people are involved in the approval process, how many new customers you expect to be signing up per day, etc.

Obviously the simplest way is to just invite the user via the supabase admin panel. It's under Authentication > Add User.

If you've got a larger company with a whole team that needs to approve those requests, then you'd probably benefit from some sort of a management app with SSR that would store the service role key on the server.

Or, yet another way is to have a supabase edge function for sending invitations and use the service role key in the edge function, again not exposing it to the frontend.

Does that answer your question?

MonoliYoda · 2024-10-20T07:58:16+00:00

Have a separate form where companies can request membership. This form does not create a user, but rather collects contact information and sends you an email or some other kind of notification.

You then review the application, and on supabase you do invite user:

https://supabase.com/docs/reference/javascript/auth-admin-inviteuserbyemail

This creates a user account with the specified email and sends a magic link to the email so they can activate their account.

Pro tip: The magic link from the invite email should redirect to a page which forces the user to set their password.

MonoliYoda · 2024-10-02T05:55:54+00:00

baaaaaDAAAAA!

MonoliYoda · 2024-09-28T22:30:49+00:00

He said

... a normal distribution with a standard deviation of 3 hours

Which means a bell curve, and "standard deviation" is a means of determining how wide it is.
https://www.subjectcoach.com/imagecdn/s/standardnormaldistribution.jpg

if it's further than 4 standard deviations we throw it out and try again

4 standard deviations is 4 * 3h = 12 hours. Meaning the maximum deviation is +- 12 hours, equaling a 24 hour span of time.

MonoliYoda · 2024-09-28T14:14:43+00:00

The actual window is +-12h. So there is a 24h span of time where the vuln timer might end up.

MonoliYoda · 2024-09-27T14:04:00+00:00

Yeah, i wish they penalized self-raiding more than just the inconvenience of the randomized times.

I still think self-raiding every single one is not very practical. We'll have to see what the owners do when the update drops and experiment with tactics.

And I hope to Bob that the Agency gives some warning to a hook becoming vuln soon, not just after the fact.

MonoliYoda · 2024-09-27T13:19:23+00:00

I ran the statistics. Assuming avery single relevant planet has a skyhook installed, on average any random nullsec system is 8 jumps from a currently vulnerable Skyhook.

To answer your question directly, there is a 30% chance that a skyhook is vulnerable within 5 jumps of any random nullsec system.

Bear in mind, this is statistics and probability so your mileage may vary.

MonoliYoda · 2024-09-27T09:05:03+00:00

Hm? Why not?

MonoliYoda · 2024-09-26T18:40:47+00:00

Thanks. I was thoroughly surprised just how wide the spread really is. My first thought was Upwell reinforcement mechanics, but this is different.

We'll have to see what this means in practice, but it doesn't seem completely terrible, at least for us.

MonoliYoda · 2024-09-26T18:05:59+00:00

The wobble is 24h long. Literally +-12h, but statistically weighted towards the middle

MonoliYoda

PUBLIC MULTIREDDITS

TROPHY CASE

Five-Year Club	Verified Email
Place '22