TechLich

I don't think that's how it works? It's the client application that has the key for the end to end encryption, not the server. I don't think you need to trust the matrix server you use? I could be wrong, I don't know matrix particularly well.

Yeah, that's fair enough, though I'm not sure it's very different from malicious instances creating normal user accounts?

You can see when users from an instance are all suspiciously voting the same way at the same time regardless of whether they are usernames or IDs.

There's lots of legitimate users that only vote but never post so doing it based on that doesn't seem very effective?

The second problem is solved using public key cryptography, the same way that you can't impersonate someone else's username to post comments. Votes and comments are digitally signed (There would need to be a different public key for voting to maintain pseudonymity though).

How about pseudonymous as a compromise? Votes could be publicly federated but tied to some uuid instead of the username. That way you still have the same anti spam ability (can see that a user upvoted these things from this instance at this time) but can't tie it directly to comments or actual user accounts without some extra osint.

It might be theoretically possible to correlate the uuids with an account's activity and dox the user in some cases, especially with some instances having a single user, but it would be very difficult or impossible to do on larger instances and would add an extra layer. Single user instances would be kind of impossible to make totally private anyway because they can be identified by instance.

Yeah, I think you're right but the phrasing is a little weird for that. It makes it sound like the optimiser lets you avoid having to do a "hex dump" which would be somehow "fattening" for the program causing it to have worse performance. Might be the marketing people not knowing what they're talking about.

Although we did do a lot of printing code on dot matrix printers back in the day, it would usually be the source code itself, this is a post-pass optimiser. It ran after the COBOL compiler had already turned the human readable code into object code. Although printing out the optimised hex might save on paper as a backup solution, it probably wouldn't help with debugging.

"virtually eliminate fattening hex dumps"

What is a fattening hex dump in this context‽

I'd add to this to say that redis as a key-value store often sits alongside a relational database like postgres etc. to act as a cache for it.

Basically, requests to be sent to the relational db (like postgres) get turned into a key and the results stored as a value in redis. Then when the same request comes through again, it can pull the results quickly out of the key-value store without having to search postgres by running a long SQL query again. There's a few different caching strategies to keep things up to date or have the cached data expire regularly, etc. but that's the gist of it.

Important to note that not all applications need something like that and not all queries would even benefit from it (postgres is pretty fast and can even do that kind of thing itself) but if there's a lot of users running the same slow query over and over, caching the results can help immensely.

It does sound very strange. What kind of anti-China content would ever help a student's application process? Most of the application documents are about things like English language competency, visa requirements and prior qualifications, not political opinions.

Ifnkovhgroghprm

The most popular brand of matches in Denmark is called Tordenskjold. In the late 1800s, Sweden had a large export production of matches, so a Danish manufacturer put Tordenskiold's portrait on his matchbox in 1882, in the hope he could once more strike at the Swedish (Danish: give de svenske stryg).[13] The Tordenskjold brand was bought by a Swedish company in 1972.[14]

Ouch.

Haha, the internet did not fit on a 1.44mb floppy in 1998. Curious to know what was on this‽

1998 was well into the CD-ROM era and the internet was full of .mp3s and .isos by then.

Raccoon was fantastic and you should be proud of what you accomplished! It's a great app and I'm sure whatever else you work on in the future will be awesome.

It's not that it's on the 172.16.0.0/12 range. That's totally normal and used for all kinds of stuff.

It's that it's in 172.16.42.0/24 which is the default dhcp settings for a wifi pineapple. It's the /24 mask given on the .42 that's a little suspicious because that's not a common range for anything else.

Being assigned one of those specific 253 hosts with that subnet mask would definitely make me think twice.