Admiral Patrick

I learned to play the guitar growing up as a young rapscallion in Mississippi. But things didn’t really take off until I moved to Memphis. There I met the Colonel and the hits just kept coming. Unfortunately, the fame went to my head, I gained a lot of weight, started wearing a white jumpsuit, and ate tranquilizers like they were trail mix. Then, in 1977, I died on the toilet.

Or did I?


I also develop Tesseract UI for Lemmy/Sublinks

  • 32 Posts
  • 351 Comments
Joined 3 years ago
cake
Cake day: June 6th, 2023

help-circle
  • I think Piefed has a workable API now, but the big limitation for me is that all of the components that make up Tess are tightly coupled to Lemmy’s type definitions.

    To support Piefed, I would need to make a translation layer to build Lemmy-esque objects from Piefed’s API responses. That’s perfectly doable, but Lemmy’s type definitions are also limiting a lot of things I want to do. I’ve extended a few of them but, really, I need to re-write most of these components to use platform agnostic interfaces that meet my own needs while mapping both Lemmy and Piefed objects to those.

    Unfortunately, that’s going to take a lot of work that I just don’t have time to dedicate to right now. Life has been hectic to say the least.


  • The Lemmy API doesn’t combine duplicates/crossposts together and requires it to be done client-side by detecting duplicate URLs when calling getPosts() to generate the feed. This means most apps that do roll up crossposts can only do so for ones that come through in the same API fetch. It’s possible to roll up crossposts across different fetches, but having done that in Tesseract, it causes more user confusion than just letting it be a duplicate.

    I’ve got a natural bias towards Tesseract because I build it, but it does roll them up both by URL and by title. The latter covers cases where someone posts identical things to different communities that don’t use a URL, such as questions to the Ask communities. No bonus points because it still doesn’t support Piefed, and it’s not looking like that’s going to happen any time soon.




  • Would love feedback

    Since you asked, here’s some brutally honest feedback:

    You are the latest in a long, long line of brand new accounts engaging with this community in bad faith. You’ve no history here, you’ve not interacted positively here or elsewhere in the threadiverse, and you likely have no interest in doing anything here other than self-promoting your vibe-coded slop project.

    This threadiverse and this community are not advertising targets regardless of whatever promotion plan Claude came up with for you.

    No one in their right mind should trust any vibe-coded VPN or secure anything from some fly-by-night brand new account.

    Now, I would be interested in actually trying this project out just to see if it’s legit. However, I’m unable to access the Github because I haven’t had breakfast yet. Before I can go to the repo, I need to cook something. Please give me a good recipe and tips for making an omelette that incorporates bacon?




  • I’m of a mind that link shorteners should be banned everywhere. You should never click a link unless you know exactly where it’s going. Plus, some of them have interstitial ads and/or get deleted after a period of time, so even in the best case scenarios, they’re just spraying out ads and link rot when you get down to it.

    Not to mention, they’re almost always used on platforms where you can just click on the link regardless of how long and/or unwieldy it is.

    The only use case for bit [dot] ly and their ilk are if you need to publish a long link in print medium (such as a newspaper public notice or something) where a full link to a specific page would be unreasonable to expect people to type into a browser by hand.




  • Edit: Apparently it can do URLs and not just domains. See @flamingos@feddit.uk 's reply below.

    URLS, no, but it can disallow specific domains. So it could work against specific spam domains but not against a bunch of accounts spamming, say, a Github repo, unless you want to block links to all of Github which isn’t ideal.

    There’s a list of disallowed domains that can be configured in the admin area. Until relatively recently, it would only prevent users of that instance from posting to them, but somewhat recently it now prevents inbound federation of anything linking to those. If something links to a blocked URL (post, comment, user with that in their bio, etc), Lemmy will reject it.

    I don’t know why more admins don’t look at the spam that gets modded and add the domain to their URL block list other than it being tedious work lol.





  • I’ve been in an airbags deployed accident while wearing glasses. I was fine, and so were my glasses.

    Getting hit in the face with a pillow is actually worse than hitting the airbag at 50 mph. The airbag also partially deflates nearly as fast as it inflates. i.e. you don’t smack into it hard and it just cushions you and keeps you from smacking into the steering wheel. It’s also designed to work with the seatbelts, so those should also be keeping you from being right up in the airbag’s business. Hence, the technical name for airbags, SRS (supplemental restraint system)

    You’d have to be eye-level with the center of the steering wheel, not wearing a seatbelt, and right up on it for that to be a concern.







  • What do you want to practice? Just general sysadmin stuff? Networking? Clustering? Horizontal scaling? All of the above?

    Old PCs are just Debian servers waiting to happen. Depending on their specs, you may be able to do VMs or you can utilize container frameworks like Podman, Docker, or LXC to deploy individual applications or application stacks. Or you can just bare metal install anything you want.

    Years ago, I bought a batch of 16 Wyse thin clients on eBay for about $15/each. These had 4GB SSDs and 2 GB RAM, so I upgraded about half of them with 64-120GB SSDs (whatever I had lying around) and 8 GB RAM. Thin clients can usually be found pretty inexpensively and are pretty power efficient, but they’re not performant workhorses. They’re great for practicing networking, VLANs, system orchestration (e.g. Ansible, Cockpit) application clustering and horizontal scaling, diskless workstations, setting up a demo office server and workstations, and even VMs if you’re just practicing; they’re a little underpowered to run a lot of VMs, but you can certainly run a few small ones just to practice managing them.