@movq@www.uninformativ.de Me too! I don’t play as much as I’d like to 😢

@off_grid_living@twtxt.net Didn’t Google scan loads of books from Public libraries? 🤔

@stigatle@twtxt.net Truly amazing shot 👌

@abucci@anthony.buc.ci Yeah like I said it’s being worked on slowly 🤞

@bender@twtxt.net I hope my pod never becomes that popular, I’d rather see other pods start to amas more interesting users and build a stronger community over time 🤣

@abucci@anthony.buc.ci Could you please file a bug for @xuu to look at, this smells like a bug in the go.yarn.social/lextwt parser 🤔

@abucci@anthony.buc.ci This is quite hard to do really. Because the “web app” is a server-side rendered (SSR) app. Mobiles Apps are not normally written this way (in fact they never are). They are two very different code-bases, which is why we spend a lot of effort on the client and the API. On a side note, I’m also working in parallel on a way to “embed” Go code (as a client) in a Flutter App in the hopes for more reusability for Salty.im – If we can pull that off, it’ll also help improve the reuseability of client features and improve on keeping things DRY for the Yarn.social app 👌

@abucci@anthony.buc.ci That’s the part that puzzles me the most. It’s as-if these spam buts just don’t know how to Yarn 😅

Pinch and a punch for the first of te month! 👊

@abucci@anthony.buc.ci LOL I swear to god these are spam bots, if only we could find out what 🤣

@abucci@anthony.buc.ci Hmm this is true, sadly. Are you able to file a feature request for this? It’s just a missing feature 🙏

Pinch and a punch for the first of the month 👊

Pinch and a punch for the first of te month! 👊

@akoizumi@social.chaotic.ninja Just stick to Yarn.social 😆 It’s better for your health 😅

@bender@twtxt.net I think I might actually follow all three of his accounts, so I hear you’re actually correct in this case. 😆

also need to talk to you about the other case that you discovered that I promised I will try and fix, which I realized I wasn’t completely 100% sure what was going on 🤦‍♂️

remember my goals for this year? To get the mobile app finally released to production with all bugs and improvements addressed? 🤔

@bender@twtxt.net Because the mobile app has a different reply thank you that needs to be fixed. It’s a non-problem and documented as a bug.

@screem@yarn.yarnpods.com Don’t know of any myself. e2e IRC encryption is not that common in my experience 😢

Anyway, even if I did, which I’m sure I did, it wasn’t intention to say that I hate all SQL database outright, but rather my inner rage in this case comes from developers far too often reaching for that shiny *SQL database (doesn’t really matter what it is), only to discover when you go looking under the covers at the source code and what data is being stored, accessed and manipulated, it could. have been done with a simple embedded KV store or even a SQLite database. But no, instead, you have to worry about this extra component 🤦‍♂️

As a big proponent of self-hosting, I find this an anti-pattern.

@abucci@anthony.buc.ci Where did I hate on SQL databases? 🤔

@abucci@anthony.buc.ci Maybe maybe not. Depends on what you’re doing I guess. For small things I find simple things are better anyway. KV, flat files, a log, etc.

@abucci@anthony.buc.ci 👌

a large part of this comes from experience, dealing with databases, and SQL many times in the past, and then eventually coming to the realizing that everything is basically key value, stores, bloom filters, trees*, tries and various types of indexes and caches.

For me personally I find it far easier to reason about the data I’m dealing with, what forms it needs to take and what to do with it.

@marado@twtxt.net TIL – Knew about talk though 😆

@akoizumi@social.chaotic.ninja Oh dear 🤦‍♂️

@screem@yarn.yarnpods.com 👌

@johano@gem.chiajlingvoj.ynh.fr sorry we haven’t made a new release in a while. Hopefully soon. 🤞

@eldersnake@yarn.andrewjvpowell.com that’s the only thing I can think of – which we do on the backend anyway for our server-side-rendered web app (SSR)

I really don’t understand why I’m getting such a hard time from y’all over my choice of database(s) and data storage/retrieval solutions in general 😢 Why? 🤔

@screem@twtxt.net Hey hey! 👋 INce to see you again and good to know you’re doing okay 👌 – We should maybe catch-up for a beer or something since we’re now geographically close to one another 🙏

@abucci@anthony.buc.ci Without Javascript you say? Hmmm? 🤔 How? (unless we’re tlaking about the same thing in different ways…)

@bender@twtxt.net fetched on demand, implies some kind of client-side JavaScript; so probably not.

However, there is another way that we talked on IRC last night…

Which again leads to searching and indexing the archive 😆

Not gonna happen 😆 But thanks for trying 🤗

@eldersnake@yarn.andrewjvpowell.com Yes yes they are 😆

Thanks god for muting hashes 😅 Had to mute that Twt, didn’t want to see that garbage in my Discover 🤣

@eldersnake@we.loveprivacy.club Sorry, @lyse@lyse.isobeef.org just pointed out to me on IRC at some ungodly hour this morning (woke up for some reason) that all my arguments are flawed 🤣 Regardless of my experiences and reasoning, I prefer to use bitcask for most things “dadtabase”(ish) and the “right data structures” for things I’m working with, be-it a key/value store, in-memory hashmap, write-ahead-log(s), indexes, etc. Perhaps I find it more comfortable and easier to use lower-level libraires to solve the same kinds of “data” needs.

@abucci@anthony.buc.ci That’s okay 😅 You don’t have to in order ot enjoy the software 🤣 I just have to pay attention to you and the community and not build or break shit people don’t want 😝

@johano@twtxt.net I think I fixed a couple of bugs in this commit – If you wouldn’t mind giving this a whirl and updating your yarnc binary? 🤔

@abucci@anthony.buc.ci Been a feature for a few years now 🤣

Also you’ve either a) not configured smtp on your pod or b) never received a “Candidates for deletion” email (yet) 😅

@abucci@anthony.buc.ci fair, I feel the same, probably why despite good heuristics (which is what that value is) I’ve never done it 😅

@jlj@twt.nfld.uk I had a similarly named account register on my pod as well. Posted NFT SPAM as well. Nuked it instantly (well I woke up for some reason 😅)

No thank you. This is not the place for you (SPAM posted!)

@abucci@anthony.buc.ci Regarding:

verify their email address

Do we want this? Would it help? We can verify email addresses without ever storing it, like we do now. Just send the email, wait for the “token link” to be opened/verified, then activated account.

@abucci@anthony.buc.ci +1 on “non-user-hostile captcha”

@abucci@anthony.buc.ci I’d like the pod to automatically nuke inactive accounts/feeds. Are you open to that? I think internally there is enough data to go on (whether the user updated their avatar, whether the user updated their description, whether the user actually posted anything at all, etc) if you’ve seen a “Candidates for deletion” email, those cores are based on nthis. Anything above a 2000 are “sfe to nuke” in my experience.

@abucci@anthony.buc.ci Yeah so if we also include mobile phone in that category, then I guess I haven’t used the “telephone” system in some decades now actually. One thing that happened in Australia when NBN was deployed was people lost their “landline” (the old telephone POTS system) and it got replaced with a VOIP system (digital) – I just always refused as I could run VOIP myself anyway, so I didn’t see the point 😅

@johano@twtxt.net Let me verify something on a local dev pod an get ack to you?

@eldersnake@we.loveprivacy.club Several reasons:

• It’s another language to learn (SQL)
  
• It adds another dependency to your system
  
• It’s another failure mode (database blows up, scheme changes, indexs, etc)
  
• It increases security problems (now you have to worry about being SQL-safe)
  

And most of all, in my experience, it doesn’t actually solve any problems that a good key/value store can solve with good indexes and good data structures. I’m just no longer a fan, I used to use MySQL, SQLite, etc back in the day, these days, nope I wouldn’t even go anywhere near a database (for my own projects) if I can help it – It’s just another thing that can fail, another operational overhead.