• 0 Posts
  • 37 Comments
Joined 3 years ago
cake
Cake day: June 19th, 2023

help-circle
  • Strictly speaking, they’re leveraging free users to increase the number of domains they have under their DNS service. This gives them a larger end-user reach, as it in turn makes ISPs hit their DNS servers more frequently. The increased usage better positions them to lead peering agreement discussions with ISPs. More peering agreements leads to overall cheaper bandwidth for their CDN and faster responses, which they can use as a selling point for their enterprise clients. The benefits are pretty universal, so is actually a good thing for everyone all around… that is unless you’re trying to become a competitor and get your own peering agreement setup, as it’d be quite a bit harder for you to acquire customers at the same scale/pace.


  • 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.


  • 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.


  • Filled it!

    I understand your experiment is already under way, so it is unlikely that you’d be able to change your methodologies at this point. One small feedback on the questions, however. As presented (to me, maybe the system is randomized, I don’t know) the questions felt leaning towards difficult/complex to use, which may lead the user skewing their responses negatively. While this may be counterweighted by the fact that you’re asking a niche community using these systems already to complete the survey, it may still be a good idea to ask more neutral questions and allowing the users to select from a spectrum instead.

    For example; instead of “I find the system unnecessarily complex; Strongly Disagree… Strongly Agree”, it may potentially be better to ask “How do you find the system? Very Straightforward … Very Complex”. Your score for each of the selection would be consistent (1 is less complex while 5 is more complex), but you’re not impressing a negative sentiment on the user.

    Anyway, good luck with your study! Looking forward to your published results!


  • I don’t know about other platforms, but YouTube membership is totally implementable on any other platform.

    The workflow anyone need to implement is the same flow Discord has implemented:

    1. Perform OAuth to get the user’s own channel using the mine filter on channels.list end point. This way the service can know SomeOneWatching is owner of channel UC1234ABCD
    2. Perform OAuth to get the host’s members on a fixed interval to get a list of all members, and match it against all known users’ channel IDs or target individual user like SomeOneWatching’s UC1234ABCD channel ID as part of filterByMemberChannelId on the same members.list end point.
    3. Upgrade users’ groups on the service to reflect membership accordingly, no direct YouTube partnership required.
    4. Revisit the same flow in 2 regularly to downgrade when memberships are not renewed; beyond the pubsubhubbub which notifies subscription content updates (new uploads/deletions) on a subscribed channel, YouTube does not have a push notification for automatic updates. This is why there’s always a slight delay when membership status changes.

    Source: I’ve worked in YouTube adjacent company using all of their public and several proprietary APIs for around 10 years now. I’m fairly familiar with their API offerings.


  • On a lot of the image boards described by OP, tagging is managed by the users collectively. That is, almost everyone could not only add but also remove tags from content, as well as collectively maintain wiki on what the individual tags mean. When multiple similar tags meaning same thing come up, they’d alias to one central one; when different usages of same tag come up, they’d take a Wikipedia-esque approach to differentiate them; some even go as far as creating categories for tags so similar concepts can be grouped together. Trouble makers (people who repeatedly use tags incorrectly) lose their tagging privileges and so problem is kind of managed at bay.



  • One downvote from the OP to troll; one downvote from the troll to OP; ten downvotes from the troll’s arsenal of alts to OP; hundreds of downvotes to the troll from the community.

    Reddit with their quirks and issues have at least demonstrated it’s fine for the most part. Established communities can identify trolls quickly, make them easier to spot for moderators through voting, and enable moderation tools to act and block quickly. Whereas the current Lemmy system feels like burying their head in the sand, and pretending trolls can’t exist because only admins can, through convoluted queries, see the users’ historical vote aggregate.








  • 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?


  • Civilian here. There are companies that mine, store, transport and broker uranium. These companies employe people with different skill sets from physical labor all the way up to management. An increase in price may lead to an increased level of employment by these companies, thereby increasing the number of jobs, and play a role in impacting the economy at large. It makes sense for this kind of news to be filed in the business section, even if it doesn’t directly affect most of our day to day.