The amount of confidently incorrect responses is exactly what one could expect from Lemmy.

First: TCP and UDP can listen on the same port, DNS is a great example of such. You’d generally need it to be part of the same process as ports are generally bound to the same process, but more on this later.

Second: Minecraft and website are both using TCP. TCP is part of layer 4, transport; whereas HTTP(S) / Minecraft are part of layer 7, application. If you really want to, you could cram HTTP(S) over UDP (technically, QUIC/HTTP3 does this), and if you absolutely want to, with updates to the protocol itself, and some server client edits you can cram Minecraft over UDP, too. People need to brush up on their OSI layers before making bold claims.

Third: The web server and the Minecraft server are not running on the same machine. For something that scale, both services are served from a cluster focused only on what they’re serving.

Finally: Hypixel use reverse proxy to sit between the user and their actual server. Specifically, they are most likely using Cloudflare Spectrum to proxy their traffic. User request reaches a point of presence, a reverse proxy service is listening on the applicable ports (443/25565) + protocol (HTTPS/Minecraft), and then depending on traffic type, and rules, the request gets routed to the actual server behind the scenes. There are speculations of them no longer using Cloudflare, but I don’t believe this is the case. If you dig their mc.hypixel.net domain, you get a bunch of direct assigned IP addresses, but if you tried to trace it from multiple locations, you’d all end up going through Cloudflare infrastructure. It is highly likely that they’re still leaning on Cloudflare for this service, with a BYOIP arrangement to reduce risk of DDOS addressed towards them overflow to other customers.

In no uncertain terms:

1. Hypixel.net has Cloudflare DNS for their domain.
2. For their website, it has orange cloud enabled to proxy traffic through CF’s global CDN and DDOS protection service.
3. For their Minecraft server, they advertise mc.hypixel.net, but also have a SRV record for _minecraft._tcp.hypixel.net set for 25565 on mc.hypixel.net
4. The mc.hypixel.net domain has CNAME record for mt.mc.production.hypixel.io. which is flattened to a bunch of their own direct assigned IP addresses.
5. Traceroute towards those direct assigned IP addresses goes through Cloudflare infrastructure but final destination is obscured, just like their website, to protect them from DDOS attacks.

Launch was cancelled minutes before go.

Approx 35k power on hours. Tested with 0 errors, 0 bad sectors, 0 defects. SMART details intact.

That’s about 4 years of power on time. Considering they’re enterprise grade equipment, they should still be good for many years to come, but it is worth taking into consideration.

I’ve bought from these guys before, packaging was super professional. Card board box with special designed drive holders made of foam; each drive is also individually packed with anti-static bags and silica packs.

Highly recommend.

And here’s the reason why layman should not: they’re much more likely to make that one wrong move and suffer irrecoverable data loss than some faceless corporation selling their data.

At the end of the day, those of us who are technical enough will take the risk and learn, but for vast majority of the people, it is and will continue to remain as a non starter for the foreseeable future.

A lot of devs I know are purely ticket in ticket out… so unless someone convinced management there’s a performance problem and that they’d need to prioritize it over new features (good luck), then it will not be done.

Looks like a case where poorly sourced article getting removed, with invitation to repost with a more reputable source... so do so with a better source. Or is the underlying article itself leaning too much towards propaganda that there is no more reputable source? and if that is the case, then is it really !news worthy?

COPPA is pretty straight forward — the tl;dr is that websites are not allowed to collect personal info from children under age of 13.

If TikTok have users under the age of 13, and they’re profiling those users the same as they are with adult users (adult users of TikTok? This sounds so weird and foreign to me; I must be too old), then they’re in hot water. I don’t see how there’s any minority report style of thought crime going on here. It’s pretty cut and dry…

Good luck getting that through the system… the cost to run something like YouTube is… well, let’s just say the lack of real competitions speaks volumes.

On the flip side, can you imagine being stranded on the ISS, and watching the ship that could have taken you home gone down safely?

Damned if you do, damned if you don’t. They’re holding up amazingly well, I don’t envy the astronauts right now.

At least from the nerd side of Lemmy, communities pertaining to technology, self-hosting, etc. — which I’d imagine to be the larger drivers due to how complicated it is to join compared to a traditional centralized setup (see also same hurdle for mastodon vs Twitter; which doesn’t gain adoption until Thread and BlueSky started to attract the less technical users), I’m seeing troubling signs of slowing down and shrinking.

If people actually want Lemmy in these areas to grow, it is important to be a lot more inclusive, and understand when to not participate in order to foster better community growth.

What I mean on the inclusive side is those FOSS advocates need to back off with the “You don’t understand FOSS, and go make your own instance” comments so other users don’t just bounce right off and leave after being bored with nothing to interact with.

What I mean by understand when not to participate is literally don’t participate in niche communities that doesn’t apply to you. So many Android users commenting irrelevant anti-Apple sentiments in Apple Enthusiasts community, for example. This is driving away actual users who are interested in discussions.

The charts don’t lie. Lemmy is shrinking, not growing. After getting a new lease on life with 0.19 due to what is essentially clever accounting, the community is still slowing down/shrinking. And for the nerdier side of the userbase, unless the community by and large start to interact more inclusively, the whole thing is sadly going to be just a small blip that’ll soon fizzle out.

There’s no shortage of people who will tell you it’s okay to self host email… in fact, you’re probably not hearing all of them, because some will inevitably get routed to spam.

At $80 a pop, might get more oomph from an older optiplex if electricity cost isn’t too big of a concern?

Locks can happen by registrar (I.e.: ninjala, cloudflare, namecheap etc.) or registry (I.e.: gen.xyz, identity digital, verisign, etc.).

Typically, registry locks cannot be resolved through your registrar, and the registrant may need to work with the registry to see about resolving the problem. This could be complicated with Whois privacy as you may not be considered the registrant of the domain.

In all cases, most registries do not take domain suspensions lightly, and generally tend to lock only on legal issues. Check your Whois record’s EPP status codes to get hints as to what may be happening.

You guys have cubicles? I thought we’ve done away with that and mandated all offices to be deprived of walls and dividers since the 2010s in favor of open office floor plans? Someone get the office manager on the line.

Multiple compose file, each in their own directory for a stack of services. Running Lemmy? It goes to ~/compose_home/lemmy, with binds for image resized and database as folders inside that directory. Running website? It goes to ~/compose_home/example.com, with its static files, api, and database binds all as folders inside that. Etc etc. Use gateway reverse proxy (I prefer Traefik but each to their own) and have each stack join the network to expose only what you’d need.

Back up is easy, snapshot the volume bind (stop any service individually as needed); moving server for specific stack is easy, just move the directory over to a new system (update gateway info if required); upgrading is easy, just upgrade individual stack and off to the races.

Pulling all stacks into a single compose for the system as a whole is nuts. You lose all the flexibility and gain… nothing?

That’s a drop in the pond in the grand scheme of things. You just out source that out to rights management companies and absolve yourself from that obligation behind safe harbour. This is basically what they’re doing in this department. They’ve built Content ID for digital finger printing, and then invented an entire market for rights management companies on both sides of the equation.

On the other hand, 500 hours of video footage got uploaded to YouTube every minute per YouTube in 2022 (pdf warning). 30 minutes of video game content (compresses better), just the 720p variant using avc1 codec is about 443MB of space. Never mind all the other transcodes or higher bitrates. So say 800MB per hour of 720p content; 500 hours of content per minute means 400GB of disk space requirement, per minute; 500TB of disk space per day.

That’s just video uploaded to YouTube. I don’t even know how much is being watched regularly, but even if we assume at least one view per video, that’s 500TB of bandwidth in and then 500TB of bandwidth out per day.

Good luck scaling that on public budget.

Being barefoot could potentially introduce extra risk of contamination from shedding skin cells; this may or may not matter depending on which part of the plant they’re working at. In clean room environments, people usually wear special clothing that prevent cross contamination; these include special coat, hair netting, and extra layer of covering around the shoes. But if the said employee works in the office on administrative tasks, far away from clean areas of production, who cares?

Very much as expected… fragmented, incomplete, and highly dependent on carrier. Google’s non standard E2EE extension will likely only work if messages are routed through their servers, which based on the observations here, even from the Android side it doesn’t seems to be routed through Google. Larger file means better quality pictures via green bubbles, anyone who’s sent/received a garbage and cares enough knows to send via third party messaging apps anyway, so nothing life changing here.

Let’s see if Apple applies pressure and push everyone to use Google’s servers for E2EE as they move towards iOS 18, but other than that… I’m still inclined to think the down play during keynote is apt.

Security when you’re on untrusted network. I can trust Google to snoop my banking data and update the spending power info on my ad profile, I can’t trust the random dude in trench coat also using the public wifi when I am traveling out of my roaming coverage.

I joke of course, but the security aspect is still valid.

"Molecular-genetic testing has been completed," it said in a statement.

"According to its results, the identities of all 10 deceased have been established, and they correspond to the list published in the flight manifest."

Not sure what’s more impressive; fact that they were able to turn the test results back so quickly, or fact that all 10 deceased, including the flight crew, have their DNA in some sort of database. Isn’t it supposed to take weeks to do the analysis?

So just because they don’t know technology like you do, they should be left behind the times instead of taking advantage of advancements? A bit elitist and gate keeping there, don’t you think?

Everyone have their own choices to make, and for most, they’ve already decided they’d rather benefit from advancements than care about what you care about.

They do, and they’ve shared the counter measure (lockdown mode) with the world.

If a nation state will individually target someone, they don’t need to doom scroll on insta (nor do they need to). Locking down the phone to the bare minimum for these kind of people is the appropriate level of response.

Having seen some spicy pillows in my times… I’d hate to be onboard if any of the battery containers becomes a bouncy castle.

You didn’t wreck the big corps. You opted yourself out of their warranty thereby saving them any money they would’ve had to spend on repairing your purchase during the defined warranty window. If anything you lined their pockets by making yourself a cheaper customer.

Safe harbour equivalent rules should apply, no? That is, the platforms should not be held liable as long as the platform does not permit for illegal activities on the platform, offer proper reporting mechanism, and documented workflows to investigate + act against reported activity.

It feels like a slippery slope to arrest people on grounds of suspicion (until proven otherwise) of lack of moderation.

They’re keeping everything anyway, so what’s preventing them from doing a DB look up to see if it (given a large enough passage of text) exist in their output history?

It is probably best to think nothing on Lemmy is private. Any instance with at least one user subscribed to a community will receive updates (messages and votes) on the community. Instance admin can go into the database to see any private message between any user on that instance.

What kind of attacks, against what service?

DDoS? It’s cheaper to hire botnets to attack than to defend. You’d most likely still be knocked off even just by the amount of traffic that leaks through your proxy before the VM gets cut off at the data centre. Specifically: it is much more likely that data centres will give higher thresholds before null routing your VM than your residential ISP would be wiling to tolerate.

Brute force on shell? SQL injection? Remote shell execution? Deploying the extra layer will not protect you from these as your own proxy will not give you WAF.

It is always important to know why you’re doing something, before anyone can prescribe a solution.

Or better yet, let her keep her gmail. Don’t force any lab instability on to others… especially email. One lost important email (even if not your fault) and you’ll never hear the end of it.

Apple is implementing it because China requires all 5G phones to support RCS to get certified.

Apple did not do this because they suddenly have a change of heart about the green bubbles. Apple did not do this to spite regulatory bodies and ‘malice compliance’ with some interoperability mandate.

This is not a move to make messaging more secure with the green bubbles. This is not a move to make messaging better with the green bubbles. This is a move so they can continue to sell phones in China.

What’s the resources requirements for the 405B model? I did some digging but couldn’t find any documentation during my cursory search.

If you’re going to use it, you’d be paying for it one way or another; either through money or privacy. Par for the course.

What is your objective for ‘hide server IP’?

Privacy to disconnect your identity from the service? There is no solution to this. Full stop. Even with Tor, the state backed acronym entities will figure it out if you get on their radar.

If your objective is to keep your service online, you’re going to be hard pressed to find cost effective alternatives… Commercial solutions are expensive, like, “if you have to ask about the price, you can’t afford it” expensive.

Alternatively, you can try to roll your own by having many many proxy servers yourself… but if you’ve got a target on your back, you’ll never have enough instances; DDOS-as-a-Service is much cheaper than the amount of reverse proxies required to keep your service online.

There’s probably other use cases, but chances are, you’d still be hard pressed to find a solution that’s cost effective.

At the end of the day, you’re running containers and both will get the job done. Go with whatever you want to start, and be open to try the other when you inevitably end up with jobby job that uses the other one instead.

The article linked to the analysis and on a quick glance, it seems to be done entirely against the Android variant of the app. This makes sense because if the alleged actions are true, they’d never have gotten on to the App Store for iOS Apple users… or at least as of a couple months ago. Who knows what kind of vulnerability is exposed by Apple only doing limited cursory checks for 3rd party App Stores.

I’m aware this is the selfhost community, but for a company of 20 engineers, it is probably best to use something commercial in the cloud.

Biggest pain point was for our ops guy, who constantly had to stay behind to perform upgrades and maintenance, as they couldn’t do it during business hours when the engineers are working. With a team of at least 20, scheduling downtimes could get increasingly more difficult.

It also adds an entire system to be audited by the auditors.

The selfhost vs buy commercial kind of bounces back and forth. For smaller teams, less than 5 to 10 engineers, it might be a fun endeavour; but from that point on, until you get to mega corp scale with dedicated ops department maintaining your entire infrastructure, it is probably more effective to just pay for a solution from a major vendor in the cloud instead.

Emojis used zero width joiner to combine multiple single code point emoji to a single combined emoji.

⛥ + ZWJ + ⬠ could form the combined character, and be rendered as desired.

Here we observe a pro gatekeeper in their natural habitat…

Why not? I’m sure some intern with red username would be tasked to find features that we like here, just so they could copy it to try to bring users back.

Again, that’s what you’d like to achieve, but why?

Without the reason, there is no way to provide a useful answer that would adequately address the underlying reason.