Things I learned after getting users • Hacker News Board

Re: Things I learned after getting users

#151

Post by wahnfrieden » Thu, Mar 16, 2023, 1:35 AM UTC

t11hrow wrote: post #137

wahnfrieden wrote: post #134

Earlier quoted context omitted.

I have a lot of thoughts on this that I plan to start writing on under indiedevstack.com before long, for now you can follow my one biz social where I will promote it once ready @manabiSRS But some quick references... One approach is to avoid algorithmic surfacing of UGC outside of one's own network (or secondary connections etc), which makes discovery harder (must be compensated in other ways). Twitter may explore s…

Hey man, thanks. Really interesting. I've added indiedevstack.com to my bookmarks, so I'll check in that once you've launched

Cheers, good luck with your own work

Re: Things I learned after getting users

#152

Post by watwut » Thu, Mar 16, 2023, 9:05 PM UTC

manv1 wrote: post #144

watwut wrote: post #114

Earlier quoted context omitted.

Ad2: Every single real world java project I have seen used hibernate (ORM) with flyway. I never ever seen any project in production where some underlying tech would be deleting tables autonomously. Ad1: People do debug ORMs, actually. Including queries effectivity.

Ad2 -> I've run into lots of hibernate apps. They also tend to use Spring, and the team often gets lost trying to figure out which one is the cause of the problem. It's usually both. Hibernate and Prisma migrations will delete tables if you allow them to. Ad1 -> I'm sure they do...but usually they call in a DBA, who basically says "this is a disaster" then recommends that they refactor everything because their databa…

I dont find neither of your responses consistent with reality. First, database administrators do not debug ORM. Second, it does not take specialist to debug those, developers debug those. Third, recommendation is rarely "refactor everything". Usually it is adding an index, change the query or some other minor tweak. Fourth, "weird object hierarchy instead of RDBMS principle" does not even mean anything.

Fifth, spring has nothing to do with database whatsoever. Sixth, every production code I have ever seen used flyway.

Re: Things I learned after getting users

#153

Post by gloosx » Fri, Mar 17, 2023, 7:04 AM UTC

The best way to deal with point one – ghosting. Feeling sorry to see 3 greatly ineffective, and 1 desperate method to get rid of the abusive spammer. I had experience with the community-driven portal, and trust me - the best way to exhaust the spammer - hide his posts from others - don't give him a single clue you acted on him, just let him continue posting in a special vacuum prison crafted exactly for him.

Re: Things I learned after getting users

#154

Post by eks391 » Fri, Mar 17, 2023, 9:22 PM UTC

mcstempel wrote: post #41

> this worked for a little bit longer, but he proceeded to get on a VPN, and then another when i blocked that IP, then another when i blocked that IP, etc, etc. Beyond VPNs, I've even seen attackers leverage residential IP networks which makes VPN detection ineffective as well [1]. If you ever need a more permanent identifier to ban users on, consider using a device/browser fingerprinting tool [2]. It helps avoid the…

Although difficult and not well known about, fingerprinting can be randomized[1]. I have been successful creating a random fingerprint on only Brave so far, but I did need to tweak some browser settings.

1 check your fingerprint details here: https://coveryourtracks.eff.org/

Re: Things I learned after getting users

#155

Post by closeparen » Sat, Mar 18, 2023, 4:35 PM UTC

ilamparithi wrote: post #135

closeparen wrote: post #109

Earlier quoted context omitted.

I'm happy to write my own SELECT queries, but it sucks to be manually schlepping row[0], row[1], etc. into the fields of my domain entities, or making sure I provide the parameters to the parameterized INSERT statement in the right order. ORMs usually let you drop down to SQL as desired, and I do that when I have a nontrivial query to express, but CRUD plumbing is nice.

Not sure which programming language you are using. For Java, I find Spring JDBC templates with Row Mappers more productive than ORMs. DataClassRowMapper will automatically populate the domain entity.

Go, Java language-level 8, Python. All have an approach, usually with some third party library, but the bone stock database drivers deal in field indexes. And people consider those libraries "ORM" whether or not they really are technically.