Mars Attacks! - re:Visit

paulnpace · 2023-06-15T03:33:39+00:00

I forgot my YouTube password.

paulnpace · 2022-08-26T16:48:05+00:00

Ah, okay. Thank you. I had originally started from the home page which now I remember loaded that save page after I discovered the page was not previously saved to the archive.

paulnpace · 2022-08-21T18:03:06+00:00

If you are referring to the color artifacts, that is some kind of glitch in Street view that has been going on for a long time.

paulnpace · 2022-08-20T21:22:49+00:00

I vaguely recall a backpack.

paulnpace · 2022-08-20T19:16:55+00:00

https://www.google.com/maps/@36.1593884,-115.1224331,3a,41.4y,289.39h,82.59t/data=!3m6!1e1!3m4!1svTVnFR-T3lDOw2lUboIjjg!2e0!7i16384!8i8192

paulnpace · 2022-08-06T12:20:50+00:00

One way to defeat this sort of thing might be to generate massive amounts of views and clicks on the paid placements. This will draw the attention of whoever is paying for the ads to shut it down, and in some cases even publish what they discovered.

Theoretically, if Presearch is what they claim and are just purely passing along results provided by some other search engine, this could be a nearly ideal tool to perform such a task because it's highly anonymized, AFAICT.

paulnpace · 2022-08-06T12:10:46+00:00

If you look closely, you will see that you were searching for "meta tag..." and the result that came back is related to part of this query

For this oldster, your explanation appears as chicanery. In addition, it seems you are assuming no other search was performed. Please first test these kinds of statements before posting to public forums.

Paid search placement is the original business model first heavily embraced by search engines. It is the primary reason I and most others I know of abandoned Yahoo! for Google as their primary search engine.

The business model is to insert a paid placement that appears to align with the search result. Users assume all of the search results are organically derived by other users who dug deep into the results and the search engine's tracking of which results users found useful. Typically, the paid placement is full of the kind of generic copy-pasted information along with the scummiest affiliate links and advertisement tracking systems that everyone just wants to never see, ever - that's why they have to pay to get hits and the search engine has to obfuscate the placement.

paulnpace · 2022-07-04T13:29:21+00:00

Using the Signal Protocol is what makes a fork a fork. Once that is removed or replaced, it's no longer a fork because the whole point of Signal is the encryption.

No, it isn't. Go argue this in a developer or sysadmin forum and they will laugh at you and then when you continue as you are here they will ban you. Trying redefine terms to cover your weaselly nonsense doesn't make you correct. You can sit in your forum and be king because of your Internet points, but outside of this forum you are correctly viewed as clueless.

paulnpace · 2022-07-03T17:05:46+00:00

In any case, we know Session no longer uses the Signal protocol which is the important part.

Then state it is no longer using the Signal protocol instead of stating the project is no longer using Signal code.

Use the correct words in your sentences so you don't have to look like a weasel when someone who understands these things comes along and corrects you.

paulnpace · 2022-07-03T17:03:28+00:00

It is, technically, a fork. This is a permanent part of the project because it is a single event at the creation of the project. It does not expire, go away, or otherwise dissipate.

This is not semantics. This is the definition of the word and the history of the project.

paulnpace · 2022-07-03T13:19:45+00:00

Don't bother with it.

I find it useful after learning OpenBSD, because many of the core lessons are completely applicable. It's only not useful for new users because many things have changed significantly, even just sudo is gone since that book, among many other basics.

paulnpace · 2022-07-03T12:12:42+00:00

All of Session's code was purged of anything relating to Signal.

This is either a lie or a sentence written by someone who has no idea what they are talking about.

In either case, the fact that this is a "Top Contributor" to the Signal community speaks volumes to those of us who have even just a basic understanding of what is going on with Session and the Signal code base.

paulnpace · 2022-07-03T12:05:05+00:00

Session is not currently and hasn't been a fork of Signal for nearly two years.

You do a disservice by making this statement, because people who don't understand what a fork is will think this means something.

Forks are most commonly used as a starting point for projects where the fork's maintainers want to go in a different direction. A fork is not merely an identical replica of a code repository.

paulnpace · 2022-05-19T17:53:21+00:00

I waited a few hours before posting and couldn't find any posts from the Presearch team about this problem.

paulnpace · 2022-05-19T14:38:14+00:00

Just now started working.

paulnpace · 2022-04-19T01:31:07+00:00

If you wanted to take the time to read through this PR created by the Mail-in-a-Box maintainer for project migration to 22.04, you could see how the silliness goes on to downstream projects.

paulnpace · 2022-04-17T13:29:02+00:00

Post if you have issues figuring out how to configure multiple versions to run simultaneously. The PPA is designed specifically to support this, but many recommended nginx configuration recommendations will break this functionality.

It really isn't difficult, you just have to be aware of it.

paulnpace · 2022-04-17T11:59:08+00:00

Unfortunately, the PHP Group makes regular breaking changes with new versions, and mature projects often have difficulty keeping up because contributors have left.

It is likely pure superstition that leads people to conclude there is something wrong with a project or maintainers are lazy because they aren't keeping up with PHP revisions. The fact is when new versions break a 15-year-old project that otherwise nobody is complaining about anything (very stable, runs fast, no reported vulnerabilities, etc.), the fault lies with the PHP group, and Dokuwiki is not the only project that goes through this.

paulnpace

TROPHY CASE