<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Topics tagged with 64-bit]]></title><description><![CDATA[A list of topics that have been tagged with 64-bit]]></description><link>https://vulndetect.org/tags/64-bit</link><generator>RSS for Node</generator><lastBuildDate>Sun, 07 Jun 2026 01:43:31 GMT</lastBuildDate><atom:link href="https://vulndetect.org/tags/64-bit.rss" rel="self" type="application/rss+xml"/><pubDate>Thu, 17 May 2018 08:03:28 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[[Implemented] Differentiate between 32-Bit and 64-Bit]]></title><description><![CDATA[@tom IMHO it would make sense to show the "(64-Bit)" behind the name of the application, so users see the differences between two identical apps at once (without having to expand the entries).
By the way: if you set an entry to [Implemented], then you also have to update the Overview of Feature and Functionality Requests.
So just leave a comment, that it is implemented, and I will do the rest.
]]></description><link>https://vulndetect.org/topic/31/implemented-differentiate-between-32-bit-and-64-bit</link><guid isPermaLink="true">https://vulndetect.org/topic/31/implemented-differentiate-between-32-bit-and-64-bit</guid><dc:creator><![CDATA[OLLI_S]]></dc:creator><pubDate>Thu, 17 May 2018 08:03:28 GMT</pubDate></item></channel></rss>