Like, really close, like each time he tried he kept getting closer
Post hog
Like, really close, like each time he tried he kept getting closer
Zeno was a time traveler
Testers are a godsend
Get a government job; everybody leaves at 5pm
My first introduction came from an episode of Reading Rainbow in which LeVar Burton takes the viewer on a behind-the-scenes look at how some of the props and special effects work on this other show he’s on called Star Trek: The Next Generation. I watched whatever the next episode was after that airing. According to IMDB, that episode aired August 15th, 1988, so it likely was a rerun from the 1987 season.
Oh I definitely agree with you there. I just think GPL is close but not close enough.
That’s why the current state of open source licenses doesn’t work. Commercial use should be forbidden for free users. You could dual license the work, with a single, main license applying to everyone, and a second addendum license that just contains the clause for that specific use, be it personal or corporate. Corporate use of any kind requires supporting the project financially.
Definitely voyager.
Obligatory “systemd was a mistake, they played us for absolute fools, yadda yadda yadda”
You mentioned PGP already, but this is exactly what that technology was designed for. You can sign the post with your private key, meaning anyone with the public key can verify its authenticity, and sites such as GitLab make use of this for signing code commits to prove it came from the author listed on the commit. A scaffolding utilizing PGP for blogging may already exist. You’d have to enter your PGP passphrase to seal the post. In fact, you may be able to take advantage of the exact mechanism GitLab and others are already using by publishing by way of a signed git commit, and displaying like a green lock or something on blog posts that are authenticated.
Nice
I’m partial to ENT and TNG, the first because it was novel and the second because it was my childhood Trek.
Big oof on the price, but I get it. That’s a really well thought-out and executed replica.
Alternative theory: it’s a Cali class ship, so the EPS capacitors did rotate automatically once over the course of a day, but that system broke and they haven’t gotten whatever replacement part is required, so they put ensigns on the task until the automated solution is fixed.
Learn emacs
Someone have a local clone? Post it to a different host.
Because many people would take that suggestion and simply light the paper on fire and let it burn. This produces large pieces which are still usually quite legible.
To make the paper burn to ashes as you’ve said, you have to burn it in an existing fire long enough for it to turn to white ash, and then it’s often still required to stir the ashes to break up any remaining large pieces. At that point, yes, it is thoroughly destroyed.
With either burning or pulping, you can simply flush the remains down the toilet.
If burning, you should use an accelerant and make sure they are fully incinerated, and then stir the ashes to break up any large pieces of charred paper. Stacks of paper are notoriously hard to burn on their own, but if left in an existing fire long enough they will burn to ash just like wood.
For pulping, an alternative I just saw on another site would be to mix the slurry in a blender to chop the pieces. That would certainly be faster than what I said previously.
Drop the black requirement and you could pulp them. Put the labels (as long as they’re paper based) in a solution of water and bleach and leave it there. Keep adding new labels as they come in, and stir the mixture like daily or something. They will start to break down into a mush. At that point you can pull out any mushed blobs of pulp and leave any larger pieces to keep breaking down.
They did lower decks wrong when they cancelled it.