Untitled attachment

Notices where this attachment appears

1. Embed this notice
   Thanasis Kinias (tkinias@historians.social)'s status on Sunday, 14-Sep-2025 02:42:17 JST Thanasis Kinias

   Are there any #histodons still on here?

   I’ve not been very active recently since I was spending a lot of time on Bluesky—where most of my old Twitter community ended up. I’m not sure how much longer that’s going to be a viable place, though.

   As luck would have it, though, just as I’m committing to spending more time here I just learned that my server will be shutting down next month and I need to find a new Fediverse home.

   Any suggestions?

2. Embed this notice
   pwm (pwm@darkdork.dev)'s status on Tuesday, 01-Jul-2025 06:46:55 JST pwm

   in reply to

   @Pi_rat @p @SuperDicq

   I had read about autoincrement being slow but I thought alternative to it would be me generating unique ids myself. I will fix code to use rowids.

   I may have not made myself clear here, you need not fuss with rowids yoursefl, you may simply use integer primary key

   I thought it would be optimized. I will refactor around this. I was going for dicts since qmark style is going to be deprecated (and as furthur along you have said, I agree dicts are cleaner)

   This is a good intuition! In other database drivers (psycopg2 for example), executemany is optimized.

   As you have pointed out, Im thinking of upsert syntax to just ignore duplicate inserts. Originally I was trying to figure out a way to have "SELECT id FROM images WHERE image IN ?" and I tried every combination of qmark and dicts but it was no dice but could be done with string formatting, but I rather not use it since Im doing parametrized queries everywhere else, that would be bad.

   Good catch here, I don't know how I missed using upsert here but you're absolutely right, this is a good use case for it.

   Ah yes I have autocommit turned on as long as there are no exceptions, I will add explicit commit. I was not even closing db mistaking that context manager will handle closing it for me. Just learned today that I have to close cursor too.

   When you use the actual python context manager syntax,

   with sqlite3.connect("yourdb.sqlite") as db: with db.cursor() as cursor: do your query etc etc ... here the cursor is now closed db.commit() here the database connection is now closed

   In this case, the python context manager will automatically call the appropriate close function as you fall out of the indented block. If you do it in the imperative style you have been doing you must call close() on each cursor and database connection yourself. In a purely technical sense, all that is being cleaned up when the program exits, and this is not a long-running server process. But it's good practice to use either of these two methods to keep things tidy yourself. Many other objects use this protocol iirc you used it when opening and reading a file.

   Is it correct to use "sqlite3" directly and using functions and passing cursor around them, writing sql statements inside function. Im not sure if there is standard way to do this but personally it seems off.

   You may pass the connection or cursor object in a function call. However, things get hairier if you start to multithread or multiprocess. sqlite3 module objects are not threadsafe and you will get programming errors if you try to use e.g. a cursor outside of the thread it was created in. This is not really a relevant concern here, though.

   As for code style, it might be slightly "cleaner" to pass the database object to functions that use the database, create a cursor for the scope of the function, and close the cursor before you return. This will still alow the callee function control over, e.g. committing to the database in case of a DML statement.

   Since python is OOP shouldnt I be creating classes and adding methods? i.e (cursor.select_image(image_id) == cursor.execute("SELECT image FROM images WHERE id = ?", (image_id,))

   It is bad practice to attach methods to objects after the object is instantiated, which is what you would be doing were you to do as you stated in this example.

   I wouldn't get too caught up in trying to follow any particular paradigm here, your codebase is small and it's a for-fun project. Short of using an ORM to abstract away handling the database connection, carefully passing a connection object around is a-ok, and what the ORNM is doing under the hood, anyway.

   I LOVE sql(ite) and will read all the Docs you have linked with fervour. Thank you VERY much for giving such detailed review. I will follow you up when I implement queries.

   You're welcome! SQLite is one of my favorite pieces of software, too, if you couldn't tell! I'm a sql and python guy so I'm happy to help out and had fun reading through this and providing commentary today.

3. Embed this notice
   RealZero (bryangreyson@social.tchncs.de)'s status on Friday, 25-Apr-2025 15:04:32 JST RealZero

   in reply to

   @Fragglemuppet Very curious answer:

   The more I encounter it in the last few months, the more I get used to READING it, as in, I accidentally learn more of which Braille is which letter or number if I SEE it. Still far from perfect, though.

   As in actually able to use it: No, I can absolutely not feel at which places the points are, my fingers aren't sensitive enough, yet. 😭

   But I bought one of those Braille board thingies to punch your own Braille into paper!

4. Embed this notice
   HistoPol (#HP) 🏴 🇺🇸 🏴 (histopol@mastodon.social)'s status on Saturday, 05-Oct-2024 03:01:17 JST HistoPol (#HP) 🏴 🇺🇸 🏴

   in reply to

   @gooba42

   (1/2)

   I agree. In this aspect, realistic expectations are critical to not disappoint BIPOC citizens, though.

   As my handle suggests, I do look a lot at history. Still, it had not been until I listened to Mathew Cook's podcast to realize the dimension of the problem. The US were indeed built as a #SlaverNation and for the sake of unity after the War Beween The States, the North made too many concession to the Conderates during Reconstruction.... @JustOneMoreThing

5. Embed this notice
   screaminggoat (screaminggoat@infosec.exchange)'s status on Friday, 27-Sep-2024 09:49:14 JST screaminggoat

   in reply to

   Tenable: CVE-2024-47076, CVE-2024-47175, CVE-2024-47176, CVE-2024-47177: Frequently Asked Questions About Common UNIX Printing System (CUPS) Vulnerabilities
   This is perhaps the most informative and comprehensive guide to the CUPS vulnerabilities yet. While I question the use of the phrase zero-days, they were publicly announced prematurely due to a leak ahead of a coordinated disclosure date, and proof of concept has been released. Fortunately, it's not the 9.9 doomsday that everyone was hawk tuahing about. Skibidi I don't think anyone reads what I write anyway. Only in Ohio though.

   As @CraigHRowland said:

   The bad news is there is a vulnerability in the CUPS printer system on Linux. The good news is nobody has ever gotten their printer working on Linux so they are safe.

   #CVE_2024_47076 #CVE_2024_47177 #CVE_2024_47175 #CVE_2024_47176 #CUPS #linux #vulnerability #cve

6. Embed this notice
   Kevin Leecaster (greenfire@mstdn.social)'s status on Saturday, 24-Aug-2024 07:47:56 JST Kevin Leecaster

   in reply to

   @Snowshadow @TonyStark
   American exceptionalism or something is why we are so wont to complain despite how good we have it I suppose. That's a dissertation I'll not be writing though.

   As to energy prices, I noticed that CNN's Jake Tapper "called out" VP Harris for not having a more thoroughly fleshed out set of policy positions for him to critique yet he hasn't criticized Trump's promise to lower energy prices by 50% his first year back in office.

   That would cause instant recession or worse.